Tama / Private release

User Guidance - Tama Agent Manager

From your first agent to a clear review of its work.

1. Open your workspace

Choose Sign in and use your workspace token, or Continue with Google when it is configured for your authorized account. Neither is your provider API key. If you do not have a token, ask the operator who gave you access; public account registration is not available.

2. Give an agent a role

Start with the default Tama agent, or choose Add an agent and enter a name and initial instructions. Select its card to see its Board; use the gear for its detail page. Double-click the name to rename it, or right-click for its other actions.

3. Organize instructions and knowledge

Use Instructions to add instruction pages, knowledge pages or folders. Click a title to edit. Right-click to manage recipients, delivery timing, type or location. Parent assignments flow to descendants unless overridden. Review the effective settings after moving a page.

4. Write down the work

To do and Brief belong to the selected agent. Notepad and Grants are shared panels. Editing To do saves the list; it does not itself start execution. When execution is available, Knock queues the request. Knock All addresses agents whose assigned instructions changed.

5. Open a conversation

Ctrl-click an agent to open Code in the current window, or use the right-click menu for a separate Code window. Drag an agent onto a work page to open its chat; if a Code window is open, it switches there. With your API connection and execution service ready, Send queues your message. A draft alone does not start work.

6. Review knowledge changes

Use Dependencies and review on a page to choose its sources and review date. In the editor, select saved text and mark it as outdated. Pipeline lets you review evidence, save a proposal, apply a change or explain why the content still applies. Each decision resolves one task.

7. Check results before retrying

Review the Brief and task result when execution is enabled. If a task has an uncertain outcome, inspect its record and artifacts before approving a retry. Do not assume that an interrupted run made no changes.

Memory and files

The agent detail page shows memory, files, assigned instructions and execution records. The current detail view is compact; it is not a complete file manager. Memory participates in knowledge dependency review. Select saved text and use its context action to mark it for review.

Copy prompt and clones

Copy prompt copies the agent's instructions. Create clone creates a separate identity with its own memory and files; its instructions follow the parent agent. Cloning does not copy or take control of a provider session.

Team, Settings and help

Team is for people and spending, separate from the selected agent. Invitations are not yet available. Usage shows reported token counts and coverage; billed costs must be checked with your provider. Settings contains connections and session locking. Question marks explain the controls; Token-login Lock clears this window's drafts. Google sign-out ends the shared browser session, including its Code windows. Neither cancels work already running.

Updated September 24, 2026