Open source Grok Bot alternative, Bring your own agent and subscription: message Claude Code, Codex, Gemini CLI, Cursor, Copilot and 40+ AI agents as bots on your own computer, from iPhone, Mac, Windows, Linux or terminal. Agent-agnostic and free. Also a Muse and Dots alternative. Built in Rust.
Codync documentation
Current documentation describes the checked-out implementation. Index last checked against the tree: 2026-10-19. Source review, a passing build, local integration tests and production acceptance are different checks; a feature documented here is not a claim that its deployed service has been verified.
Start here
| Task | Read |
|---|---|
| Find a module or decide where a file belongs | File structure |
| Understand clients, host, cloud and data ownership | Architecture, conversation runtime |
| Work on the macOS, Linux and Windows desktop app (Electron) | Desktop app, desktop styles |
| Build, install, restart and run checks | Development, Codync Dev beside production |
| Write or refactor code in any module | Clean code |
| Change something users see or do (keep the codync.dev manual current) | User docs |
| Change an iPhone or desktop screen or button | UI conventions |
| Change the composer | Composer behavior and checks |
| Ship app and host updates | Updates, client and host compatibility |
| Plan and build Android | Android plan, Android status |
| Test a phone over Cloudflare instead of LAN | Cloudflare testing |
| Configure dev/main or deploy the services | Environments and deployment |
| Run the host on a Linux server or cloud VM | Linux servers |
| Reproduce or check something on Windows (UTM VM) | Windows testing |
| Set up accounts, approvals or desktop SSH | Accounts and SSH |
| Check connectors against live services | Connector verification |
| Change transport or cryptography | Remote protocol and shared vectors |
| Review an issue or pull request | Issue and PR review (the review-issue-pr workflow) and its security check |
| Patch around an agent adapter's bug, or check whether upstream fixed one | ACP adapter workarounds |
| Look into errors or failed turns users hit | Usage analytics, iPhone crash tracing, investigations |
Features
- Lead bot (every computer's own bot: on top, checks in, speaks first on calls)
- Chat messages
- Group chats and replies
- Bot-to-bot collaboration
- codync-network (your computers' network: bots message bots on the user's other computers)
- Cloud assistants (ChatGPT, Claude and others message the bots through the Codync connector)
- codync-network and cloud assistants: design (why iroh, connectors and relays, trust, addresses, quiet letters, the connector's choices, next steps)
- Context and memory
- Usage limits (which agents show, how each one is read, and which can't be)
- Bot memory and compaction (design; storage, gate and dreaming built, compaction to come)
- Bot memory research (files vs. database, embeddings, open-source systems, harness instructions)
- Bot workspaces
- Bot import (agents from a Grok Bot export file become bots)
- Agent fallbacks (the next agent carries a turn on when the bot's own runs out of usage)
- Routines
- Dev servers (programs a bot keeps running: the host runs them, every client shows their port)
- Voice calls
- iOS Shortcuts
- File attachments
- Artifacts and the Library
- Remote screen and computer use
- Computer identity and list ordering
- Notch island (desktop)
- Extensions and agent setup
- Connector setup and credentials
- Usage analytics and error tracking
- Widgets, Live Activities and onboarding
- Notifications and background Live Activity updates
Plans
- Optional sign-in (signed-out phones, computers in no account, the relay only within an account; built, the rollout steps remain)
- Windows remote screen (a screen helper for Windows; planned)
- Android parity and acceptance
- codync-network and cloud assistants: what's left (network screens in every app, access rules, Codync's own relays, and the rest, in build order)
- Harness memory (the switch that keeps a harness's own memory on; a choice of it instead of Codync's, planned)
- Error tracking detail (symbolicated iPhone crashes and sessions, built; consented problem reports, proposed)
Investigations
Production signals (PostHog errors, failed turns) traced to a root cause, newest first. Dated records: the fixes they name have shipped or are listed as open.
- PostHog error triage, 2026-11-03: Android crash on a dropped connection, blank desktop windows, iPhone voice call crash
- Claude reported signed in on Windows while signed out, 2026-10-20
- PostHog error triage, 2026-10-19: host panics, desktop and iPhone crashes, failed Claude turns
- npm agents failing to start on Windows, 2026-10-14
Documentation layout
docs/
├── README.md # Navigation and maintenance rules
├── architecture/ # Current boundaries, data flow and file ownership
├── features/ # Current behavior and implementation entry points
├── design/ # UI rules, system integration and design write-ups for larger features
│ └── reference/ # Reference screenshots the designs follow
├── guides/ # Build, configuration, testing and deployment steps
├── reference/ # Wire contracts, shared executable fixtures, adapter workarounds
│ └── fixtures/
├── plans/ # Work planned or in progress, not released yet
├── investigations/ # Dated root-cause records of production errors
├── archive/ # Dated plans/audits; never current instructions
└── screenshots/ # Images the repository README shows
Service-local entry points remain in cloud/README.md and relay/README.md. Repository-wide development rules remain in AGENTS.md and CLAUDE.md.
Maintaining these docs
- Describe implemented behavior in the present tense. Label proposals and unverified deployment steps explicitly.
- Keep one authoritative explanation per topic; link to it from related pages. Link to source for schemas and public APIs instead of copying entire definitions that drift.
- Use lowercase, kebab-case filenames and relative links. Source paths written in backticks are relative to the repository root.
- When moving a document, update inbound links, code comments, test fixture imports and CI path filters in the same change.
- Check local links and run the affected fixture tests. Keep generated images/build logs under
build/or a temporary directory, outside the documentation tree. - Record verification scope and limitations. Do not turn an old test report or historical audit into a current passing status.
Archived plans and audits retain earlier decisions and review context. Their original dates, line numbers and proposed APIs are historical.