jb/paseo
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

Add detached agents and heartbeat scheduling (#1266)

Browse Source
This commit is contained in:
Mohamed Boudra
2026-06-01 14:07:31 +08:00
committed by GitHub
parent 89ec358d00
commit 7fb3dda20c
13 changed files with 443 additions and 271 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/paseo-handoff/SKILL.md
+5 -3
View File
@@ -12,7 +12,7 @@ Transfer the current task — context, decisions, failed attempts, constraints
## Prerequisites
Read the **paseo** skill — provider for the receiving agent comes from orchestration preferences unless the user names one.
Read the **paseo** skill. Before choosing a provider, read `~/.paseo/orchestration-preferences.json` unless the user explicitly named a provider in this request. Do not create the receiving agent until you have read it.
## Parsing arguments
@@ -29,7 +29,7 @@ The receiving agent has zero context. Include:
[Imperative description.]
## Context
[Why this task exists, background needed.]
[Why this task exists, required context.]
## Relevant files
- `path/to/file.ts` — [what it is and why it matters]
@@ -54,6 +54,8 @@ The receiving agent has zero context. Include:
## Launch
Create the agent via Paseo with a `[Handoff] <task>` title, the briefing as initial prompt, and cwd set to the worktree path if `--worktree`.
Create the agent via Paseo with a `[Handoff] <task>` title, the briefing as initial prompt, `detached: true`, and cwd set to the worktree path if `--worktree`. Leave `notifyOnFinish` omitted unless the user explicitly wants no callback.
Handoff agents are siblings/root agents, not your subagents. They must survive you being archived and must not appear in your subagent track.
Don't wait by default — the user decides whether to follow along or move on. Tell them the agent ID and how to follow along (the paseo skill explains).