sub2sub connects your devices and those your teammates authorize you to use, so you can share AI resources and collaborate through familiar AI tools. Send selected files, bring responses and results back, and continue the same task in your conversation. Account credentials stay with their owners, and hosts control what they share.

A Host shares AI capabilities and executes authorized tasks. A Client delegates tasks and receives results. One device can serve both roles. Connect directly on a private network, or enable cross-network service on both devices.

Start with installation, then connect two devices. For a first task, send a small non-sensitive text file and ask for a summary.

The current management UI with synthetic device names and task records; no real accounts or task content are shown.

What you can do

• Choose where each task runs. Select an execution tool and available model from your paired nodes, with on-demand queries for a Codex node's remaining quota. Optionally enable ordered host selection before new task submission; submitted tasks never reroute automatically.
• Bring back files and responses together. Receive a complete local work copy with the inputs and latest changes. Decide when to apply them to your source project, and open saved results offline.
• Request revisions on the same task. “Improve the mobile layout too” continues with the host's existing working files and session.
• Choose session visibility. New Codex tasks archive after each turn and restore on continuation by default. Hosts can keep them in the native task list; existing tasks and file retention stay unchanged. Details.
• Keep sharing under the host's control. Hosts choose authorized connections, an execution tool, and offered models. They can stop accepting new tasks at any time. Each node runs up to four tasks concurrently by default; the host can adjust the limit. Full nodes reject new work without a queue, and lowering the limit lets existing tasks finish.

Good fits include organizing documents, building offline pages, and making code changes with clear inputs and outputs. Tasks run in separate work copies with task network access, MCP, app, and browser integrations disabled. The host checks the environment needed for the task. By default, checks unavailable there can be completed on the client; an explicit requirement to run on the host still applies. Required checks must pass before claiming completion. Execution scope and limits

Install

Install on both the computer sending tasks and the computer receiving them. Choose the app where you will use sub2sub below; the receiving device can choose its execution tool separately. Sign in to that app first. Packages include Node and certificate generation; no npm setup is needed.

Ask your AI to install it

Send this to the Codex or Claude Code app you are using:

Follow the installation instructions at https://github.com/mekoand/sub2sub to install the latest stable sub2sub release for the app I am using. Check and report the installed version, confirm it is the latest stable release and enabled, then tell me how to restart and get started.

The assistant chooses the installation method for your host and system. If it cannot run the installer, ask for the matching command. Restart the app as instructed after installation. You can also install manually below.

Codex

macOS · Terminal (Apple Silicon or Intel, detected automatically)

/bin/bash -o pipefail -c 'curl -fsSL https://github.com/mekoand/sub2sub/releases/latest/download/install.sh | /bin/bash'

Windows x64 · PowerShell

irm https://github.com/mekoand/sub2sub/releases/latest/download/install.ps1 | iex

After Installed sub2sub appears, fully quit and reopen Codex Desktop, or exit and restart the Codex CLI. Closing only a window or starting another conversation may keep the old plugin loaded.

Claude Code

macOS · Terminal (Apple Silicon or Intel)

/bin/bash -o pipefail -c 'curl -fsSL https://github.com/mekoand/sub2sub/releases/latest/download/install.sh | /bin/bash -s -- claude'

Windows x64 · PowerShell

& ([scriptblock]::Create((irm https://github.com/mekoand/sub2sub/releases/latest/download/install.ps1))) -Target claude

After installation, start a new Claude Code session. Client-only devices do not need Codex. Claude execution on receiving devices requires macOS; Windows can send tasks from Claude Code. Requirements and custom paths

Confirm that it loaded

In your restarted app, ask:

Show sub2sub status and version without changing settings.

Check the version loaded in the current conversation. A stopped sharing node is normal before you start receiving tasks. On first use, review the settings when prompted; this does not enable cross-network service or authorize file transfer.

To update later, say “Upgrade sub2sub” in the app you installed it into. Pairings and saved results are preserved. Restart that app to load the update; an existing sharing node keeps running until you explicitly restart it while idle. Install, update and troubleshooting

Connect your work nodes

For devices on different networks, first ask to enable cross-network connection service on each device. It is off by default. For devices already reachable on a private network, leave it off. Cross-network setup and existing connections

On the computer that will receive tasks:

Generate a sub2sub invitation.

On the computer that will send tasks, paste that invitation:

Connect this sub2sub invitation and name it office-mac.

Confirm the file-transfer scope when prompted. Give each connection a recognizable name. Sharing runs independently after startup: keep the receiving computer awake and connected; its management conversation can close.

Try one small task

Choose a short, non-sensitive text file such as notes.txt in your current workspace, then ask:

Use sub2sub to send only notes.txt to office-mac. Summarize it in summary.md and return that file and a short answer.

After the task completes, open the local summary.md link. Success means the answer and file have been saved on your computer; a connected node alone does not mean a task has completed. Your source file remains unchanged.

To revise the result in the same conversation:

Continue that task. Make summary.md shorter and save the updated result locally.

The receiving device reuses the original task and working files. You can open saved results even when it goes offline. Delegation, results and cleanup

Example: delegate from Codex to Claude

A teammate is signed in to Claude Code on their Mac and authorizes you to use it through sub2sub. In your own Codex conversation, pair with that device, name the connection office-mac, and delegate the documentation task:

Use sub2sub to send the docs directory to office-mac. Build an offline help site with search, check the links, and return the complete files.

The result is saved locally. Take a look, spot a mobile layout that could use some work, and continue:

Continue that task. Group the pages by topic and improve the mobile layout.

The host reuses the task's working files and Claude session. Only changed files are transferred back, and you receive a complete local copy. Once the result is ready:

Save the latest results, finish the task, and clean up its remote work copy.

Your source project stays unchanged until you choose to apply the result. Saved files remain available when the node goes offline. Usage, settings, and cleanup

A compact view of tasks and results

Say this in your conversation:

Open sub2sub management.

The local management page provides a compact view for nodes, tasks, and saved results, with pairing, settings, and on-demand Codex quota queries. Resource statistics over 7 or 30 days show where your tasks went, how many turns ran, and their measured execution time. Native model usage is available by turn, model and source, with partial-data notes and JSON export; no prices are calculated.

Management is enabled by default and can be turned off at any time. It shares the plugin process, adds no background service, and does not open a browser automatically. Task instructions and follow-ups stay in your conversation. Management and statistics

Across networks

Cross-network service is off by default. Enable it on both devices, then exchange one invitation as usual. Private connections are tried first; the bundled Tailcat transport can use public relays when needed. Users do not select routes per task. Existing connections keep their current route until explicitly migrated. Setup and migration.

Compatibility

The managing app is where you use the plugin; the Host chooses its execution tool separately.

WorkBuddy and other managing apps remain untested. Versions and validation details

The current release is v0.9.2. main can contain changes awaiting release, including the Host/Client terminology and environment guidance described here. Connection Token budgets, expiry-based full cleanup, and automatic Host selection are tracked in #60, #61, and #62; they are not part of v0.9.2. Check releases before relying on a feature.

Development

npm ci --omit=optional --ignore-scripts
npm run check
npm test

Development and packaging · Architecture · Contributing · Changelog

If something gets stuck, ask “Help diagnose this sub2sub problem” in the original conversation. When you want to report it, say “Submit this issue to GitHub”. The assistant prepares a public-safe draft, checks for duplicates, and uses the host's existing submission tools. If those are unavailable, it gives you the draft. Troubleshooting · Issues

Contribute and give feedback

Documentation, translations, bug reproductions, focused fixes, and tool-adapter proposals are welcome. Start with the contribution guide (中文). Use Issues for bugs, proposals, and planned work; report vulnerabilities through the private security channel. See the changelog for updates and the MIT License for licensing.

sub2sub is community-maintained. Please keep discussion respectful and evidence-based. You are responsible for following the terms of the AI services you use. This project is not an official OpenAI or Anthropic product and does not imply their endorsement.

MIT © 2026 mekoand