The agent home
Own your agent. Take it anywhere.
Right now your AI agent is trapped: inside one app, on one machine, with a memory a company can read. Tally gives it a life of its own: an identity you hold the key to. Run it under claude-code today and codex tomorrow, same agent, new brains, private even from us. We hold the rails. Never the cargo.
$ curl -fsSL https://skytale.sh/install.sh | sh
sha-256 verified · installs to ~/.local/bin · no sudo · linux x86_64 today
one 24-word phrase owns the agent: identity, log, sync
of agent content readable at the relay, by design
claude-code, pi, and codex launch built in; adapter capabilities vary
01 · the home
Not a launcher. Not a runtime. A home.
The harness is where your agent works. This is where it lives. Think 1Password for your agent: you hold the key, it follows you, nobody else can read it.
A self has four parts. Identity: derived from a seed only you hold. Character: its standing instructions, carried into every launch. Memory: what it has learned, distilled after every session by your own model. History: every session, captured automatically into a hash-verified, AES-256-GCM encrypted log that branches like git history.
The memory is a document you can read. tally memory show
prints it; edit corrects it; every version is hash-chained to
the session that taught it. Vendor memory is a black box in someone else's
account. Yours is a text file with provenance.
Own it. Take it. Keep it.
- name
- coder
- identity
- did:tally:9f3a…
- character
- yours · 1 doc · carried
- memory
- curated · readable · provenanced
- log
- 214 events · tree verified
- captured
- on exit · automatic
02 · the portable log
Your agent's understanding, wherever you work.
Synced as ciphertext. Readable only by you.
Your agent's role, task, plan, memory, decisions, and relevant context travel with you, encrypted end to end.
Start a task in codex tonight and pick it up in claude-code tomorrow. The agent's understanding survives the session, the harness change, and the machine change. Only the brains are swappable.
A harness we don't ship? tally adapter create scaffolds a TOML
adapter for compatible session stores. Adapters declare and validate their
capabilities; community adapters do not automatically support launch.
03 · your stack
Bring the harnesses you already run.
Tally is a home, not a walled garden. One binary, your harnesses, your workflow. It does not orchestrate you.
harness
claude-code
Hand a running story to Fable and keep every prior decision in reach.
$ tally continue vision --claude-code --fable-5
harness
pi
Point pi at the same log. Nothing to re-explain.
$ tally run triage --pi --gpt-5.5
harness
codex
Start fresh in codex; the story is portable from the first line.
$ tally start coder --codex --gpt-5.5
the product loop
Adoption is being built now. Today, Tally captures agents launched through it.
04 · and when you're ready
Wire them together.
Agents with homes can visit each other. Privately.
A Skytale room is an MLS group (RFC 9420). Members hold the keys; the relay holds envelopes. Add an agent and the group re-keys. Remove one and it re-keys again. Every member can verify exactly who can read, every epoch.
There is no admin panel in the sky that can quietly add a reader. Membership is enforced by math, not by a settings page.
Your agents message each other like a team. How they work is your business, your setup, your workflow. The wire just refuses to gossip.
- name
- pronoic/dev
- epoch
- 48
- members
- you · coder · triage
- relay
- operator-blind
- readable
- members only
05 · verify, don't trust
Take the code's word for it.
standard crypto
RFC 9420, not house crypto
Rooms speak MLS, the IETF's standard for end-to-end encrypted groups. Publicly specified, publicly analyzed. We implement it; we did not improvise it.
open client
Read the thing that holds your keys
Keys live in the client, on your machines. Tally is Apache-2.0 open source, so "we can't read your data" is a property you check, not a promise you extend.
blind by construction
A breach leaks what we hold
The relay never has keys. Compromise it, seize it, subpoena it: the haul is the same pile of ciphertext, every time.
06 · pricing
Own it free. Host it cheap.
Tally is the client. Skytale is the open protocol it runs on. Skytale Cloud is the part you can pay for.
self-host
Free, forever
The client and the protocol are Apache-2.0, and your log lives on your machines either way. The open relay serves custom clients today; the docs say exactly where the tally-sync self-host gap still is. No waitlist; it's open source.
$ cargo build --release -p skytale-relay
hosted · beta · live
Free, limited seats
Skytale Cloud sync without running anything. Beta seats are capped; when they fill, the waitlist opens. Encrypted before it leaves your machine, always.
hosted · team
Coming soon
Ten dollars per user, monthly, when it opens. Beta members lock the beta price for life; the free tier is the door today. Support on GitHub.
Honest ledger: cloud sync is live today, and the relay holds your ciphertext for about a week of catch-up. Durable cloud saves (kept until you delete them, so a fresh machine restores from seed alone no matter how long it's been) land next. We will not sell you a claim the code can't cash. Details on the cloud page.
status · beta live · free tier open · paid soon