Roost documentation#

Roost gives your AI agents a place to keep working. Each agent has its own purpose, conversation, files, and memory. You run Roost on your own host and connect it to Codex.

Start here#

• Choose a deployment platform — start with exe.dev, or find the right path for your host.
• Read with an agent — plain Markdown, llms.txt, and a deployment prompt.
• Getting started — connect Codex and create your first agent.
• Install and operate Roost — Linux installation, private access, updates, and recovery.
• Agents and memory — shape an agent's behavior and understand what persists between conversations.

Work with your agents#

• Shared Feed — follow publications, personalize stories, and discuss what matters in a shared chronological stream.
• Message threads — keep focused follow-ups alongside the main conversation and react to replies on the web.
• Coding job workspaces — open previews, save feedback, continue workers, and review PRs.
• Coding agents — manage development jobs, task sources, and execution profiles.
• Automations — recurring work, timezones, quiet updates, and run history.
• Delegation — let agents hand a focused task to a specialist.
• Files and approvals — upload inputs, download results, and review actions that need your permission.
• Payments with Link — connect a wallet and approve agent purchases on web and iPhone.
• Dashboards — edit to-do lists, log meals, and check live weather in Dashboard or chat.
• Adaptive views and trackers — focus an existing dashboard by topic or format, with shared views on web and iPhone.
• Shared computer — watch browser work and take control of the desktop.
• Push notifications — receive results and approval requests on your devices.
• Settings and appearance — find controls, preview themes, and choose how replies look.
• iPhone and mobile web — connect the native app or add Roost to your home screen.

Build and operate#

• Development — run from source, contribution conventions, and packaging.
• Public websites — build and host the marketing and documentation sites separately.
• Architecture — application structure, Codex integration, and storage.
• Remote desktop setup — provision a persistent Linux desktop.
• Conversation performance and PWA startup — implementation notes and measured results.

Deployment model#

Roost is a single-user app. The packaged server listens on loopback by default. For remote access, enable native passkey login at your HTTPS address, or use an SSH tunnel or a reverse proxy that authenticates both HTTP and WebSocket connections. Native login is opt-in; existing private-proxy installations can keep their current access controls. The public marketing and documentation sites are hosted separately from the app.

Work runs on the server, so closing a browser does not stop it. Roost and its host must stay running for scheduled tasks and notifications. Agent memory and sessions are stored separately, while the operating-system account, connected accounts, and configured desktop are shared.