Use Dot to coordinate one software project thread

They tried using Dot as a standing project manager for a software build, but it kept dropping context and missing follow-through.

Done with Dots· Advanced· Oct 2026

What they did
The user set up Dot to run as a long-lived project manager for a large software project. Other agents were already handling messages, file access, task handoffs, and work across different models and command-line tools, and Dot was meant to keep one session tied together: track status, delegate jobs, nudge people, and route updates. Instead, the connection kept breaking, it forgot earlier setup, skipped ready-to-send tasks, and kept bringing up the same approved questions and blockers until the user had to intervene.
How it went
They say it was not dependable for this kind of orchestration. A standard coding agent they start themselves now handles most of the work with less friction, while comments suggested Dot can time out or lack the control needed for this job. One person did report a smaller workflow where Dot reads a repo log in GitHub and updates a Notion kanban.
Tips
This kind of setup seems to need strong memory and reliable handoffs, so test it on a small workflow first. If you use it for coordination, build in frequent check-ins and expect to step in when blockers repeat.

Try it yourself with Dots

Act as my persistent project manager for [project name]. Keep a single running thread for the project, summarize what is done, what is blocked, and what should happen next, and check back with me on a [daily/weekly] cadence. If you need to assign work to another agent, message someone, change the repository, or send anything outward, first show me the exact action plan and wait for my approval before proceeding.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on reddit.com ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.