archeious/marchwarden
1
0
Fork 0
Code Issues 14 Pull requests Projects Releases Packages Wiki Activity Actions

M6.2 PI-driven CLI (replaces V1 ask command) #52

New issue
Open
opened 2026-04-08 23:25:03 +00:00 by claude-code · 0 comments
claude-code commented 2026-04-08 23:25:03 +00:00
Collaborator
Copy link

Phase 6 — PI Orchestrator, milestone 2. Closes Phase 6.

Goal

Replace the V1 CLI shim's ask command (which talks to one researcher at a time) with a PI-driven interface (which dispatches the question to all researchers via the PI from M6.1 and shows live progress).

Scope

  • marchwarden investigate "question" — new top-level command that goes through the PI
  • Live progress display via rich's Live / Progress widgets:
    • Which researchers are running
    • Per-researcher status (planning / searching / synthesizing / done)
    • Token spend in flight
    • Discovery events as they fire
  • Final rendering: the PI's InvestigationResult with per-researcher attribution panels
  • The old ask --researcher X command stays for direct/single-researcher debugging
  • Update UserGuide with the new command

Stretch

  • Web UI as an alternative to the rich CLI — separate issue if pursued

Deliverable

  • marchwarden investigate working end-to-end against web + arxiv researchers
  • Smoke test: complex question that benefits from both researchers; show the live progress rendering and the final attributed answer

Blocked by

M6.1

Phase 6 — PI Orchestrator, milestone 2. Closes Phase 6. ## Goal Replace the V1 CLI shim's `ask` command (which talks to one researcher at a time) with a PI-driven interface (which dispatches the question to all researchers via the PI from M6.1 and shows live progress). ## Scope - `marchwarden investigate "question"` — new top-level command that goes through the PI - Live progress display via rich's `Live` / `Progress` widgets: - Which researchers are running - Per-researcher status (planning / searching / synthesizing / done) - Token spend in flight - Discovery events as they fire - Final rendering: the PI's `InvestigationResult` with per-researcher attribution panels - The old `ask --researcher X` command stays for direct/single-researcher debugging - Update [UserGuide](https://forgejo.labbity.unbiasedgeek.com/archeious/marchwarden/wiki/UserGuide) with the new command ## Stretch - Web UI as an alternative to the rich CLI — separate issue if pursued ## Deliverable - `marchwarden investigate` working end-to-end against web + arxiv researchers - Smoke test: complex question that benefits from both researchers; show the live progress rendering and the final attributed answer ## Blocked by M6.1
archeious added this to the Phase 6: PI Orchestrator milestone 2026-04-08 23:25:15 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
feat/step-durations
chore/makefile
feat/depth-presets
feat/per-step-logging
fix/budget-display-clarity
feat/costs-command
feat/cost-ledger
feat/structured-logging
fix/mcp-env-propagation
fix/budget-enforcement
fix/model-default-id
fix/synthesis-truncation
chore/docker-test-env
feat/cli-replay
feat/cli-ask
feat/mcp-server
feat/open-questions
feat/agent-loop
feat/trace-logger
feat/search-fetch-tools
feat/contract-models
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Phase 6: PI Orchestrator
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: archeious/marchwarden#52
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?