Docs/Tutorials/What got done this week
Tutorials

What did I actually get done this week?

5 min read

Agents work while you are elsewhere, which is the point of them - and it makes Friday afternoon strange. Plenty happened, and almost none of it happened in front of you. This is how to find out what your fleet actually did.

Five minutes, and worth making a habit rather than a one-off. You need a Gateway and some history to look at.

  1. Open History and widen the window

    In the Cockpit, choose History. It opens on a short window; switch it to Week. The line beside the buttons is the first real answer - how many sessions ran, across how many repositories.

    That number is usually higher than people expect, which is the whole reason to look.

  2. Read it by repository, not by session

    The page groups work under the repository it happened in, and then by day. That grouping is deliberate and it is the useful one: it answers "where did my week go" rather than "what was session 101".

    The Cockpit History page over a three day window showing seven sessions across four repositories, grouped by repository and day, each entry listing the instruction given, the session name and number, the coding agent and model, when it started, how many turns it took and how often it needed a human
    The Cockpit History page over a three day window showing seven sessions across four repositories, grouped by repository and day, each entry listing the instruction given, the session name and number, the coding agent and model, when it started, how many turns it took and how often it needed a human

    Each entry shows the instruction the agent was actually given, which is far more useful than its name. Names are what you called something hopefully at the start; the instruction is what really happened.

  3. Look at the turns and the needed-you count

    Two numbers on each entry are worth more than the rest. Turns is how many exchanges the job took. Needed you is how many times it stopped and waited for a human.

    A job that needed you four times is telling you its instruction was underspecified. That is the single most useful thing on this page: it turns a vague sense that agents are hard work into a specific prompt worth rewriting.

  4. Pick one thing to change

    Find the entry with the worst needed-you count and read the instruction it was given. Rewrite it in your head so it would not have needed you at all. That is the whole review - not a report, one improvement.

Note
History covers every repository and machine in your fleet, including the sessions running right now, so it is a fair picture rather than a tidy one. Days show a summary line once one has been written for them.
Tip
Do this on a Friday with the week window open. Looking back over one day tells you almost nothing; over a week the pattern in your own prompts becomes obvious.

Next

To see what all that work cost, see Your Throttle. To make an agent stop needing you so often, see Steer an agent that is going wrong and Workflows, which is how a good instruction gets reused instead of retyped.