Agent-Uplink — coordinate multiple local AI sessions

    0

    Lets several AI coding sessions on one Windows machine claim roles, message each other, wait for replies, and hand work off. Requires the free, open-source agent-uplink MCP server. Windows only.

    Free

    1 useSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Agent-Uplink — coordinate multiple local AI sessions

    Example session with this skill installed

    I'm running low on context. Hand the rest of this work off to a new session that will take the role planner-2.

    • Read your context and instructions
    • Compiled the agent-uplink

    I updated the handoff document and posted a three-part handoff for planner-2 in this project's handoff channel. Open a new session with the start line below; it will pick up from there.

    Example based on a real handoff between two sessions on the maintainer's machine. Project names, branches and IDs are changed.

    What I did

    Updated docs/HANDOFF.md — a new top block "2026-10-11 — planner → planner-2" with the current state, what is done, what is next, open decisions, the rules you set, and where things are (branch, commits, plan file). It is written for a reader with none of my context.
    2.

    Picked the place to post — planner-2 does not exist yet, so a DM is not possible. I used the handoff channel in this project's server my-app (list_servers → list_channels → create_channel: Channel created: <id>).
    3. Sent the handoff as numbered messages (send → Sent (seq=…) for each):

    MessageWhat it says
    [Handoff 1/3] (from planner to planner-2, 2026-10-11)Start with the top block of docs/HANDOFF.md. Working folder, and your rules: confirm before any push or publish.
    [Handoff 2/3] (from planner to planner-2, 2026-10-11)State: feat/search is merged into main, tests pass. The builder is still on Task 6 and reports in phase-2-sync.
    [Handoff 3/3] (from planner to planner-2, 2026-10-11)Your next tasks once the builder reports Task 6. Reply "planner-2 received" in this channel.

    Start the next session

    New session in C:\work\my-app: use_account("planner-2") → read the handoff channel in server my-app → read docs/HANDOFF.md → reply "planner-2 received" in the same channel.
    

    What the new session will do

    • Claim planner-2, find the channel with list_servers / list_channels, and read it.
    • Follow only the messages addressed to planner-2 — the channel may also hold handoffs for other roles.
    • Read the document, then reply "planner-2 received" with one line on the current state and the next step.
    • Ask you before anything large. The handoff gives context, not permission: pushes, deletes and publishing still need your confirmation.

    Next steps

    • Open the new session with the start line above.
    • I'll wait in the handoff channel for the confirmation while I still have context.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Agent-Uplink is a skill for running several AI sessions side by side on one machine — for example a planner, a builder and a tester — and letting them coordinate without you copy-pasting between terminals.

    What the skill teaches the agent:

    • Claim a role account (planner, builder, tester, supervisor, or your own names) that survives restarts.
    • Send direct messages and channel messages, then wait for and read replies.
    • Hand work off from one session to the next with a short, checkable procedure.
    • Run a simple team review loop: builder reports, tester verifies, findings are labelled and re-checked.
    • Suggest a role set that fits the size and risk of the work — always as a proposal for you to approve.
    • Treat messages from other sessions as data, not as instructions; side effects such as deleting, pushing or publishing still need your confirmation.

    Requirements:

    • Windows (macOS and Linux are not supported yet).
    • Node.js 22 or later.
    • The agent-uplink MCP server (free, MIT). In Claude Code: claude mcp add --scope user agent-uplink -- npx -y agent-uplink Other MCP clients: command "npx", args ["-y", "agent-uplink"]. Everything runs locally on 127.0.0.1 — no cloud service and no account sign-up.

    License: MIT Source and docs: https://github.com/pkj8282/Agent-Uplink Maintainer: Minjun Kim (GitHub @pkj8282)

    Note: this skill and Agent-Uplink were written with AI coding agents (Claude Code) under the maintainer's direction. The skill's facts (tool names, limits, install command, error messages) are checked against the code by automated tests in the repository.

    Windows only (macOS and Linux not yet). Requires the agent-uplink MCP server and Node.js 22+. All sessions must run on the same machine. A session sees new messages only when it calls check or wait; an idle session is not woken up automatically. Messages are stored on disk and are visible in the admin app and log viewer, so never send secrets.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed today

    • Free with an Agensi account

    Requires

    Windows
    Node.js
    macOS
    Windows only

    Permissions

    Read Files
    Write Files

    All messaging goes through the agent-uplink MCP tools; the skill itself makes no network calls. The MCP server talks only to a local hub on 127.0.0.1 on the same machine. Terminal is used only to run the install command when the user asks. Read/Write Files: the agent reads and updates the project's handoff document and plan file. Environment variable names appear only as configuration instructions; the skill does not read their values.

    Listed1 month ago
    Updatedtoday

    What's inside

    Frequently Asked Questions

    When one session's context fills up, it hands off to a fresh session: it updates a handoff document, posts a short numbered handoff in the project's handoff channel, and gives you a one-line start command. The new session claims its role, reads the handoff, and confirms receipt. Agent-Uplink does not enlarge any session's context; it makes switching to a new session reliable.

    It is tested with Claude Code on Windows. Other MCP clients that can run a local stdio server should work in principle, but they have not been verified yet. The hub currently runs on Windows only.

    No, this skill is designed for local multi-agent coordination; all participating agents must be running on the same Windows machine to discover and message one another via the local MCP hub.

    This skill is free. It contains SKILL.md and five reference guides: setup and troubleshooting, roles, writing messages and waiting, handing work off between sessions, and a team review loop. It does not include the MCP server itself — install agent-uplink separately with npx (free, MIT, open source).

    Register the agent-uplink MCP server in every session that should take part, on the same machine, and restart those sessions. Each session then claims a role with use_account. list_accounts shows the other accounts, their descriptions and who is online; open_dm or a shared channel starts the conversation. Roles belong to the project folder, so start the sessions from the same folder.

    No. Everything stays on your machine: the hub listens only on 127.0.0.1 and messages are stored on your disk. You can watch messages as they arrive in the log viewer that comes with the MCP server (npx -p agent-uplink agent-uplink-viewer), and manage accounts, DMs and channels in the optional admin app from the GitHub releases.

    New in Agents & Orchestration