Customer.ioAutomate Messaging Everywhere — Startups Get 12 Months Free
Promoted
Superset is a turbocharged IDE that allows you to run any coding agents to 10x your development workflow.
- Run multiple agents simultaneously without context switching overhead
- Isolate each task in its own sandbox so agents don't interfere with each other
- Monitor all your agents from one place and get notified when they need attention
- Review changes quickly with built-in diff viewer and editor
Wait less, ship more.
This is the 3rd launch from Superset. View more
Superset Mobile
Launching today
Orchestrate coding agents from your iPhone. Pick up the same workspaces from your computer, review diffs, and merge PRs away from your desk. Works with Claude Code, Codex, and other terminal agents.
Included with Superset Pro. First month free with code MOBILELAUNCH.
Free Options
Launch Team / Built With
Conductor
Claude Code
Superset
@soloships You mean credentials for Claude, codex ? We use your already logged in creds of Claude or all agents we support
Superset
@soloships you auth with your claude/codex or whatever model provider account you have
How does the diff view hold up on a phone when the agent changes a bunch of files?
Superset
@dylan_friddle12 We recently launched a pretty good PR view that makes reviewing changes across multiple files much easier, even on a smaller screen. It gives you a much cleaner way to go through the overall changes, and we're continuing to improve the flow to make the review experience even easier on mobile.
Is there a way to prevent two agents from unknowingly solving the same task?
Superset
Superset
@michelletran luckily you could have a session that useses the superset cli to check what other workspaces are working on and make sure they are solving the same task
Having separate sandboxes makes sense for experimentation. What happens when two agents make changes to the same part of a codebase?
Superset
@alheri_murya For most of the work, Git worktrees provide really good isolation between agents. Each agent can work independently in its own worktree without affecting the others.
The tricky case is when two agents need to modify the same file or the same part of the codebase. If they're operating in the same worktree, there can be some back-and-forth between the agents as they see and react to each other's changes. Otherwise, we mostly rely on Git to handle the integration - separate branches make it straightforward to merge the changes and resolve any conflicts that arise.
Can you see the current status and recent activity of every agent without opening each session?
Superset
@austinphillips we have a pretty good list view where you can see the status of all the agents that are running and ran, I think it's a good idea to show the last message of the agent here so that you can quickly get a view
The idea of 100s of agents changes the workflow quite a bit. What is the best way to organize them once several projects are running at the same time?
Superset
@mariusholm I'd start with one project per repo and one clearly named workspace per task. That gives each task its own branch and files, and you can pick up those same workspaces from your phone.
I'd probably use this just to check whether the agent is still running when I'm away from my laptop.
@aria_taylor yep even that is super useful! I also used it instead of a laptop for my recent flights 😁
Superset
@aria_taylor definitely, it surprisingly nice to be able to unblock my agent from the grocery store l