Context that carries over
Stream replies, find earlier messages, steer running work and keep drafts between chats. Tools and subagents have their own place in the conversation.
Open source. Runs on your computer.
Let your agents keep working on your computer. Sign in from a browser or phone, find your computer, and continue the conversation, approvals and work.
macOS · Windows · Linux · Android · Web
A familiar way back to your work.
Your devices decrypt your work.
Device interface illustration · Not live device status
One host. All your screens.
AnyWork connects your browser or Android app to Codex or Harness on your own computer. Your files, tools and working context stay with the host.
Work content is encrypted between your devices. Cloud services receive identity and connection metadata; model requests still use your configured provider.
Pick up an existing chat, follow tool calls and subagents, review files, and keep the conversation moving. Connect to Codex or the official shared Harness host.
The layout now adapts to smaller screens. I also checked the download links and keyboard navigation.
All checks passed
.workspace { − width: 960px; + width: min(100%, 960px); + padding-inline: 24px; + margin-inline: auto; }A little more breathing room.
The layout follows the screen. The context stays with you.
~/workspace $ npm run check ✓ Type check ✓ Keyboard navigation ✓ Responsive layouts ✓ Download links All checks passed ~/workspace $ ▌
Continue the conversation…
Run the project checks
npm run checkExample approval · no command is executed
Interactive illustration · fictional example data
Stream replies, find earlier messages, steer running work and keep drafts between chats. Tools and subagents have their own place in the conversation.
Respond to an approval, inspect a change, or add an image with your own annotations. Browser notifications bring you back when the work needs attention.
Open files, documents, Git changes and a terminal beside your conversation. Each chat remembers its own set of tabs.
Sign in on your computer; remote access turns on after the workspace is ready and can be turned off anytime. On your phone or browser, sign in to the same account, choose that computer and confirm its identity.
First review the introduction, then register or sign in through your system browser. The desktop client prepares the local workspace after sign-in, then turns on remote access by default. You can turn it off anytime.
Open the account page on another device. Your computers appear here with their current status; no server address or access key is needed.
Confirm the computer’s identity and open its workspace. Return to My devices at any time; signing out closes your authorized remote session.
Install the latest AnyWork on your Mac, review its introduction and sign in through your system browser to prepare the workspace.
Remote access turns on when your local workspace is ready. You can turn it off in the console and expand active encrypted connections.
Use the same account on your phone or browser, choose your device, and continue over an encrypted connection.
Run the same service from a portable package. Choose your workspace and connect with the Web client.
# Run from the extracted resources directory
./bin/anywork --web-dir web \
--workspace /path/to/projects \
--codex-scope allInstall the manager on your computer. Take the workspace with you.
Latest release: v0.1.28
DMG installer · macOS 14+ · Ad-hoc signed, not notarized
Windows 10/11 · WebView2 · Installer + portable
GTK 3 + WebKitGTK 4.1 · See distribution requirements
Android 8+ · Signed universal APK · Secure browser account entry
Use the latest desktop version. Review the introduction, sign in and prepare the workspace, remote access turns on by default once it is ready and can be turned off anytime. On your phone or the Web, use the same account to select the computer. The desktop console shows active encrypted connections. Create account
Account remote access is currently qualified on macOS. Android opens the same HTTPS account and device page in a Custom Tab or system browser. Windows and Linux account endpoints require separate validation. See the support matrix
No. Your agent and tools run on your host computer. Your phone or browser connects to that workspace. The host needs to stay awake and connected.
Yes. Codex desktop sharing depends on compatible Unix interfaces and the installed version; Windows uses CLI-backed chats. Harness connects to the original official 0.2.2-rc.1 Web/Desktop host, preserving native session identity and history. Its discovery companion provides the host address; a TUI without a shared carrier cannot be controlled.
Logto manages accounts and minimal device settings. CyberGrid exchanges connection information. Remote conversations, files and terminal content remain encrypted between your devices; cloud services still see necessary connection metadata. The desktop client requires sign-in before preparation or a new browser-open action. Already authorized local browser sessions and the standalone CLI remain independent. Remote access turns on by default after sign-in and preparation; you can turn it off on the computer.
Codex and the official shared Harness host are supported. Harness goal/plan, fork and message editing are not included. Full Codex goal operations need a compatible shared engine; the desktop follower can read and pause goals. Voice, cross-client native queue migration and closed-browser push are not included.