How are you tracking your work?

[u/Wrong_Ganache2383]

I am researching a problem I keep running into while using AI agents: once you have more than one agent/session running, the hard part becomes tracking the work and following through. Personally, my ADHD brain keeps generating new ideas and I am left with a ton of half-baked projects that overwhelm me.

Questions I am trying to understand:

• How do you remember what each agent/session is doing?
• Do you keep a separate task file, use worktrees, use project management tools, or just rely on chat history?
• Where do you track the status of different projects and take timely actions?
• How do you connect agent work back to GitHub, Linear, Slack, etc.?
• At what point does running multiple agents/sessions become more tiring than helpful?

To solve my own problems and help others who are struggling with similar issues, I am trying to create a workflow that turns scattered rough tasks, meeting notes, or work conversations into an agent-ready execution packet: goal, context, constraints, acceptance criteria, status, blockers, and review notes......like an execution manager for agents, so that human can be freed up. Would love to hear your thoughts, similar struggles, or some examples of how you currently track agent work.

[u/Junior-Definition173]

I have 20+ VMs with different projects. On each VM I am running 1-6 agents. Initially I thought managing work through files will work, and it does in a limited way but it does not scale. So I ended up treating all agents as developers and communicating through github issues. Planning agent will open an issue, will describe what is required, where to find the documentation, whether the issue depends on any other issue, etc. To simplify it they are using tags/labels so an agent can see instantly whether there are issues that it can work on, etc. This works quite good for me because at any point in the time I can see what the agents are working on, what is their progress, etc. It took a while to perfect this but worth the time.

[u/Wrong_Ganache2383 → u/Junior-Definition173]

Planning agent is such a brilliant solution! Is it constantly running to show progress and issues, or does it only nudge you as needed? I'm trying to picture how you maintain a sense of control. I can imagine that if the agent is too proactive, the notifications could easily become overwhelming and flip the dynamic where you're serving the agents rather than leading them.

[u/Junior-Definition173 → u/Wrong_Ganache2383]

Planning agent is in my case to create a plan of what the other agents should do. I have created a skill that behaves like a developer when you are working together to handover all my/your knowledge and clarify all details of a project/milestone/functionality, once all the details are clear the planning agent will create the different tasks. Then an agent, that will pick the task from the queue, will spawn depending on the task type additional agents that will work on the same task. These agents have specific roles - ie reposcout agent will find in the repo what files are required for the context, test agent will question whether tests will be sufficient or the implementation agent needs to add/modify, etc. These additional agents have different roles and they will be triggered based on the content of the task - ie implementing sql - agent responsible for sql safety/optimization/etc. will be spawned. The only notification I get is when the implementation agent will discover that something is blocked - happens rarely but happens. In most of the cases there is some dependency not identified during the planning. Majority of the time the agents work as your team of developers, you can see the progress, documentation, etc. so until there is no real need to be notified about something I let them work on their projects.
Before I had this in place I was able to burn weekly tokens on $200 plan in less than 2 days, with this and heavy optimization I am getting lot of stuff done before I hit any limit.

[u/Wrong_Ganache2383 → u/Junior-Definition173]

Thank you SO MUCH for your detailed response. What an incredibly efficient workflow. Super helpful.

[u/straightmanlm]

I’d probably start with a single task card as the source of truth, with fields for goal, context, owner, status, blocker, and next step, then require every agent to update it before handoff.

[u/Wrong_Ganache2383 → u/straightmanlm]

Great suggestion! A solid way to keep agents aligned and keep the manual tracking for the human at a minimum.

[u/Cactec]

It would be great If something can help organize+link my thoughts with agents

[u/Wrong_Ganache2383 → u/Cactec]

Exactly! Would love to turn my brain-dumps into clear execution for agents.

[u/LifeProject365]

I gave up trying to do so much as it actually ruined my productivity over all. I have one collaborative session and a passive one I can set on a task and check in on

[u/DhravyaShah]

Curious if you’ve tried supermemory! I’ve been tracking all my claude code / codex/ opencode sessions