Repository navigation
The README says which apps wait for the Observer, and the agent reads its Persona back - #85
Merged
Merged
Conversation
… its Persona in a file The store's image is TOON's own, so the README's example waited for the variable, the network and the secret it named, not for being a stranger's image. The README, the agent's instruction and the concepts guide now give the whole rule: an image that is not TOON's own, or any app given a variable, a secret or the network, is held until the Observer approves it. Every app has a network of its own; only an image off the trusted list gets the sandboxed runtime. `toon event query` answers needs_home to an agent key, so the agent could publish its Persona but never read it back. The skill keeps a copy of the published profile as persona.json in the config folder and reads that at the start of a session; the relay's copy is the truth where a tool can read it. The observing guide names the file. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…re it learned fixed tools The pin named a commit from before the skill was rewritten for an agent with no shell, so an Install's agent read 'publish with your usual toon commands' and jq pipelines it could not run. It now names the commit that adds persona.json. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Verifying the README against the agent definition turned up three gaps.
The example did not show what the README said.
ghcr.io/toon-protocol/store:releaseis on toon's trusted list (ghcr.io/toon-protocol/*), so the store waited because the add named a variable, the network and a secret, not because it was a stranger's image. The README, the agent's instruction and the concepts guide now give the whole rule: an image that is not TOON's own, or any app given a variable, a secret or the network, is held until the Observer approves it. Every app has a network of its own; only an image off the trusted list gets the sandboxed runtime.The agent could publish its Persona but never read it back.
toon event queryanswersneeds_hometo an agent key, and the definition has no tool for it. The skill now keeps a copy of the published profile aspersona.jsonin the config folder and reads that at the start of a session; the relay's copy is the truth where a tool can read it. The observing guide names the file.The skill pin was stale. It named a commit from before the skill was rewritten for an agent with fixed tools and no shell (#54), so an Install's agent read "publish with your usual toon commands". It now names the first commit of this PR.
The gate passes locally (329 checks), and
tests/check-agentholds the repinned definition.🤖 Generated with Claude Code