Tama / Private release
How this manager works
Tama manages the work. Model providers supply execution.
A stable home for agent state
Tama owns agent identity, instructions, memory, permissions, task records and orchestration. Provider sessions are execution contexts, not the only copy of the agent's state.
A designated conversation
The implemented API path records a designated session and uses it for follow-up work. A new provider session is not silently substituted when the original is unavailable. This is distinct from accessing a conversation created in a consumer app.
Knock and the queue
Knock creates persistent work containing the relevant context. New work waits for the current task to finish. Updated instructions apply through a new task context; this is not a guarantee that they are inserted into an already running turn or every internal model call.
Handoffs
A persistent handoff records source and target agents, task lineage, context, artifact references and the requested action. It preserves Tama's work records for the next agent; it does not transfer hidden model state or guarantee perfect understanding.
Restart and recovery
Queued state is stored by Tama. Work with an uncertain outcome after interruption requires reconciliation before another execution. Same-session continuation across a Tama restart and cancellation of the exact provider turn have been tested. An ambiguous run is fenced for review rather than automatically replayed.
Current readiness
The private BYOK path passed live chat, Knock, canonical data writes and knowledge-review acceptance. Live agent-to-agent handoff execution is not claimed by those tests. No consumer session wrapping, undocumented wake mechanism or automatic session reset is offered.
Updated September 24, 2026