Agent panel — soul contract (plan mode, scoped tools, structured events, diffs, checkpoints) #27

Open
opened 2026-06-19 15:35:53 +00:00 by tim.lingo · 0 comments
Member

@will.anderson — the Agent panel (Cowork-style right rail in chat) is built client-side (neuron-ui feat/agent-panel). These pieces need soul-side support. Full contract in the PR: docs/AGENT-PANEL-SOUL-CONTRACT.md. Priority order:

0. Prerequisite — deploy the fixed agentic soul (issue #25). The panel shows live activity but the agent can't reliably act until the merged fixes (#17–#22, #58) ship in the running binary.

1. agent_workspace_root scoping (PR #23, open). Scopes file tools to the panel's chosen folder. Needs your build + the design call (.el guard vs el_runtime.c).

2. Plan-mode endpoint for "Plan before running" (default-on): POST /api/chat {mode:"plan"}{plan:{steps:[...]}}, returns a structured editable plan WITHOUT executing. (Client-side fallback possible, but native is cleaner.)

3. Structured activity events on the agentic path (step_id, tool, args, status, summary) so the panel can show per-step status + will-do vs did.

4. Diffs for file-writing tools (before/after, per-file accept/reject) — the #1 user-loved feature in the competitive research.

5. Checkpoints / rewind — per-step snapshot + restore endpoint.

1–2 unlock the most user value; 4–5 are the heaviest lift. Nothing here blocks the v1 panel (autonomy, live activity, inputs/outputs, settings) which works now.

@will.anderson — the Agent panel (Cowork-style right rail in chat) is built client-side (neuron-ui `feat/agent-panel`). These pieces need soul-side support. Full contract in the PR: `docs/AGENT-PANEL-SOUL-CONTRACT.md`. Priority order: **0. Prerequisite — deploy the fixed agentic soul (issue #25).** The panel shows live activity but the agent can't reliably act until the merged fixes (#17–#22, #58) ship in the running binary. **1. `agent_workspace_root` scoping (PR #23, open).** Scopes file tools to the panel's chosen folder. Needs your build + the design call (`.el` guard vs `el_runtime.c`). **2. Plan-mode endpoint** for "Plan before running" (default-on): `POST /api/chat {mode:"plan"}` → `{plan:{steps:[...]}}`, returns a structured editable plan WITHOUT executing. (Client-side fallback possible, but native is cleaner.) **3. Structured activity events** on the agentic path (step_id, tool, args, status, summary) so the panel can show per-step status + will-do vs did. **4. Diffs** for file-writing tools (before/after, per-file accept/reject) — the #1 user-loved feature in the competitive research. **5. Checkpoints / rewind** — per-step snapshot + restore endpoint. 1–2 unlock the most user value; 4–5 are the heaviest lift. Nothing here blocks the v1 panel (autonomy, live activity, inputs/outputs, settings) which works now.
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: neuron-technologies/neuron#27