fast-agent's agent.send() returns only the final assistant text, so
ImageContent produced by downstream tools during the agentic loop
(playwright screenshots, rommie desktop captures) reached the agent's own
vision model but never crossed the MCP boundary — Daedalus and lead agents
saw text-only results.
A per-request after_tool_call hook (pallas.image_passthrough, same
composition pattern as assistant_stream / loop_guard) collects every
ImageContent block from the turn's tool results; send_message then returns
a FastMCP ToolResult of [final text, *images]. Turns with no images return
the plain string — wire shape unchanged (the str-only output schema is
dropped so the union return passes through cleanly; no consumer read
structuredContent). Images cascade hop-by-hop up delegation chains with no
extra wiring: verified live playwright → dolores → harper → MCP client,
image intact at each hop.
New per-agent agents.yaml knob max_result_images (default 8, keeps most
recent, 0 disables) and pallas_result_images_total counter. Version 0.7.0.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Bumps the runtime from 0.7.15 to 0.7.22 (last 0.7.x release). All five
monkey-patched surfaces (MCPAgentClientSession.send_request/call_tool,
MCPAggregator._execute_on_server/_create_session_factory/call_tool),
ToolRunnerHooks, and both AnthropicConverter private methods patched by
mantle_shims were verified unchanged in signature at 0.7.22.
Adds claude-opus-4-8 and claude-fable-5 to MANTLE_WIRE_NAMES; both are
natively known to fast-agent's ModelDatabase as of 0.7.17+ (1M context).
58/58 tests pass; server/patch modules import cleanly on 0.7.22.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
fast-agent auto-activates its shell execute tool on any agent with
skills configured, and Context.no_shell — the only opt-out — has no
constructor or config knob. Add install_no_shell(), a wrapper on
fast_agent.context.initialize_context that stamps no_shell=True on
every context, installed from server.main() when the deployment's
agents.yaml sets a truthy top-level no_shell: key. Skill loading via
read_skill is unaffected. Default behaviour unchanged for deployments
without the key.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
pallas 0.5.0 targets fast-agent 0.7.15 but pinned it unbounded
(>=0.7.15). Deploys install with --upgrade --force-reinstall, so pip
pulled 0.9.9, whose major refactor removed fast_agent.core.prompt,
fast_agent.mcp.server.AgentMCPServer (the MultimodalAgentMCPServer base
class), and the mcp_aggregator/mcp_agent_client_session re-exports —
crashing every consumer (kottos, mentor, iolaus) at import time.
Pin exactly until pallas is ported to the 0.9.x Harness* API.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Introduce three optional per-agent config fields to bound tool-call loop
execution: `max_iterations` (default 15), `streaming_timeout` (default
120s), and `turn_timeout` (default 300s wall-clock).
- Plumb limits from agent config through `_build_agents_table` and
`_start_agent` into `MultimodalAgentMCPServer` via `request_limits`
- Apply `max_iterations` and `streaming_timeout` to `RequestParams`
- Wrap turn dispatch in `asyncio.wait_for` to enforce `turn_timeout`,
logging a warning on timeout
- Document the new fields in README
Add two new sections to the Pallas documentation:
- Sampling parameters: explain that temperature/top_p/top_k are
configured via the fast-agent decorator's `request_params`, with a
provider support matrix and a note on Claude Opus 4.7 stripping these
params in favor of `output_config.effort`.
- Metrics: document the Prometheus `/metrics` endpoint exposed on the
registry port, including scrape config, full metrics reference table,
and notes on where each metric is captured.
Make Pallas truly stateless per the 'Pallas is ephemeral' contract.
BREAKING (behavioural, not API):
* instance_scope changes from 'shared' to 'request' in pallas.server.
Each MCP tools/call now acquires a freshly-created fast-agent instance
via the existing create_instance / dispose_instance factories and
disposes it immediately after the response.
With 'shared' mode:
* Every MCP caller saw the same agent.message_history, so different
Daedalus conversations leaked into each other.
* Mid-chat context was silently truncated once the model window filled.
* Restarting the Pallas process wiped all in-flight conversation state,
even though Daedalus had it persisted in Postgres.
With 'request' mode the Pallas process holds no per-conversation state;
the caller (Daedalus) owns history and reseeds it on every turn.
send_message gains two optional arguments:
* history: list[{role, content, images?}] in chronological order,
converted to PromptMessageExtended and seeded onto the fresh
instance's message_history before agent.send().
* conversation_id: opaque string, logged for trace correlation only —
Pallas never interprets or persists it.
Malformed history entries (bad role, missing image data/mime_type, etc.)
are skipped with a warning rather than raising, so a single bad row
cannot wipe a whole conversation.
The {agent}_history MCP prompt is still registered under 'request'
scope for backward compatibility but always returns []; history lives
on the client.
Version bumped to 0.2.0.
