Fayeblade FAQs

Question 1

How does Fayeblade communicate with other applications?

Accepted Answer

It communicates over standard input/output (`stdin/stdout`) using a JSON-RPC-like protocol. Fayeblade supports two transport framing modes: `line` (one JSON message per line) and `content-length` (HTTP-like `Content-Length: N` framed messages).

Question 2

What are the benefits of Fayeblade's I/O design?

Accepted Answer

Fayeblade's I/O design is hardened to prevent common protocol mismatches and issues. It uses a custom writer that never logs to `stdout` (all diagnostics go to `stderr`), ensures clean flushing per message, and maintains a pure protocol channel for reliable communication.

Question 3

Can Fayeblade maintain browser sessions or cookie states across multiple operations?

Accepted Answer

Yes, Fayeblade supports a single persistent browser context. By configuring the `MCP_STORAGE_STATE` environment variable, it can save and reuse session data, including cookies and local storage, enabling 'logged-in' states across calls.

Question 4

What is Fayeblade and what does it do?

Accepted Answer

Fayeblade is a browser automation bridge that uses Playwright to control web browsers. It enables host applications to interact with a browser over `stdin/stdout` using a JSON-RPC-like protocol for robust, programmatic web interactions.

Question 5

Which web browsers does Fayeblade support?

Accepted Answer

Leveraging Playwright, Fayeblade supports popular web browsers including Chromium (default), Firefox, and WebKit. You can configure the target browser using the `BROWSER` environment variable.

Fayeblade

About

Key Features

Use Cases