[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-94799":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":8,"htmlUrl":9,"language":10,"languages":8,"totalLinesOfCode":8,"stars":11,"forks":12,"watchers":13,"openIssues":13,"contributorsCount":8,"subscribersCount":13,"size":13,"stars1d":13,"stars7d":13,"stars30d":13,"stars90d":13,"forks30d":13,"starsTrendScore":13,"compositeScore":14,"rankGlobal":8,"rankLanguage":8,"license":8,"archived":15,"fork":15,"defaultBranch":16,"hasWiki":15,"hasPages":15,"topics":8,"createdAt":8,"pushedAt":8,"updatedAt":17,"readmeContent":18,"aiSummary":19,"trendingCount":13,"starSnapshotCount":13,"syncStatus":20,"lastSyncTime":8,"discoverSource":21},94799,"remote.futrx","futrx-com\u002Fremote.futrx","futrx-com",null,"https:\u002F\u002Fgithub.com\u002Ffutrx-com\u002Fremote.futrx","Go",228,40,0,38.84,false,"main","2026-08-24 04:01:22","\u003Cp align=\"center\">\n  \u003Ca href=\"https:\u002F\u002Fremote.futrx.com\u002F\">\n    \u003Cimg src=\"docs.remote.futrx.com\u002Fstatic\u002Fbrand\u002Fremote-futrx-on-dark.png\" alt=\"Remote by FutrX\" width=\"300\">\n  \u003C\u002Fa>\n\u003C\u002Fp>\n\n\u003Ch1 align=\"center\">Give every AI project its own computer.\u003C\u002Fh1>\n\n\u003Cp align=\"center\">\n  Run Codex, Claude Code, Kimi, and Antigravity in separate, always-on Linux workspaces on your own server.\n  Use everything from one browser: chat, IDE, terminal, files, Git, live previews, and a shared browser.\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Ca href=\"https:\u002F\u002Fremote.futrx.com\u002F\">\u003Cstrong>Website\u003C\u002Fstrong>\u003C\u002Fa>\n  ·\n  \u003Ca href=\"https:\u002F\u002Fdocs.remote.futrx.com\u002F\">\u003Cstrong>Documentation\u003C\u002Fstrong>\u003C\u002Fa>\n  ·\n  \u003Ca href=\"#quick-start\">\u003Cstrong>Install\u003C\u002Fstrong>\u003C\u002Fa>\n  ·\n  \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Ffutrx-com\u002Fremote.futrx.com\u002Fissues\">\u003Cstrong>Roadmap\u003C\u002Fstrong>\u003C\u002Fa>\n\u003C\u002Fp>\n\n![Remote showing an AI conversation beside the application it built](docs\u002Fassets\u002Freadme\u002Flive-preview.webp)\n\n## What is Remote?\n\nRemote is an open-source, self-hosted home for AI coding agents.\n\nThink of every project as its own server-side computer:\n\n- It has a durable workspace, processes, ports, settings, and agent sessions.\n- Codex, Claude Code, Kimi, and Antigravity can work in the same project without moving files between tools.\n- The work keeps running on your server when you close your laptop.\n- You can watch, review, edit, restart, or take over from any browser.\n\nRemote is not another AI model. It gives the models you already use a complete place to work.\n\n## A quick tour\n\n\u003Ctable>\n  \u003Ctr>\n    \u003Ctd width=\"50%\">\n      \u003Cimg src=\"docs\u002Fassets\u002Freadme\u002Fcreate-project.webp\" alt=\"Creating a new isolated project in Remote\">\n      \u003Cbr>\n      \u003Cstrong>1. Create a project\u003C\u002Fstrong>\u003Cbr>\n      Remote prepares a separate Linux workspace with its own files, processes, ports, and agent homes.\n    \u003C\u002Ftd>\n    \u003Ctd width=\"50%\">\n      \u003Cimg src=\"docs\u002Fassets\u002Freadme\u002Fparallel-agents.webp\" alt=\"Multiple AI agents working in parallel in Remote\">\n      \u003Cbr>\n      \u003Cstrong>2. Run agents in parallel\u003C\u002Fstrong>\u003Cbr>\n      Keep several chats moving while every agent works against the same project state.\n    \u003C\u002Ftd>\n  \u003C\u002Ftr>\n  \u003Ctr>\n    \u003Ctd width=\"50%\">\n      \u003Cimg src=\"docs\u002Fassets\u002Freadme\u002Fbrowser-ide.webp\" alt=\"Remote project opened in its browser IDE\">\n      \u003Cbr>\n      \u003Cstrong>3. Inspect the real workspace\u003C\u002Fstrong>\u003Cbr>\n      Open the project in the browser IDE, terminal, file manager, or Git history.\n    \u003C\u002Ftd>\n    \u003Ctd width=\"50%\">\n      \u003Cimg src=\"docs\u002Fassets\u002Freadme\u002Fagent-browser.webp\" alt=\"Remote agent browser with human takeover\">\n      \u003Cbr>\n      \u003Cstrong>4. Share the browser\u003C\u002Fstrong>\u003Cbr>\n      Watch the agent use a headed browser, then take control for sign-in or human judgment.\n    \u003C\u002Ftd>\n  \u003C\u002Ftr>\n\u003C\u002Ftable>\n\nSee the continuous five-step product tour at [remote.futrx.com](https:\u002F\u002Fremote.futrx.com\u002F#product-tour).\n\n## What you get\n\n- **One project computer per project** — an unprivileged LXC container with durable files and agent homes.\n- **Your choice of agent** — use Codex, Claude Code, Kimi, or Antigravity with provider-specific model and reasoning controls.\n- **A complete development surface** — chat, browser IDE, root terminal, files, uploads, Git history, and reusable skills.\n- **Live applications** — Remote finds listening ports, creates project URLs, adds HTTPS, and shows the app beside the conversation.\n- **A browser agents and humans can share** — let an agent browse visually, watch it work, or take over the same session.\n- **Scheduled work** — let a project chat run a one-time or recurring prompt later, even when your browser is closed.\n- **Controls outside the workspace** — manage access, secrets, CPU, memory, lifecycle, and recovery from the Remote host.\n\n## How it works\n\n```mermaid\nflowchart LR\n    A[\"You\u003Cbr>any browser\"] --> B[\"Remote host\u003Cbr>identity, routing, lifecycle\"]\n    B --> C[\"Project computer\u003Cbr>one unprivileged LXC container\"]\n    C --> D[\"Codex · Claude · Kimi · Antigravity\"]\n    C --> E[\"IDE · terminal · Git · files\"]\n    C --> F[\"Browser · apps · HTTPS previews\"]\n```\n\nThe project computer is the capability boundary: agents can install tools, run servers, use Git, and browse inside it. The Remote host keeps authentication, routing, membership, and container lifecycle controls outside that boundary.\n\n## Quick start\n\n### What you need\n\n- A fresh Ubuntu or Debian server\n- Root or `sudo` access\n- A hostname pointing at that server — one you own, or a free one\n- A working SSH key\n- Ports 80 and 443 open\n\n> [!IMPORTANT]\n> The installer disables SSH password login. Confirm that key-based SSH access works before you run it.\n\n### 1. Point DNS to the server\n\nEvery project gets its own HTTPS address, so Remote needs a hostname with wildcard subdomains under it. Pick whichever case describes you — HTTPS is automatic in all three, with free Let's Encrypt certificates issued and renewed for you.\n\n**If you already own a domain,** use a subdomain of it. For a base domain such as `remote.example.com`, create these records, all pointing at your server's IP address:\n\n| DNS name | Purpose |\n| --- | --- |\n| `remote.example.com` | Remote web app |\n| `code.remote.example.com` | Browser IDE |\n| `*.code.remote.example.com` | Per-project browser IDEs |\n| `*.dev.remote.example.com` | Per-project application previews |\n\n**If you want a free hostname,** [DuckDNS](https:\u002F\u002Fwww.duckdns.org) is the quickest, because it resolves every subdomain automatically and there are no DNS records to create:\n\n1. Sign in with GitHub or Google.\n2. Add a name such as `yourname`. You now own `yourname.duckdns.org`.\n3. Replace the pre-filled IP address with **your server's** address, then select **update ip**. The page fills in the address of the computer you are browsing from, which is usually not your server.\n\nThen install using `yourname.duckdns.org` as the hostname.\n\n[deSEC](https:\u002F\u002Fdesec.io) is a good alternative, run by a non-profit and less likely to be filtered on corporate networks. It is a full DNS host rather than a wildcard service, so create the four records from the table above under your `yourname.dedyn.io` name.\n\n> [!NOTE]\n> Free dynamic-DNS providers are community-run with no uptime guarantee, and some corporate networks block all of `*.duckdns.org` because of unrelated abuse elsewhere on it. If a preview link refuses to open at the office, that is usually why, and a domain you own avoids it.\n\n**If you have neither,** a domain costs around $10 a year and gives you the shortest, most reliable URLs. Register one and follow the first case.\n\n### 2. Install Remote\n\nConnect to the server and run:\n\n```bash\ncurl -fsSL https:\u002F\u002Fremote.futrx.com\u002Fget | sudo bash -s -- remote.example.com\n```\n\nReplace `remote.example.com` with the hostname you set up above. The installer downloads Remote, installs its dependencies, builds the workspace image, starts the services, and enables HTTPS.\n\n### 3. Create your first project\n\n1. Visit `https:\u002F\u002Fremote.example.com`.\n2. Create the administrator account.\n3. Open **Settings → Agents** and connect Codex, Claude Code, or Kimi.\n4. Select **New project**.\n5. Start a chat and describe what you want in normal language.\n\nRemote will show the agent's progress. When the work is ready, review it in the chat, IDE, terminal, file manager, Git history, or live preview.\n\n## Security in plain language\n\nRemote is designed to reduce the blast radius of agent work, not to promise an air gap:\n\n- Projects use separate unprivileged LXC containers, but they share the host kernel.\n- The host administrator can access project data and controls.\n- Secrets given to a project are readable by agents working in that project.\n- Durable storage survives routine container replacement, but it is not a backup.\n\nBefore using Remote with valuable code or credentials, read the [threat model](docs\u002Fthreat-model.md), [known limitations](docs\u002Fknown-limitations.md), and [security policy](SECURITY.md).\n\n## Updating\n\nRun on the Remote server:\n\n```bash\nsudo bash \u002Fopt\u002Fremote.futrx\u002Finfra\u002Fupdate.sh\n```\n\nThe updater rebuilds the app and project image while preserving project files and provider homes. Coordinate a maintenance window, or use `--skip-workspaces`, when agents are actively running. See [Deployment and operations](docs\u002F04-operations\u002F09-deployment-and-operations.md#update-flow) for details.\n\n## Learn more\n\n- [Documentation](https:\u002F\u002Fdocs.remote.futrx.com\u002F) — operator and user guides\n- [System architecture](ARCHITECTURE.md) — components, data flow, and trust boundaries\n- [Project philosophy](docs\u002F01-overview\u002F00-philosophy.md) — why Remote treats each project as a computer\n- [Contributing](CONTRIBUTING.md) — local development and contribution workflow\n- [Issue tracker](https:\u002F\u002Fgithub.com\u002Ffutrx-com\u002Fremote.futrx.com\u002Fissues) — bugs, ideas, and roadmap\n\n## License\n\nCopyright © 2026 FutrX.\n\nRemote is free software licensed under the [GNU Affero General Public License v3.0](LICENSE). You may self-host, modify, and redistribute it under the AGPL's terms. If you offer a modified version as a network service, the AGPL requires you to make the modified source available to its users.\n","Remote 是一个开源、可自托管的 AI 编程代理运行平台，为每个 AI 项目提供独立、持久、隔离的 Linux 工作空间（基于 LXC 容器）。核心功能包括：多 AI 代理（如 Codex、Claude Code、Kimi）并行协作于同一项目状态；浏览器内集成 IDE、终端、文件管理、Git 和可交互式浏览器；支持会话持久化与人工接管。技术上采用 Go 实现，强调安全性（非特权容器）、状态一致性与全栈可观测性。适用于需要长期运行、多人协同评审、模型能力复用及本地数据合规要求的 AI 编程实验、自动化开发与智能体测试场景。",2,"trending"]