- Persist chat stars in the operator-session registry (chat_star) so every browser/device shows the same Starred group; migrate old local stars once. - Add a compact pipeline graph shape to list responses and draw a lightweight list miniature; replace the cryptic id/version line with the stage count. - Surface OpenCode form questions as a chat card (chat_answer), replay a pending form to late subscribers, and notify for background questions. - Make the mobile dock's Search cell equal to every destination, keep the tab row visible with 100svh, and let Source use the full pane height. - Let a fresh sign-in auto-connect to its own origin; use a Lax session cookie with Expires so Remember me survives app/link launches. - Keep shipped starters and the skill agnostic: no repository paths, project areas or personal device commands; add Diagnose/Fix and Research starters. - Refresh the installed skill and document the new browser conventions.
2.9 KiB
name, description
| name | description |
|---|---|
| Pipelines | Use and author Pipelines workflows, inspect runs, and recover or deliver project work directly when that is the simpler route. |
Pipelines
Pipelines are reusable workflows for repositories. They are optional: direct work, delegation and a pipeline are all valid routes. Use whichever finishes the task with the least ceremony, and keep work small enough to verify.
Using it
pipelines list shows the registered workflows; pipelines runs shows history.
Start a run with pipelines run <name> "<task>", and inspect it with
pipelines inspect <id>. pipelines wait <id> blocks until it finishes.
A failed run keeps its worktree and commits. Read pipelines inspect <id> --json
before deciding: resume the failed stage (pipelines retry <id>), fix directly,
or continue from the preserved branch.
Authoring
A definition is Markdown: # stage <Name> sections with prompt, configs,
tools, edges, and optional limits/checks/settings. Start from
examples/. Use stage names that describe the work:
Plan · Code · Review · UIReview · Land (Prepare and Survey are
useful variants).
Keep prompts short and objective: what the stage should produce and any real
constraints. The runner enforces turns, tools and limits; prompts do not need to
repeat them. Only # outcome is parsed from output.md; everything else is
free markdown. Use links and memory only when they clarify a handoff.
pipelines validate DRAFT checks a draft; pipelines submit DRAFT publishes a
new immutable version. pipelines help <command> has flags.
Turns and artifacts
Each visit has input.md (the run prompt or previous body), memory.md
(completed turns), output.md, and private/. Every run also has one shared
public/ directory, addressed by its absolute path; files there are visible to
later stages and are the stage's real artifacts. input.md, memory.md,
output.md and session.html are system evidence for auditing, not stage
output.
References
Read only what the task needs:
| Need | Reference |
|---|---|
| Definition syntax and turn files | references/format.md |
| Limits, tools and permissions | references/control.md |
| Stages, parallel work, recovery | references/orchestration.md |
| CLI, storage and evidence | references/operations.md |
| Verification and accounting | references/verification.md |
| Failures | references/debugging.md |
| Delivery and installation | references/delivery.md |
| Harnesses and models | references/harnesses.md |
| Notifications | references/notifications.md |
| Transfer and versions | references/transfer.md |
| Hosting, auth and deployment | references/access.md |
| Queue and work items | references/work.md, references/queue.md |
Ask about real ambiguity, destructive actions or changes outside the request; routine steps of an authorized task do not need another confirmation.