Your first task
Lesson 1 of 10 · 4 min 27 s. Pick the project, describe a change in your own words, press Go, follow it on Tasks while an agent works, then read what it did, how long it took and the evidence in its report, and use the change in the app.
Before you start
- You are signed in to the console.
- Your team has a project you can start tasks in, and a machine to run the work. The lesson uses TimeSaver, a time-tracking app for small teams, and asks for a Pause button on its running timer.
Steps
- On the Tasks page, click your project in the list on the left. Tasks now shows only that project's work, newest at the top, and whatever you ask for from here goes into this project.
- Click New Task at the top right. The form opens with the project already filled in.
- Describe what you want the way you'd say it to a colleague. The lesson's description is: Add a Pause button to the running timer, so a break isn't counted in the entry. One sentence of what you want and why is enough: the agent reads the code, finds where the change goes, and checks it with the team's own tests.
- Under the description, check the two choices. The first is how big the piece of work is: a single change is a task, the middle size, which is already chosen. The second is how much you want to be involved; choose Unattended, which lets the agent make its own decisions and come back when it's finished.
- Press Go. You are back on Tasks, and the new task sits at the top of the project's list, waiting its turn behind any other work on the project's machine. You don't need to stay: the line always shows where the work has got to.
- When its turn comes, the work starts by itself and the line's mark changes: an agent has taken it on. It works in its own copy of the project's code, so nothing reaches the rest of the team until the change is finished and checked. A change this size usually takes a few minutes.
- Wait for the mark to change to finished. Before the change was accepted into the code, it passed the team's tests, and the agent tried it in a browser and wrote down what it did.
- Open the task. At the top is your request, word for word, and the mark beside the title says it's done. Everything about this piece of work lives on this page, so its link is all a colleague needs.
- Open Details. Under Outcome, the agent says in plain words what it built and how it checked it, with a link to the change itself.
- Open Metrics. Task run metrics shows what the work took: how long it ran, and how much of that was the agent working.
- Open Artifacts. The agent keeps anything it wrote along the way here; for a change like this that's one document, the Report, which opens below the list.
- Read the Report. It starts with what was built and why, then the checks: the team's tests, the agent's own try of the new button in a browser, and each part of the request with its result and the evidence beside it. It's the document to send when someone asks what was actually done.
- Try the change in the app. In the lesson, TimeSaver's timer now has a Pause button: press it and the clock stops, press it again and the timer carries on in the same entry, with the break left out.
What you learned
- The whole loop is: pick the project, describe the change, press Go, and come back to a finished change.
- A task's line on Tasks shows where the work has got to: waiting its turn, taken on by an agent, or finished.
- What was done is under Details → Outcome, what it took is under Metrics → Task run metrics, and the evidence is under Artifacts, in the Report.
- The agent brings evidence: the team's tests, a check in a browser, and a result for every part of the request.
Next
Next lesson: Writing a request that comes back right.
Related: