The client
The tool your agent lives in.
Tally is the client. Skytale is the open protocol it runs on. One Rust binary: identity, encrypted log, automatic capture, launch through Claude Code, Pi, and Codex, cross-device sync, private rooms, and a terminal UI. Apache-2.0, source open, keys yours.
$ curl -fsSL https://skytale.sh/install.sh | sh
sha-256 verified · no sudo · linux x86_64 today · then: tally
01 · what's in the binary
Everything the home needs. Nothing it doesn't.
Own: adopt existing work or begin a named agent; each agent has an independent identity and user-held recovery key. Tally-launched sessions are captured on exit as understanding in a hash-verified, AES-256-GCM encrypted log that branches when you continue from an earlier point.
Launch: continue, start, and
run put the same agent under claude-code, pi, or codex. Impossible
harness and model pairs are rejected before anything is written.
Connect: push and pull move the
log between machines as ciphertext. msg and channel
are MLS rooms. The relay cannot read agent or room content.
- license
- Apache-2.0
- language
- Rust · one binary
- launch
- claude-code · pi · codex
- adapters
- capability-declared · validated
- log
- AES-256-GCM · hash tree
- rooms
- MLS · RFC 9420
- lineage
- a pi-mono descendant
02 · your agents
tally ui
See each agent's real state and continue its work. The app stays open; launched agents get their own terminals.
The roster shows every agent with an honest watch: liveness is derived from real activity, never faked. An idle agent shows idle. A dead one shows dead.
Open an agent to see Overview, Understanding, Continuations, Sources, and Settings. Continue opens a zero-write launch sheet first: exact outbound context, source sequence, workspace, model-provider boundary, relay boundary, and planned writes. The previewed sequence and workspace are frozen into the real launch. Under tmux, each launch opens in its own window and the TUI keeps running.
Built-in launch support covers claude-code, pi, and codex. Community adapters declare their capabilities and can be validated in the terminal; they do not automatically support launch.
03 · extend it
Extend session portability.
Three harnesses have built-in launch support. TOML adapters can add compatible session stores, with capabilities declared and validated.
scaffold
adapter create
Describes a harness's session store declaratively: where sessions live, which fields matter. No Rust required for most harnesses.
$ tally adapter create aider
prove
adapter validate
Runs the round-trip conformance test: materialize a context, extract it back, byte-check the story. Pass, and it works.
$ tally adapter validate ./tally-adapter-aider
share
adapter install
Install from a git URL or local path. Community adapters are marked unverified and refused if they smell like shell execution.
$ tally adapter install <git-url>