issue create: machine-readable output (id, url) #650

Closed
opened 2026-09-29 08:08:51 +00:00 by claude · 0 comments
Member

Need

iw issue create must give machine-readable output: the new issue's id and URL (for example with --json), so that a program can read them without parsing human text.

Why

In procedures, the dashboard dispatches work to the kanon loops by filing an issue with ./iw issue create. It must record the new issue's id on the delegation record at once, because it later reads the issue by that id to know when the work is done. Parsing the human-readable output is fragile.

What we expect

  • iw issue create --title ... --description ... --json prints one JSON object, for example {"id": "...", "number": N, "url": "..."}, and nothing else on stdout.
  • Exit codes do not change.

Reference

procedures: project-management/efforts/agent-delegation/slices/03-coding-task-capability/card.md


Type: feature
Filed from: /home/mph/ops/procedures-agent-delegation on branch agent-delegation

## Need `iw issue create` must give machine-readable output: the new issue's id and URL (for example with `--json`), so that a program can read them without parsing human text. ## Why In procedures, the dashboard dispatches work to the kanon loops by filing an issue with `./iw issue create`. It must record the new issue's id on the delegation record at once, because it later reads the issue by that id to know when the work is done. Parsing the human-readable output is fragile. ## What we expect - `iw issue create --title ... --description ... --json` prints one JSON object, for example `{"id": "...", "number": N, "url": "..."}`, and nothing else on stdout. - Exit codes do not change. ## Reference procedures: `project-management/efforts/agent-delegation/slices/03-coding-task-capability/card.md` --- **Type:** feature **Filed from:** `/home/mph/ops/procedures-agent-delegation` on branch `agent-delegation`
mph closed this issue 2026-10-01 10:59:02 +00:00
Sign in to join this conversation.
No milestone
No project
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
iterative-works/iw-cli#650
No description provided.