Skip to content

The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu

Merge remote-tracking branch 'origin/main' into claude/gallant-curie-cqv4rr-g-copilot

Claude2880ee333a0c
diff --cc cli/beacon/internal/handoff/resume_test.go
index 5d34217d,39c4d7f7..d6b66db6
--- a/cli/beacon/internal/handoff/resume_test.go
+++ b/cli/beacon/internal/handoff/resume_test.go
@@@ -24,7 -24,8 +24,8 @@@ func installed(names ...string) func(st
}
}
- var allRuntimes = installed("claude", "codex", "opencode", "cline", "pi", "prime-agent", "omp", "gemini", "qwen", "kiro-cli", "agy", "devin", "muse", "openhands", "goose", "copilot")
+ var allRuntimes = installed("claude", "codex", "opencode", "cline", "pi", "prime-agent", "droid",
- "omp", "gemini", "qwen", "kiro-cli", "agy", "devin", "muse", "openhands", "goose")
++ "omp", "gemini", "qwen", "kiro-cli", "agy", "devin", "muse", "openhands", "goose", "copilot")
// resumableSession is a session whose directory and session file both exist.
func resumableSession(t *testing.T, harness, id string) Session {
@@@ -80,7 -82,7 +82,8 @@@ func TestPlanResumeStartsANewSessionInE
{HarnessCline, "cline", []string{"--tui", "--auto-approve", "false"}},
{HarnessPi, "pi", []string{"--"}},
{HarnessPrime, "prime-agent", []string{"--"}},
+ {HarnessFactory, "droid", nil},
+ {HarnessCopilot, "copilot", []string{"-i"}},
{HarnessOhMyPi, "omp", []string{"--approval-mode=always-ask"}},
{HarnessGemini, "gemini", []string{"--approval-mode", "default", "--prompt-interactive"}},
{HarnessQwen, "qwen", []string{"--approval-mode", "default", "--prompt-interactive"}},
diff --cc cli/beacon/internal/handoff/runtimes.go
index eb3ba334,8a699d9f..c2118681
--- a/cli/beacon/internal/handoff/runtimes.go
+++ b/cli/beacon/internal/handoff/runtimes.go
@@@ -7,7 -7,7 +7,8 @@@ import
"github.com/asymptote-labs/agent-beacon/cli/beacon/internal/claudesession"
"github.com/asymptote-labs/agent-beacon/cli/beacon/internal/clinesession"
"github.com/asymptote-labs/agent-beacon/cli/beacon/internal/codexsession"
+ "github.com/asymptote-labs/agent-beacon/cli/beacon/internal/copilotsession"
+ "github.com/asymptote-labs/agent-beacon/cli/beacon/internal/factorysession"
"github.com/asymptote-labs/agent-beacon/cli/beacon/internal/opencodesession"
"github.com/asymptote-labs/agent-beacon/cli/beacon/internal/pisession"
"github.com/asymptote-labs/agent-beacon/cli/beacon/internal/primesession"
@@@ -54,7 -54,7 +55,8 @@@ const
HarnessCline = clinesession.Harness
HarnessPi = pisession.Harness
HarnessPrime = primesession.Harness
+ HarnessFactory = factorysession.Harness
+ HarnessCopilot = copilotsession.Harness
// Runtimes Beacon starts but whose sessions it reads only from the runtime log.
HarnessOhMyPi = "omp"
@@@ -162,24 -162,21 +164,39 @@@ var runtimes = []Runtime
NewSession: func(prompt string) []string { return []string{"--", prompt} },
},
},
+ {
+ Harness: HarnessFactory,
+ Label: "Factory Droid",
+ Aliases: []string{"droid", "factory-droid"},
+ NewSource: func(dir string) Source { return &factorySource{dir: dir} },
+ // Droid's interactive mode asks before it acts. Beacon never passes --auto, so a session it
+ // starts keeps asking.
+ Command: &runtimeCommand{
+ Executable: "droid",
+ Resume: func(s Session) ([]string, bool) { return []string{"--resume", s.ID}, true },
+ // The prompt is droid's positional argument. It starts with a word that is neither an
+ // option nor one of droid's subcommands, so it is read as the prompt.
+ NewSession: func(prompt string) []string { return []string{prompt} },
+ },
+ },
+ {
+ Harness: HarnessCopilot,
+ Label: "GitHub Copilot CLI",
+ Aliases: []string{"copilot", "copilot-cli"},
+ NewSource: func(dir string) Source { return &copilotSource{dir: dir} },
+ Command: &runtimeCommand{
+ Executable: "copilot",
+ // --resume takes an optional value, so the id is bound to it with = rather than left to
+ // be read as the next argument.
+ Resume: func(s Session) ([]string, bool) { return []string{"--resume=" + s.ID}, true },
+ // -i starts the interactive TUI and sends the prompt as its first message.
+ NewSession: func(prompt string) []string { return []string{"-i", prompt} },
+ // Copilot asks before each tool call unless COPILOT_ALLOW_ALL=true, which also trusts the
+ // directory, or COPILOT_PLAN_THEN_AUTOPILOT, which starts in plan mode and carries the plan
+ // out without waiting. A session Beacon starts never inherits either.
+ Env: map[string]string{"COPILOT_ALLOW_ALL": "", "COPILOT_PLAN_THEN_AUTOPILOT": ""},
+ },
+ },
// The runtimes below keep no session store Beacon reads. Their sessions come from Beacon's
// runtime log, so they always continue from a brief; each can also be the runtime another
diff --cc docs/cli/handoff.mdx
index 838016c6,10295583..ef398248
--- a/docs/cli/handoff.mdx
+++ b/docs/cli/handoff.mdx
@@@ -25,11 -25,11 +25,12 @@@ Sessions come from each runtime's own l
| Cline | `~/.cline/data` | `cline` |
| Pi | `~/.pi/agent/sessions` (or under `PI_CODING_AGENT_DIR`) | `pi` |
| Prime Agent | `~/.prime/agent`, both `sessions` and `session-artifacts` (or `PRIME_AGENT_CODING_AGENT_DIR`) | `prime` |
+ | Factory Droid | `~/.factory/sessions` | `droid` |
+| GitHub Copilot CLI | `~/.copilot/session-state` | `copilot` |
When a Codex thread has more than one rollout file, `beacon handoff` lists it once, under its newest file. Cline can hold the same task both as a CLI session and in its older task history; the CLI session is the copy that is listed. Cline kanban cards are not sessions and are not listed. Prime Agent subagent transcripts, under `session-artifacts`, are listed as subagents of the session that started them.
- `--store-dir <runtime>=<path>` takes the location in the table: for Pi its sessions directory, as `beacon endpoint pi sync --sessions-dir` does, for Prime Agent the agent directory holding both of its roots, and for GitHub Copilot CLI the `~/.copilot` directory that holds `session-state`, as `beacon endpoint copilot sync --copilot-dir` does.
-`--store-dir <runtime>=<path>` takes the location in the table: for Pi its sessions directory, as `beacon endpoint pi sync --sessions-dir` does, and for Prime Agent the agent directory holding both of its roots. For Factory Droid it is the sessions directory, as `beacon endpoint factory sync --sessions-dir` does.
++`--store-dir <runtime>=<path>` takes the location in the table: for Pi its sessions directory, as `beacon endpoint pi sync --sessions-dir` does, and for Prime Agent the agent directory holding both of its roots. For Factory Droid it is the sessions directory, as `beacon endpoint factory sync --sessions-dir` does. For GitHub Copilot CLI it is the `~/.copilot` directory that holds `session-state`, as `beacon endpoint copilot sync --copilot-dir` does.
### Runtimes Beacon starts but does not read
@@@ -129,7 -129,7 +130,8 @@@ There are two ways to resume
| Cline | `cline --tui --auto-approve false --id <id>` |
| Pi | `pi --session <session file>` |
| Prime Agent | `prime-agent --resume <session file>` |
+ | Factory Droid | `droid --resume <id>` |
+ | GitHub Copilot CLI | `copilot --resume=<id>` |
- **Start a new session from a brief.** Otherwise, or with `--agent` naming another runtime or with `--new`, Beacon writes a brief (see `export`) and starts a new session. The first message of that session points at the brief:
@@@ -141,7 -141,7 +143,8 @@@
| Cline | `cline --tui --auto-approve false "<prompt>"` |
| Pi | `pi -- "<prompt>"` |
| Prime Agent | `prime-agent -- "<prompt>"` |
+ | Factory Droid | `droid "<prompt>"` |
+ | GitHub Copilot CLI | `copilot -i "<prompt>"` |
| Oh My Pi | `omp --approval-mode=always-ask "<prompt>"` |
| Gemini CLI | `gemini --approval-mode default --prompt-interactive "<prompt>"` |
| Qwen Code | `qwen --approval-mode default --prompt-interactive "<prompt>"` |
@@@ -158,9 -158,8 +161,10 @@@ Claude Code, Cline and Prime Agent suba
Cline approves every tool call by default. Beacon always passes `--auto-approve false`, so a session Beacon starts never gets auto-approval on Beacon's say-so. You can still turn it on inside the Cline TUI.
- GitHub Copilot CLI asks before each tool call unless `COPILOT_ALLOW_ALL=true` is set, which also trusts the directory, or `COPILOT_PLAN_THEN_AUTOPILOT` starts it in plan mode and carries the plan out without waiting. Beacon removes both from the environment it launches Copilot with (`--print` shows them under `env`), and never passes `--allow-all-tools` or `--yolo`. Copilot sessions are not tied to a directory, but Beacon still starts Copilot in the session's recorded directory.
The same holds for every runtime Beacon starts. Oh My Pi and goose approve every tool call by default, so Beacon passes `--approval-mode=always-ask` to Oh My Pi and sets `GOOSE_MODE=approve` for goose. Where a CLI takes an approval mode, Beacon names the mode that asks (Gemini CLI, Qwen Code, Muse Code, and Devin CLI, whose `DEVIN_PERMISSION_MODE` could otherwise hold `dangerous`), so a user or project setting that approves everything does not carry over. Beacon never passes a flag that turns approvals off.
++GitHub Copilot CLI asks before each tool call unless `COPILOT_ALLOW_ALL=true` is set, which also trusts the directory, or `COPILOT_PLAN_THEN_AUTOPILOT` starts it in plan mode and carries the plan out without waiting. Beacon removes both from the environment it launches Copilot with (`--print` shows them under `env`), and never passes `--allow-all-tools` or `--yolo`. Copilot sessions are not tied to a directory, but Beacon still starts Copilot in the session's recorded directory.
++
The runtime runs in this terminal, in the session's recorded directory. If that directory no longer exists, Beacon stops rather than starting somewhere else; pass `--cwd` to choose a directory. Beacon prints the plan and asks `Continue? [Y/n]` before launching. Without a terminal, it launches only with `--yes`. `beacon handoff resume` exits with the runtime's own exit code.
| Flag | Description |
@@@ -196,8 -195,8 +200,8 @@@ The link event keeps the new session's
Two paths record the link:
- **Live hooks and plugins.** Every runtime whose prompts Beacon captures as they are sent records it: the shared prompt hook (Claude Code, Cursor, Factory Droid, Qwen Code, Kiro, Kimi Code, Devin, Muse Code, OpenHands, Grok Build, DeepSeek Harness, Hermes Agent, VS Code), Antigravity (including the prompt it recovers from its transcript when the prompt hook does not fire), the Cline, OpenCode and OpenClaw plugins, and the Pi, Oh My Pi, Prime Agent and Senpi extensions (`harness.collection_method` `hook` or `plugin`).
- - **Session-store sync.** `beacon endpoint claude sync`, `codex sync`, `opencode sync`, `cline sync`, `pi sync`, `prime sync` and `copilot sync` record it when they read the prompt back from the runtime's store (`harness.collection_method: poll`).
-- **Session-store sync.** `beacon endpoint claude sync`, `codex sync`, `opencode sync`, `cline sync`, `pi sync`, `prime sync` and `factory sync` record it when they read the prompt back from the runtime's store (`harness.collection_method: poll`).
++- **Session-store sync.** `beacon endpoint claude sync`, `codex sync`, `opencode sync`, `cline sync`, `pi sync`, `prime sync`, `factory sync` and `copilot sync` record it when they read the prompt back from the runtime's store (`harness.collection_method: poll`).
-Codex CLI prompts reach Beacon over OTLP and through `beacon endpoint codex sync`, not a prompt hook, so a session continued in Codex is linked by the sync. For a runtime that also has a prompt hook or plugin, a sync can record the same link the hook already did; the two carry different `collection_method` values, as every other event those runtimes report through both paths does. A sync's link has a deterministic `event.id`, so syncing again never duplicates it.
+Codex CLI prompts reach Beacon over OTLP and through `beacon endpoint codex sync`, not a prompt hook, so a session continued in Codex is linked by the sync. The same holds for GitHub Copilot CLI, whose live path is OTLP: `beacon endpoint copilot sync` records the link. For a runtime that also has a prompt hook or plugin, a sync can record the same link the hook already did; the two carry different `collection_method` values, as every other event those runtimes report through both paths does. A sync's link has a deterministic `event.id`, so syncing again never duplicates it.
The marker is a claim made in prompt text, not a verified identity: anyone can type it. `fidelity: observed` records that the marker was seen, not that `beacon handoff resume` wrote it. A native resume keeps the session's own id, so it needs no link.