Launched this week
ADE
All your coding agents, synced everywhere, free forever
72 followers
All your coding agents, synced everywhere, free forever
72 followers
Use any coding subscription you already pay for, in one synced app that runs on web, desktop, terminal, and mobile. All your chats stay synced between all ade surfaces. Run agents from your laptop, continue the conversation from your phone at dinner, then later finish it off from another computer by simply using the web client. All subs, all in one place. Fully free and open source!
ADE
The multi-device sync model is what caught my attention — having one session carry across web, desktop, and mobile is the hard part of any self-hosted tool, especially when agents are mid-task. Curious about the auth layer: since you can deploy it yourself and chat history syncs across devices, does the self-hosted version keep everything on your infra with no external calls, or is there a relay or cloud component for the mobile sync? Also wondering how the iOS client handles auth token storage given how aggressive iOS background app management is.
The syncing part is what caught my attention. Most of the agent tooling I've tried assumes one machine, so moving between a laptop and a desktop means rebuilding context from scratch every time.
What actually travels in the sync — just config and sessions, or the accumulated context the agent has built up about a codebase? The second one seems much harder to keep consistent if I have uncommitted local changes on one machine and not the other, so I'm wondering how you draw that boundary.
the "worktrees so agents run in parallel without stepping on each other" part is the piece I'd want to stress test. isolated worktrees solve the during-execution conflict, but eventually those branches have to merge back into the same main. does ADE do anything to flag when two agents touched overlapping files/dependencies across worktrees before you go to merge, or is that still on you to catch in review like any normal set of parallel branches would be?
syncing every coding subscription and chat history through one middle layer is convenient but it's also now holding the keys to all of them at once. if your sync service gets compromised, is the exposure limited to session tokens for each connected tool, or could someone pull full account credentials for the underlying subscriptions?
Congrats on the launch! Picking the same session back up on a different device is the part I did not know I wanted. When you come back to it on your phone, does it show you what the agent got up to while you were away, or do you scroll back and piece it together yourself?