This60：哪個編碼智能體工作階段需要你優先處理？

When you return to several coding-agent sessions, each may be in a different state. One has finished, another needs a decision, and a third has stopped after a failed test.

You can open each session and ask what happened. Before investigating a particular task, though, you need to decide which task needs you first.

Ask each agent to record a short update in its existing This60 task before stopping. You can then review the task descriptions together and choose which session to open.

I develop This60. The examples below are fictional. This article was drafted with AI assistance and reviewed by the developer.

Ask for a useful stopping-point update

Suppose you have three tasks, each linked to an agent session:

• Fix settings persistence: the agent made a change and ran the relevant tests. It needs your review.
• Update the import process: the agent needs you to decide how duplicate records should be handled.
• Add an export option: the agent stopped because a test failed and needs further investigation.

The full conversations contain the details. The task updates need only explain the outcome and the next action.

Give the agent this instruction, using the task's actual file and identifier:

Before stopping, update this task's existing .this60/ file. Record what you completed, what remains unresolved, and the next action. State clearly if you need a decision from me. Mark the task complete only if its acceptance criteria are met. Commit and push the task update to main, following the repository's instructions and preserving other work.

Writing the update is an explicit instruction. This60 does not infer it from the conversation. The update must reach GitHub before the app can retrieve it.

Review the tasks before opening the sessions

After those updates reach GitHub and This60 refreshes, read the task descriptions in the app.

For the import task, the update might say:

Decision needed: Should an imported record replace an existing record with the same identifier, or should we skip it? Implementation is paused pending that choice.

For the settings task:

Review needed: Changed how the setting is saved. The settings persistence tests pass. Next action: review the change and check that the setting survives an app restart.

Answer the import question first because it is preventing further work. Then open the settings session to review its changes. Use the linked sessions for explanations, evidence and follow-up instructions.

Open the session that needs you first

The time saving is in choosing where to intervene. Instead of opening every session to ask for its status, review the updates in This60 and open the session that needs your attention.

A blocked decision, a change awaiting review and an unfinished investigation call for different responses. Reading those outcomes together lets you choose the next action before entering a conversation.

This workflow is for people managing several independent sessions. If you have one active task, or already know which session to inspect, opening that session directly is simpler.

Keep the updates trustworthy

A task update should describe what the agent actually did. A statement that tests pass should identify which tests ran. Complete should mean the task's requirements were met, rather than that the agent stopped responding.

An update describes a particular stopping point. If work continues afterward, the agent needs to update the task again. Otherwise, the description becomes stale.

The session remains the place to inspect the work in detail. The task update is a short explanation of where things stand and what should happen next.

Try it across your active tasks

If you regularly return to several agent sessions, ask each agent to record its stopping-point update. Then review the descriptions in This60 before opening a session.

The practical test is straightforward: can you choose which task needs you without asking every agent for a status report? When you inspect the work, do the updates accurately describe it?

This60 stores repo tasks in Markdown under .this60/ and brings tasks from connected repositories into the app. That gives you a place to review these updates across projects. The workflow depends on agents writing useful updates; it is not automatic monitoring of their conversations.

Get This60 for Mac, iPhone or iPad. Free covers three repos, three recurring items and three task dependencies. Agent subscriptions are separate. This60 is also available on Android; there is no browser version.

See the illustrated Mac setup walkthrough.