Getting started
1. Install
Download the macOS Apple Silicon offline kit from the homepage. Use Node.js 22 or later installed outside an application bundle. Extract the archive, enter its directory and run:
node install-local.cjs
~/.local/bin/linkcattle service status --json
| Platform | Use |
| macOS Apple Silicon | CLI; Codex, Pi, Claude, DSH or Qoder |
| Linux x64 | Native acceptance pending; no package published in this release |
| Windows | Native CLI/Core acceptance pending; no package published in this release |
| Android ARM64 | Signed Android 0.1.1+2 is available; physical-device acceptance pending |
| iOS | Archive and App Store release in preparation |
The offline kit includes signed and notarized CLI 0.1.4, its macOS components and independently verified Core 0.1.4. This delivery excludes npm publication. Source and artifact checks passed; local installation, phone and complete end-to-end acceptance remain incomplete. Check linkcattle service status --json before connecting. See the CLI guide for details.
2. Connect your computer
After installation, run:
linkcattle --lang en
linkcattle --region cn
linkcattle login
linkcattle connect codex
Codex desktop sharing supports macOS only. Before first connection, finish your tasks and quit independently running Codex. After connection succeeds, open Codex normally. No default project is bound. Use linkcattle connect codex -qr to claim the service by scanning from your phone.
Other connection types:
linkcattle connect pi --executable /absolute/path/to/pi
linkcattle connect claude --profile /absolute/private/claude/profile.json
linkcattle connect dsh --profile /absolute/private/deepseek/profile.json
linkcattle connect qoder
linkcattle connect web 127.0.0.1:8080
The Qoder adapter requires Qoder CLI 1.1.37, Node.js 22+, npm and jq. Complete qoder login on the computer first; the first connection installs the pinned official SDK. Qoder uses its existing sign-in, with no custom model endpoint or key. IDE shared control is unavailable.
Pi uses its local environment; Claude and DSH use existing protected profiles. Each agent retains its model login and tool permissions. Keep projects and agents inside the same Linux or WSL environment. WSL must stay running; systemd alone does not keep it alive. See the CLI guide for API connections and service management.
3. Continue on your phone
With the matching computer-workspace platform and Runtime, computer login automatically registers the computer and its OS. Select it from Connections or the homepage computer switcher.
Rename a registered computer from its management actions. Only the account owner can change its display name; the trimmed name contains 1–80 characters and is shared by all devices signed in to that account. Heartbeats, reconnects and Runtime restarts keep the chosen name. A new computer starts with its readable system name, or an OS/model label when its hostname is only a technical identifier. Sign in before renaming the local computer.
Services use an icon grid. Long press an icon, use its more menu or press Shift+F10 to manage it. New services appear on that computer's homepage by default; hidden icons remain in All services. Favorites show their source computer and open it without changing the selected computer. Display preferences are isolated by account and region. The bell next to Refresh opens notifications and sharing requests.
To share a service, open its more menu and choose Share service. The invitation includes all of its current shareable features; there is no permission picker. The recipient scans the code and applies, then the owner approves from the issuing device's notifications. This grants service use, including permitted writes and Agent tasks, without transferring ownership or credentials. Existing limited shares need a new invitation and approval to receive the current features; future features are not added automatically.
Add service submits a typed request to the selected computer's Runtime. Prepare the agent's local sign-in, executable and permissions on that computer first. If the outcome is unknown, query the original request under Connections instead of submitting it again. An older platform still exposes existing services but needs an upgrade for computer registration and remote setup.
Sign in to the same China account, install Coding from the marketplace, open the service under Services, and choose a project and session. The computer must remain awake and online, with the agent and LinkCattle background service running. Updating the phone App does not update the computer runtime. The CLI verifies and manages the independent Core release. Core and CLI versions may differ; no separate Connector installation is needed. Finish active work before updating the matching CLI package.
Generic websites open directly from Services without a business App. They retain their own login and currently support the owner account only. Third-party login/CDN, hardcoded URLs, JavaScript cookies and Service Workers may need adaptation.
Region, language and data
On Android, choose Add to phone home screen in a service's menu and confirm the launcher prompt. The icon opens the service through normal identity and access checks. Sign in to the account that created it; deleted services or expired grants cannot be opened. Launcher support is required.
China uses https://cn.linkcattle.com/gateway. Singapore and US endpoints are not enabled. Changing region does not migrate accounts or services. App and CLI language supports zh, en, ja and ru; language does not change region.
Projects and model sign-in stay on your computer. The platform handles account, authorization and connection metadata; a trusted HTTPS gateway can read forwarded content. CLI uses ~/.linkcattle/. Never package or commit that directory.
linkcattle disconnect ID pauses a connection. linkcattle service uninstall stops the background service while retaining configuration. linkcattle delete INSTANCE_ID --yes permanently deletes service registration and sharing grants, retaining projects, native sessions and computer files.