Skip to content

The panel moves to its own repository, and the launcher takes Requests - #84

Merged
ALLiDoizCode merged 1 commit into
mainfrom
panel/own-repo
Oct 13, 2026
Merged

ALLiDoizCode merged 1 commit into
mainfrom
panel/own-repo

Conversation

@ALLiDoizCode

Copy link
Copy Markdown
Contributor

What

  • The Omarchy panel (the QML, the manifest, relay-events, mark-seen, request, the demo, five guides and their tests) moves to toon-protocol/spaceturtle-panel, with its history. ADR 0006 records why: omarchy plugin add reads the manifest at a repository's root, so the panel could not move to a subdirectory.
  • What both repositories keep is the contract: the files the agent shares with its Observer. New docs/guide/observing.md describes them for whoever observes; the being-observed skill is reframed around them and no longer calls itself a bar widget.
  • The launcher takes Requests, so an Install needs no panel: spaceturtle ask <text>, spaceturtle persona [--name …], spaceturtle requests, spaceturtle withdraw <id>. They write to the queue the agent's zone mounts.
  • An unattended session leaves last-session (how it ended, Requests answered, apps waiting). spaceturtle status prints it, and notify-send says it on the desktop when there is something for the Observer (SPACETURTLE_NOTIFY names another program; a quiet session says nothing).
  • README, CONTEXT.md, the guides, docs/development.md and .sandcastle/implement-prompt.md describe an agent and a launcher. The README and the first-run guide say where the harness runs: Linux with KVM; the definition alone runs wherever docker-agent and toon run.

Tests

tests/run: 329 checks, 0 failed (run three times; one same-second race in the report was found and fixed by counting against the set of Requests that were waiting at session start). New checks cover ask, persona, requests, withdraw, the report, the notification, a quiet session, a failed session and remove.

After merging

  • The agent definition pins the skill by commit (skills: in agent/spaceturtle.yaml). The skill's text changed here, so the pin should move to the merge commit in a follow-up, as it has before.
  • The panel repository has no factory files (close-linked-issues.yml, .sandcastle/) and no triage labels yet. Its first issue should be reading an Install: the node inside the connector's zone, and the Install's directories under ~/.local/state/spaceturtle/agent/ rather than the bare-node defaults.
  • Not done here: a record of refused orders in the report (needs the session's own output), and relay config --name as a tool for the agent.

🤖 Generated with Claude Code

spaceturtle is an agent for docker-agent and the harness that runs it; the Omarchy panel
was the first iteration, and the repository root was its plugin. The panel now lives in
toon-protocol/spaceturtle-panel, with its history, its demo, its five guides and its tests
(ADR 0006). What stays here is the contract both keep: the files the agent shares with its
Observer, described in docs/guide/observing.md and in the being-observed skill, which no
longer calls itself a bar widget.

So that an Install needs no panel, the launcher writes, lists and withdraws Requests
(`ask`, `persona`, `requests`, `withdraw`), and an unattended session leaves a report of
how it ended, the Requests it answered and the apps that wait, which `status` prints and
a desktop notification says when there is something for the Observer.

The README, the glossary, the guides, the development notes and the factory's prompt
describe an agent and a launcher, and say where the harness runs: Linux with KVM.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@ALLiDoizCode
ALLiDoizCode merged commit ee86097 into main Oct 13, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant