Skip to content
Tanzanite Docs

Chat, plans & goals

You work with an agent in Chat, in the sidebar. There is no separate place for “autonomous” agents: a quick question and a long-running task start the same way, and the agent does as much work as the request needs.

Chat

Section titled “Chat”

Type into the composer — Ask anything or give the agent a task… — and send. Opening Chat from the sidebar clears the active project for general, project-free conversation; pick a project in the sidebar to work inside it with that project’s files and tools.

The composer also sets how this message runs:

  • The autonomy tier — how much the agent may do without asking: Observe (read-only), Draft (holds its outputs for your approval), Execute (runs within guardrails and asks only before destructive actions) or Full Auto (no approval gates; cost guardrails still apply).
  • The model, thinking and web search for this message.

Plans

Section titled “Plans”

Each conversation is a plan. The agent works through it in rounds: it reasons, calls tools, produces artifacts, and reports back — and a follow-up message continues the same plan. Your conversations are listed in the chat history panel.

Goals

Section titled “Goals”

A plan can carry goals — the things that must be true for the work to count as done. They appear in the Goals panel at the top of the plan with a done/total count, and you can add one yourself with Add goal. This plan will not finish while a goal is open: the agent has to meet each one, or say honestly that it is blocked.

Goals are not the same as the agent’s tasks (Show tasks), which are its own working checklist and never hold a plan open.

Subagents

Section titled “Subagents”

For larger work the agent can spawn subagents that run in parallel, each scoped to part of the problem, then report back. The plan tree shows them live; the agent tree explorer shows each one’s status and lets you pause or cancel a node that went off track.

Approvals and control

Section titled “Approvals and control”

You stay in control of a running plan:

  • Approve sensitive tool calls before they execute — Allow Once, Allow Always for that kind of action, or Deny. How often you are asked depends on the autonomy you chose.
  • Answer the questions the agent asks in a prompt above the composer.
  • Pause and Resume at any time.
  • Redirect by typing while the plan runs — the composer reads Redirect the agent….
  • Stop Agent when you’re done. A stopped plan can be picked up again by sending a message.

Spend

Section titled “Spend”

Every plan tracks its token usage and cost as it runs. The $ chip in the plan header sets a Plan spend limit — a Hard limit or a Target — for that plan.

Rich output

Section titled “Rich output”

Agents can produce and render markdown, code, images, video, HTML, and PDFs inline through the renderer registry, and can generate media with built-in tools. Open an artifact and Generate share link to share it; your links are listed under Shared in the sidebar.

Next steps

Section titled “Next steps”