Merge main into run token usage branch
This commit is contained in:
+26
-18
@@ -153,7 +153,7 @@ pipelines edit # fuzzy pipeline selection
|
||||
pipelines edit "bug fix" # ask the harness what to change
|
||||
pipelines edit "bug fix" "Add a review step"
|
||||
pipelines new "release notes" "Summarize changes and notify my phone"
|
||||
pipelines new "Add a feature" --template task
|
||||
pipelines new "Add a feature" --template feedback-loop
|
||||
```
|
||||
|
||||
`new` opens the configured harness (Pi or OpenCode; host by default, or
|
||||
@@ -214,27 +214,21 @@ is not ownership (the kernel lock is). This is a local-filesystem lock, not a
|
||||
distributed lease; hard-link database aliases and filesystems without reliable
|
||||
advisory locking are unsupported.
|
||||
|
||||
Use `:templates` for four simple, manual-only starters: task, review, research,
|
||||
and plan/implement/review. **Submit template** (`s` or Enter) asks for a
|
||||
Use `:templates` for the four manual-only examples, read in order: one stage,
|
||||
two stages, a feedback loop and a human decision (`examples/README.md`). A
|
||||
brand-new database already holds them as ordinary pipelines; the server seeds
|
||||
them once and never again, so removing them or upgrading never brings them back.
|
||||
**Submit template** (`s` or Enter) asks for a
|
||||
name without opening an editor. Enter saves a retained draft, then a separate
|
||||
confirmation publishes it as a new pipeline. Esc before naming creates nothing;
|
||||
Esc at publication keeps the draft. **Customize** (`e`) opens the editor picker
|
||||
instead. Both paths inherit the configured default model and preserve existing
|
||||
pipelines/history. The research starter requires configured web search support.
|
||||
Starter stages use goal-appropriate tools: the task worker and the three-stage
|
||||
implementer edit and run checks, the task, planner and review stages may
|
||||
search/fetch official sources only when external knowledge is genuinely needed,
|
||||
the three-stage implementer has no web tools and follows the planner's research,
|
||||
the standalone review stage never edits or runs commands and says so explicitly,
|
||||
and the three-stage reviewer independently inspects the real changes and receives
|
||||
the planner-owned acceptance checks rather than the implementer's summary,
|
||||
approving only when the applicable acceptance checks were independently observed
|
||||
passing and no unresolved substantive issue remains. The task and three-stage
|
||||
templates end in a committer stage that stages the runner's captured changed paths
|
||||
and commits locally without ever pushing; a genuine operator gate is a `type=human`
|
||||
decision stage, never a model stage pretending to approve. Editing a bundled
|
||||
template source changes no installed or published definition; a starter becomes an
|
||||
immutable version only after explicit authoring and publication.
|
||||
pipelines/history. Only the stages that make the requested change (`implement`,
|
||||
`act`) may edit; the others read, and the loop's reviewer also runs read-only
|
||||
checks. No example commits, pushes or deploys. A genuine operator gate is a
|
||||
`type=human` decision stage, never a model stage pretending to approve. Editing a
|
||||
bundled template source changes no installed or published definition; a template
|
||||
becomes an immutable version only after explicit authoring and publication.
|
||||
|
||||
Home's `n` / `:new` and **Customize** (`e`) on a template first ask how to author the new
|
||||
pipeline: **nvim** opens a retained Markdown draft file, or a configured harness
|
||||
@@ -477,6 +471,20 @@ sessions pipeline runs create. The protocol types are:
|
||||
for the run that owns them. The list is fail-closed: with no registry and no
|
||||
store it returns an empty list, never the endpoint's whole session list. A
|
||||
session is never marked `busy`: any number of clients may watch and write one.
|
||||
Each row carries `activity` (`turn_running`, `background_tasks`, `seq`): the
|
||||
server's live view of the session. An older server omits it.
|
||||
- `chat_activity` is pushed to every open connection, not only the chat's
|
||||
watchers, when a session's turn starts or ends or its count of running
|
||||
background tasks changes (shells, background commands, Claude Code background
|
||||
Bash and subagents, Codex command executions). The body is `chat_activity`
|
||||
(`session_id`, `turn_running`, `background_tasks`, `seq`). It is sent on those
|
||||
transitions only, never per output chunk. `seq` increases with every change
|
||||
and keeps increasing across a restart, so a client keeps the snapshot (list
|
||||
row or push) with the larger `seq`. Background tasks are counted only while
|
||||
the server observes the session: after a chat's last viewer leaves, the
|
||||
server keeps observing it while its tasks run (bounded like an unattended
|
||||
turn: at most 16 such chats and 6 hours). Once released it reports none
|
||||
rather than a stale count.
|
||||
- `chat_subscribe` attaches a connection to one session's shared live stream (body
|
||||
`session_id`) and replays the session's still-pending approval requests, so every
|
||||
client that watches a session sees every frame any client's turn produces — the
|
||||
|
||||
Reference in New Issue
Block a user