stroblmeandClaude Fable 5.1
cc4091166e
Docs / docs (push) Successful in 42s
Playwright Tests / test-playwright (1, 2) (push) Failing after 2m42s
Playwright Tests / test-playwright (2, 2) (push) Failing after 10s
pre-commit / pre-commit (push) Failing after 2m33s
Test Backend / test-backend (push) Failing after 2m48s
Compose Smoke Test / test-compose (push) Failing after 9s
Playwright Tests / merge-reports (push) Failing after 2m17s
A provider set under Settings (OpenAI-compatible; key encrypted in flow-data/ai.json) turns on an Assistant panel in the sidebar. Each turn runs the FastMCP tools in-process as the person chatting, streams the rounds over SSE and keeps one transcript per user. The panel floats on any screen and shares the editor's lane: a settings panel keeps the top half, the chat the bottom. The MCP client is now built once, for the endpoint and the chat. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
8 lines
345 B
Python
8 lines
345 B
Python
"""The assistant: a model driving the MCP tools from inside the dashboard.
|
|
|
|
``config`` is the provider and the key, ``client`` the one call every
|
|
OpenAI-compatible provider answers, ``agent`` the loop between the model and
|
|
the tools. The tools are the MCP server's own, so what the assistant can do is
|
|
exactly what an external agent can do.
|
|
"""
|