Link Dots to your Claude Code workflow

They wired Dots into a live Claude Code setup so it could pass updates between several coding lanes, but the connection needed tuning.

Done with DotsChatGPTClaude Code· Intermediate· Oct 2026

What they did
The person was already working with many orchestrator and subagent lanes in Claude Code desktop. They then made a quick ChatGPT MCP so Dots could pull information from that active Claude Code session and push messages back into it. They also kept Codex running and relied on Dots as the main session for collecting progress across the lanes with less manual shuttling.
How it went
They said the system needed a few hours of adjustment before Dots began giving useful output. The biggest drawback was shaky reliability, along with uncertainty about whether Dots was really changing things or only creating and messaging Claude Code sessions.
Tips
Expect some setup work before this becomes helpful. If you test a similar bridge, verify two-way communication early and keep an eye on whether actions are actually reaching the intended session.

Try it yourself with Dots

I’m managing several coding lanes in [project folder] and want [Dots] to coordinate with my running Claude Code session. Create a simple connection method, like a shared task file or an MCP-style bridge, so [Dots] can read updates and send replies between the two systems. Before you do anything that sends, deletes, submits, or modifies files, stop and ask for my approval. Then show me how to test both directions, record failures, and confirm whether [Dots] is truly writing changes or only interacting with sessions.

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.