flue-agent-console
v0.1.2
Published
A local browser console for inspecting and chatting with any Flue agent.
Maintainers
Readme
flue-agent-console
A local browser console for chatting with and inspecting any Flue agent.
It displays conversation history, streaming text with optional Markdown rendering, reasoning, tool calls and results, runtime advisories, response metadata, and the complete JSON behind every message.
Unofficial developer tool. Not affiliated with or endorsed by the Flue project.
Run with npx
Start your Flue agent, then run:
npx flue-agent-consoleThe command starts the console at http://localhost:5180 and opens it in your browser. Enter:
- Agent server URL — for example
http://localhost:5173 - Agent path — the path passed to
app.route(), for example/agents/my-agent - Conversation id — any caller-chosen durable conversation identifier
- Initial data — optional JSON used when creating a new conversation
By default, the console generates a random conversation id. You can edit it in the browser or set it with --conversation.
Connection configuration is saved in browser local storage.
Pass connection defaults
CLI options prefill the corresponding browser fields:
npx flue-agent-console \
--url http://localhost:5173 \
--agent-path /agents/my-agent \
--conversation demo--path is an alias for --agent-path. You can also pass the agent path as the only positional argument:
npx flue-agent-console /agents/my-agentAvailable options:
--agent-path <path> Flue route mount path
--path <path> Alias for --agent-path
--url <url> Agent server URL (default: http://localhost:5173)
--conversation <id> Conversation id (default: randomly generated)
--port <number> Console port (default: 5180)
--host <host> Console host (default: 127.0.0.1)
--no-open Do not open a browser
-h, --help Show help
-v, --version Show the versionThe console continues running until you press Ctrl+C.
Initial data
Enable Include initial data to show the optional JSON editor. It accepts any valid JSON value, including objects, arrays, strings, numbers, booleans, and null. When it is non-empty, the console parses it in the browser and includes the value as initialData in the first message request that creates the conversation. Invalid JSON is shown as an error and no request is sent. Leaving the toggle off or the editor empty preserves the normal message request.
Flue validates initial data against the agent's declared schema when the conversation is created. The value is immutable after creation; later messages cannot change it. Initial data is persisted with the conversation and is not a secrets channel—do not put credentials, tokens, or other secrets in it.
CORS and authentication
The browser talks directly to the agent server; the CLI does not proxy agent traffic. The agent server must therefore allow the console origin. Flue's localhost development server supports local cross-origin development by default.
For deployed agents, configure explicit CORS and authentication suitable for your application. Avoid exposing privileged production conversations through an unauthenticated local tool.
Develop
Requirements: Node.js 22.19 or newer and pnpm 11.
pnpm install
pnpm devRun the tests and validate the package:
pnpm test
pnpm check
npm pack --dry-runTest the built CLI without opening a browser:
pnpm start -- --agent-path /agents/my-agentLicense
MIT
