AGENT SYSTEMS · PUBLIC AND PRIVATE
Nexus Prime and tetris.codes have public install paths. Grain, NXL, and Phantom are in private development; availability is confirmed against the workflow, access, and review requirements.
memory and control for coding agents
When coding agents switch tools or sessions, Nexus Prime keeps shared memory, file scope, approvals, and handoff records in one local-first control plane.
npm i -g nexus-primeUse it when coding-agent work loses decisions, scope, or review state between sessions.
compresses repeated context
Long agent sessions resend the same prose, code, and traces. tetris.codes compresses those channels before the model call and leaves fallback behavior visible when compression cannot be used.
curl -fsSL https://get.tetris.codes | shUse it when repeated context is consuming the working window in long coding-agent sessions.
defines the handoff
Grain describes the fields, required checks, and record each workflow step must pass forward, so teams do not rebuild the handoff for every integration.
Use it where work changes systems or owners and the required handoff is currently implicit.
runs repeatable loops
NXL records how repeatable agent work runs, supports deterministic replay, and keeps planning state available so teams can inspect failures before changing the loop.
Use it where a repeated agent loop needs inspectable execution and a reliable replay path.
keeps work on course
Phantom keeps multi-step agent work attached to its goal, current owner, checkpoints, and review history as it moves across time and workers.
Use it where work spans multiple steps, owners, or review cycles without a durable operating record.
NEXT ACTION
We will identify the smallest useful system, the decisions it must leave with people, and the evidence each handoff should keep.