Skip to content
AghataDocs
Open Aghata

Start

Your first task

A guided first run — what you'll see at each stage and why it looks that way.

This walkthrough runs one real task and explains what you’re looking at. It takes about five minutes.

Pick a task with a deliverable

Section titled “Pick a task with a deliverable”

Choose something that produces an artifact, touches no external accounts, and needs one judgment call from you. A good template:

Compare [three options you actually care about] for [your real situation] and write me a recommendation memo. Ask me before assuming my budget.

Send it in Computer mode.

  1. The plan

    Section titled “The plan”

    Aghata replies with a plan before doing anything: the steps it intends, the tools it will use, and what it will produce. If the plan is wrong, say so in plain language — it revises rather than barreling ahead.

  2. Visible execution

    Section titled “Visible execution”

    Open the task from Tasks. Each step streams into the session as it runs: research with sources, code execution, file assembly. You never have to wonder what it’s doing; the answer is on screen.

  3. The pause

    Section titled “The pause”

    Because you said “ask me before assuming my budget,” the session will enter needs input and stop. The question is specific, your answer is recorded in the session, and execution resumes immediately after.

    This is the same mechanism used for approvals (risky actions) and authentication (websites that need you to log in) — the three pause states you’ll see across all of Aghata.

  4. The deliverable

    Section titled “The deliverable”

    The memo lands in Library as a file with the sources it drew from. Open it, check a claim, follow the citation. This inspectability is the point: you should never have to take a deliverable on faith.

  5. What it remembered

    Section titled “What it remembered”

    After the run, Aghata may propose memories — “budget for tooling is around $X/month” — in Memory. Keep, edit, or reject them. What you keep is what future tasks start from, and every entry stays linked to this run as evidence.

If something went wrong

Section titled “If something went wrong”
  • Task never started → check provider readiness in Settings.
  • Stuck on a pause you didn’t expect → open the session; the pause card says exactly what it’s waiting for.
  • Output missed the point → reply in the session with the correction; it revises the deliverable in place.