Skip to content

Task how-tos

Short, task-focused recipes for the things people do most. Each one assumes you’re signed in with a project open. For concepts behind these steps, follow the links at the end of each section.

Turn a folder on your computer into a cloud project, history included (desktop app only).

  1. In the project list, click Import repo and choose the folder.
  2. If it isn’t a git repository yet, Tanzanite proposes a .gitignore and initializes one before anything is committed.
  3. Pick any extra branches or tags to bring along (the default branch and its full history always come), then click Import history.

The history is uploaded to the git repo Tanzanite hosts for the project, and the folder stays linked as its local mirror. See How cloud agents run for how the mirror keeps both sides in step.

Run an agent automatically on a recurring basis — a morning briefing, a nightly check, a weekly report.

  1. Open Schedules in the sidebar and create a schedule for a Cloud or Device project.
  2. Give it what to do — a prompt for the agent, a script from the project, or both — and the cadence (for example, every morning or each Monday).
  3. Save it. Tanzanite runs it on that cadence and records each fire in the schedule’s run history.

A schedule can also be started by a commit instead of the clock — that is a trigger, on the Triggers tab of the same screen. More in Schedules & Triggers.

A skill is a pack of instructions an agent loads when a task calls for it — your house style, a review checklist, the steps for a fiddly internal process. Your skills live under Skills in the sidebar.

Four ways to add one:

  1. Import from GitHub — paste owner/repo or a GitHub URL. Tanzanite reads the repository’s SKILL.md plus any references/, scripts/, and assets/ files. If a repository holds several skills, the first one found is imported.
  2. Create manually — a name, a description, and the instructions themselves.
  3. Create with AI — describe what you want in a chat and ask the agent to save it; it drafts the skill and adds it to your library.
  4. Import a folder — pick a folder on your computer that already contains a SKILL.md (Chromium-based browsers and the desktop app).

The description matters more than it looks: until an agent decides a skill is relevant, the name and description are all it sees. Write it as what this does and when to use it, not as a title.

Built-in skills appear in the same library marked Built-in — you can attach those, but not edit them.

Adding a skill to your library does not switch it on. Attach it in one of two places, depending on how often you want it:

  • Every chat in a project — Project Settings → Skills. It applies to every new chat in that project, and to sub-agents those chats spawn.
  • Just this chat — click the Skills chip in the message composer and toggle it on.

The chip shows how many skills are active in the chat you have open, and the popover separates on this chat from from project. To silence a project-wide skill for one conversation without removing it for everybody, switch it off in the chip: it shows struck-through with an undo, and the project keeps it.

You can also just ask — “attach the pdf skill to this chat”, “make me a skill for PR reviews”, or “which skills are on right now?” all work in chat.

There is a limit of 24 active skills per chat. Each one costs a little of every message the agent sees, so the cap keeps runs fast; if you hit it, detach something first.

Skills work alongside the harness, which decides which tools an agent can reach. See The Harness.