# r5d documentation > Connect your own machines and model access to an agent workspace, with optional deployment to services you choose. - [Welcome to r5d](https://docs.octomerge.dev/index.md): An agent workspace using your machines and model access. - [Sign in](https://docs.octomerge.dev/get-started/sign-in.md): Sign in with Google, Apple or GitHub, add another way to sign in to your account, connect GitHub for repository access, and delete your account. - [Connect a worker](https://docs.octomerge.dev/get-started/add-worker.md): Run project commands on your own machine and select it in r5d. - [Run the worker as a service](https://docs.octomerge.dev/get-started/worker-service.md): Keep a worker running in the background and across reboots with systemd on Linux or launchd on macOS. - [Run a worker in a container](https://docs.octomerge.dev/get-started/worker-container.md): Run a worker with Docker, Docker Compose, Kubernetes or Helm, connected with a one-time enrollment token. - [Start a worker on a cloud server](https://docs.octomerge.dev/get-started/cloud-server.md): Settings → Workers makes a cloud-init or Terraform/OpenTofu file that connects a new server as a worker on its first boot, with no sign-in on it. - [Connect a remote](https://docs.octomerge.dev/get-started/add-remote.md): Let agents run commands and edit files on a machine without bringing your workspace to it, like ssh. - [Run a worker in a macOS VM](https://docs.octomerge.dev/get-started/macos-worker.md): Create an isolated macOS worker on an Apple-silicon Mac with the r5d macOS npm CLI. - [Browser service](https://docs.octomerge.dev/get-started/browser.md): Connect your Chrome browser to r5d. - [MCP servers](https://docs.octomerge.dev/get-started/mcp-servers.md): Connect remote MCP servers so agents can use their tools. - [Use r5dctl](https://docs.octomerge.dev/cli/r5dctl.md): Manage projects, conversations, account settings, and workspace commands from your terminal. - [TypeScript API client](https://docs.octomerge.dev/cli/api-client.md): Use the typed r5d client to manage account settings, projects, and agent conversations, and to follow the work shared with a team. - [Shell environment](https://docs.octomerge.dev/platform/shell-environment.md): Run tools in a conversation's isolated workspace. - [Deploy access](https://docs.octomerge.dev/platform/deploy-targets.md): Give every agent deploy access once: sign in to Vercel or Cloudflare, or add a Fly.io token, a kubeconfig or AWS credentials in Settings → Secrets. - [Projects and Git remotes](https://docs.octomerge.dev/platform/git-remotes.md): Start a project from GitHub, from an SSH or HTTPS remote on any git host, or without a remote. - [Conversations and workspaces](https://docs.octomerge.dev/platform/workspace-chats.md): Continue work with durable history and synchronized project files. - [Archiving branches and projects](https://docs.octomerge.dev/platform/archiving.md): Keep old work cheaply: an archived branch leaves every worker, and its files, commits and conversations stay on r5d, readable. - [Usage and limits](https://docs.octomerge.dev/platform/usage.md): What your account holds and runs against its limits: your workspace's files, storage and checkouts, your archive, and your agents running at once. - [Open LLM Router apps](https://docs.octomerge.dev/platform/open-llm-router.md): Connect one of your Open LLM Router apps in Settings → Models, choose its models as your default, refresh it when the app changes, and revoke r5d's access. - [Coordination claims](https://docs.octomerge.dev/platform/claims.md): Let sessions take turns on a task, a checkout or a shared host resource. - [AGENTS.md and skills](https://docs.octomerge.dev/platform/agent-instructions-and-skills.md): Give agents standing instructions and reusable procedures across your account or in one project. - [Launch links](https://docs.octomerge.dev/platform/launch-links.md): Start or continue work in r5d from a link in your issue tracker, after you confirm it. - [Teams](https://docs.octomerge.dev/platform/teams.md): Share sessions, branches or whole projects read-only with your team, mention a session so your agent reads it, link a branch's team page from a pull request, and connect issue trackers. - [Issue tracker integrations](https://docs.octomerge.dev/platform/integrations.md): Start r5d work from GitHub issues and pull requests or from Threadline, and follow it there. - [Persistence and recovery](https://docs.octomerge.dev/platform/persistence.md): Understand durable history, synchronized files, and interrupted work. - [Artifact storage](https://docs.octomerge.dev/platform/artifact-storage.md): Upload large attachments, resume transfers, and work with the files in a conversation's artifacts folder. - [Bring a deployment destination](https://docs.octomerge.dev/platform/deployment.md): Deploy using the tools, credentials, and destinations available on your worker. - [Build and push with GHCR](https://docs.octomerge.dev/platform/ghcr.md): Use GitHub Container Registry from your workers and configure deployment access separately. - [Guides](https://docs.octomerge.dev/guides/index.md): Step-by-step setups for running r5d in particular places, tested end to end. - [Run a worker on a boat.dev sandbox](https://docs.octomerge.dev/guides/boat-dev-worker.md): A worker on a boat.dev virtual machine that stops when you aren't using it and starts again from boat's dashboard, with a skill that keeps it running while agents work. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.