Continuous Memory
Every session starts where the last one stopped.
Every agent picks up where the last one left off
- Add retry helpersession 7f2c · 9d1e0a7 · 3 declared reads
- Document backoff limitssession 41ab · 2c5f9e1 · 2 declared reads
- Transcript: 38 turns, 1 redacted
$ yoneda context # YonedaRepo context for this clone main at 4be81c2 (log version 215). ## Landing rules - approvals required: 1; required checks: test … ## Open change requests - #12 Retry on 503 [branch retry at 9d1e0a7, by jane]
How it works
- Each commit keeps its sessionThe agent CLI, the model, a summary and the session id, with the files the session declared it read.
- Transcripts, redactedPrompts, tool calls and replies, with credentials replaced before storage. Anyone who can read the repository can read them.
- Context at the start
yoneda contextprintsmain’s head, the landing rules, recent sessions, open Landings and symbol contracts, within a byte budget. - Set up once
yoneda setupinstalls hooks for popular coding agents, so each session starts with the context and records itself on its commits.