Find and Delegate AI Sessions with /ss and /dl

Two things get harder the longer you use OpenCockpit. You remember talking about something — "that session where we worked out the CSRF issue" — but not which project, which engine, or which week. And halfway through a task you spot work that belongs somewhere else — a flaky test in another repo, a job you'd rather give to Codex — and the only option is to stop, open a tab, switch directory and engine, re-explain the context, and remember to check back.

This release adds one command for each.

/ss — find a session from one sentence

/ss the session where we worked out CSRF on the local API

The agent doesn't search your sentence verbatim. It expands it into the keywords that would literally appear in that conversation — both languages for technical topics (跨站 / CSRF), synonyms, the words the assistant would have used — searches, reads the snippets, and replies with 1–3 candidates:

1. **Local API request checks** — cockpit · claude · 2026-09-10
   Walks through the CSRF issue you described, and settles on a fix
   [Open session](/project?cwd=…&sessionId=…)

Click the link and Cockpit switches to that project and opens the session in the Agent panel. The search covers every session Cockpit can read: Claude, Codex, DeepSeek, Kimi, GLM and Ollama, in every project, with no date cutoff.

/dl — hand it off, don't wait

/dl have codex fix the flaky date test in the api project

The agent writes a self-contained brief — the child sees none of your conversation — starts a new session in that directory on that engine, and gets a receipt back immediately:

Delegated **Fix flaky date test** to codex in `/Users/me/work/api` — [open session](/project?cwd=…&sessionId=…)

Then you carry on. The child runs like any other session and shows up unread in your recent sessions when it finishes; open the link any time to watch it or take over. Later:

how did that delegated task go?

The agent finds the receipt — in this conversation, or through /ss from any other — checks the child, and reports running, done, failed or incomplete (stopped or interrupted; open it and continue), with a summary of its last reply.

Where it fits next to subagents

For parallel work inside one repository, Claude's own subagents are still the right tool — and /dl tells the agent so. /dl is for everything else: another directory, another engine, and a session you can open and take over rather than a read-only transcript.

Try it

Update Cockpit, then type /ss with whatever you remember about an old conversation — or /dl something you'd rather not wait for. Details in the Skills docs. For everyday workflows, see Three Ways to Use /dl.

Try it: npm i -g @surething/cockpit · GitHub · Try Online