Melvin StroblandClaude Opus 5.5 75e257d9e4 Assistant node, and the Control tab as one conversation (openpanel V5) ...

run_turn takes its tools, system prompt and tool caller; the chat passes the
MCP tools as before. The assistant node offers one tool per wired target,
reads its other inputs as context, streams its reply a sentence at a time,
warms the provider on `listening` and says so when the provider is not there.
Completions share the per-server HTTP client. wren replies when nothing reads
`unhandled`, stt shows a note when nothing was heard. /ai/control lists one
conversation per entry node with the messages to watch.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ljdk7nDaguh9Uhi3zhcSjn

2026-10-19 23:23:25 +02:00

..

dashboards.md

Voice nodes (openpanel V4): stt, tts, wren reply/unhandled, socket publish

2026-10-19 21:34:02 +02:00

flow-editor.md

Capability report: PUT /devices/{id}/report, a Capabilities section, offline devices degraded

2026-10-16 17:37:49 +02:00

index.md

Assistant node, and the Control tab as one conversation (openpanel V5)

2026-10-19 23:23:25 +02:00

operations.md

Modules resolve the manifest with uv pip compile before syncing, so listed packages bring their dependencies

2026-10-15 17:06:20 +02:00

portal.md

A node's worker label is worker, so a device is only a paired one

2026-10-16 16:56:05 +02:00