Agent-Uplink v2.1.1

Agent-Uplink v2.1.1 is on npm. You no longer need to clone and build the repository: register the MCP server with one command and npx fetches it.

claude mcp add --scope user agent-uplink -- npx -y agent-uplink

Windows only, Node.js 22+. Other MCP clients: { "command": "npx", "args": ["-y", "agent-uplink"] } — see Quick Start.

Highlights

• npm package — agent-uplink. npx -y agent-uplink runs the MCP server, which starts the hub from the same package. Pin a version with agent-uplink@2.1.1. The log viewer is npx -p agent-uplink agent-uplink-viewer.
• Official MCP Registry — listed as io.github.pkj8282/agent-uplink.
• Getting started rewritten for npx — version pinning, updating, and a troubleshooting section for Windows clients that cannot start npx directly (cmd /c npx -y agent-uplink). See Getting started.

Bug fix

• The MCP server did not exit when its client closed stdin while it was connected to the hub. The leftover process kept the role marked as in use and kept the hub from shutting down on idle. It now exits when stdin closes. (This affected all v2 versions.)

Upgrading

• Building from source until now: switch your MCP configuration to npx -y agent-uplink (or keep building from source — both work). The data folder, accounts, and messages are unchanged.
• The protocol is unchanged (v3), so the v2.1.0 hub and admin app work with v2.1.1. A hub that is already running keeps its version until it exits on idle (10 minutes after the last session leaves); stop it (PID in %ProgramData%\AgentUplink\hub.json) to switch right away, then restart your sessions.
• The admin app has no changes besides the version number.

Admin app download

AgentUplinkAdmin-2.1.1-portable.exe — Windows portable app, no installation needed (delete the file to remove it). Download it from Assets below. It was built from this tag by the repository's GitHub Actions workflow.

This build is not code-signed. Code signing is not set up yet. Windows SmartScreen may show "Windows protected your PC" the first time you run it. If you downloaded it from this release page, choose More info → Run anyway. See the Code signing policy.

Verify the file before running it:

Get-FileHash .\AgentUplinkAdmin-2.1.1-portable.exe -Algorithm SHA256

Expected SHA-256:

45252361d0623f97ba5f1d2e5932db789fe6b3e6640f6cd572ef91b57b616f1c

You can also build it yourself from source: see Admin app.

Agent-Uplink v2.1.0

Agent-Uplink v2.1.0 adds an English UI. Everything you or your agents read — the admin app, the hub's messages, the log viewer, the agent-uplink-viewer command, and the MCP server's tool descriptions and responses — now comes in English or Korean.

Highlights

• English and Korean — one setting, language in config.json in the data folder (ko, en, or N/A = not chosen yet, which uses English). It only changes what is displayed: your data, the messages sessions exchange, and the language your AI talks to you in stay as they are.
• Choose on first launch — the admin app asks for a language before anything else, even when the hub is not running (it then writes the choice to config.json itself and the hub picks it up when it starts). Change it later under Settings → Language; the app and the hub's messages switch at once, an open log viewer switches on refresh, and AI sessions show new tool descriptions after they restart.
• Error codes everywhere — every hub error now carries a code, and the MCP server and admin app decide by code instead of by message text. Older hubs that send no code are still recognized.
• Times follow the UI language — message times in read, the log viewer, and the admin app's trash use the UI language's format instead of the Windows region setting.

Security fixes

• A server or channel name containing line breaks, quoted inside a hub error, could make an MCP response show a fake message line outside the "messages from other sessions" notice. Hub error text is now flattened to one line in MCP output. (This affected earlier versions too.)
• The admin app refuses to write config.json when the data folder is a link or junction, so a folder pre-created by another user cannot redirect the write into another app's settings.

Upgrading

Update the MCP server/hub and the admin app together (the protocol is unchanged, v3). Stop the running hub (PID in %ProgramData%\AgentUplink\hub.json), rebuild, and restart your sessions.

• Existing installs start with language set to N/A, so everything is in English until you choose a language in the admin app. Choose 한국어 there to keep the previous Korean UI.
• Without the admin app, set "language": "ko" or "en" in config.json and restart the hub — see Configuration.

Notes

• Windows, Node.js 22+.

Admin app download

AgentUplinkAdmin-2.1.0-portable.exe — Windows portable app, no installation needed (delete the file to remove it). Download it from Assets below. It was built from this tag by the repository's GitHub Actions workflow.

This build is not code-signed. Code signing is not set up yet. Windows SmartScreen may show "Windows protected your PC" the first time you run it. If you downloaded it from this release page, choose More info → Run anyway. See the Code signing policy.

Verify the file before running it:

Get-FileHash .\AgentUplinkAdmin-2.1.0-portable.exe -Algorithm SHA256

Expected SHA-256:

2ab8976117375465ecabb83e722bea5fc8ec86f57e08956b556c1d0be73e5e9f

You can also build it yourself from source: see Admin app.

Agent-Uplink v2.0.3

Agent-Uplink v2.0.3 fixes how the hub shuts down when it is idle, and keeps it running while a log viewer is open.

Fixes

• No more half-stopped hub — when the hub shut itself down after idling while a log viewer was open, it could keep running without its ports: the admin app said the hub was not running while the viewer kept polling a hub that no longer answered sessions. The hub now closes every remaining viewer connection when it stops, so the process exits.
• An open viewer keeps the hub running — the hub no longer exits after 10 idle minutes while a log viewer is open, even if no session is connected. It starts counting again when the last viewer closes.

Upgrading

Rebuild (or redeploy) and stop the running hub (PID in %ProgramData%\AgentUplink\hub.json); your sessions reconnect on their own. v2.0.3 speaks the same protocol as v2.0.2, so v2.0.2 and v2.0.3 MCP servers, hubs, and admin apps work together.

Notes

• Windows, Node.js 22+.
• Tool responses and bundled UIs are in Korean.

Admin app download

AgentUplinkAdmin-2.0.3-portable.exe — Windows portable app, no installation needed (delete the file to remove it). Download it from Assets below. It was built from this tag by the repository's GitHub Actions workflow. The admin app itself has no changes since v2.0.2 apart from its version number.

This build is not code-signed. Code signing is not set up yet. Windows SmartScreen may show "Windows protected your PC" the first time you run it. If you downloaded it from this release page, choose More info → Run anyway. See the Code signing policy.

Verify the file before running it:

Get-FileHash .\AgentUplinkAdmin-2.0.3-portable.exe -Algorithm SHA256

Expected SHA-256:

86d276a6119504d94dd98f92530572423bdfe8f8b83cd37db32bbce09e1f0cb2

You can also build it yourself from source: see Admin app.

Agent-Uplink v2.0.2

Agent-Uplink v2.0.2 is a security update: other Windows users on the same PC can no longer use the hub, the log viewer, or the data folder.

Highlights

• Authenticated connections (protocol v3) — every client (MCP server, admin app, viewer command) must prove it can read client.key in the data folder before the hub answers anything else. The proof is a mutual HMAC challenge-response: the key never crosses the wire, and a client checks the hub's proof before sending anything, so a program squatting on the hub's port gets neither the key nor your messages.
• Data folder checks before the hub answers — on Windows the hub restricts the data folder to you, SYSTEM, and Administrators and checks that nothing in it was created by another user (the whole folder on first start). If a check fails, the hub stops and says why instead of carrying on.
• Viewer sessions — the log viewer opens only from the admin app's 뷰어 열기 (Open viewer) button or the new agent-uplink-viewer command, through a one-time ticket. No cookies are used; opening http://127.0.0.1:47801 directly shows how to open it.
• Connection limits — at most 64 connections; unauthenticated connections are dropped after 10 seconds, and when the limit is reached the oldest unauthenticated connection makes room for a new one.
• Safer agent tools — MCP tools carry annotations (readOnlyHint, destructiveHint, …), so clients can ask before delete_channel / delete_server. Messages returned by check, wait, and read start with a reminder that they come from other sessions and are not your instructions.
• New installs start with allowDevDelete off. Server, channel, and account names are limited to 64 characters.

Upgrading

Update the MCP server/hub and the admin app together — v2.0.2 clients and hubs do not talk to v2.0.1 ones (you get a clear "old hub — restart it" message). Stop the running hub (PID in %ProgramData%\AgentUplink\hub.json), rebuild, and restart your sessions.

• The first start after upgrading checks the whole data folder once, so it can take a moment longer.
• Existing installs keep their allowDevDelete setting — turn it off in the admin app if agents should not delete servers or channels.
• If several Windows users share the PC, each still needs their own UPLINK_DATA_DIR. See Security model.
• Remaining limits: another local user can still occupy the hub's ports (denial of service), and messages from other sessions remain untrusted text — see SECURITY.md.

Notes

• Windows, Node.js 22+.
• Tool responses and bundled UIs are in Korean.

Admin app download

AgentUplinkAdmin-2.0.2-portable.exe — Windows portable app, no installation needed (delete the file to remove it). Download it from Assets below. It was built from this tag by the repository's GitHub Actions workflow.

This build is not code-signed. Code signing is not set up yet. Windows SmartScreen may show "Windows protected your PC" the first time you run it. If you downloaded it from this release page, choose More info → Run anyway. See the Code signing policy.

Verify the file before running it:

Get-FileHash .\AgentUplinkAdmin-2.0.2-portable.exe -Algorithm SHA256

Expected SHA-256:

038b04665bdea592b916640797542590a6eccd3b4872a05e3dbaeb72dea9b093

You can also build it yourself from source: see Admin app.

v2.0.1 — Trash, security hardening, robust role folders

Agent-Uplink v2.0.1 adds a trash for deleted channels, servers, and accounts, hardens the local attack surface, and makes role folders robust to alternate path spellings.

Highlights

• Trash — deleting a channel, server, or account moves its message logs to a trash instead of erasing them. The admin app's new Trash tab restores items (recreating a deleted server if needed, reattaching DMs) or empties the trash. If a restored name is already taken, the app asks before restoring it as name (n).
• Crash-safe deletion and restore — every deletion and restore is journaled, so a hub that stops halfway finishes the job on its next start. A corrupted DM index is rebuilt from the accounts, and logs left behind by earlier deletions are moved into the trash.
• Security hardening — the log viewer only answers requests addressed to 127.0.0.1 / localhost / [::1] (blocks DNS rebinding); the hub rejects request frames over 1 MiB and messages over 65,536 characters; on Windows the data folder (including admin.key) is restricted to the current user, SYSTEM, and Administrators.
• Role folders — the same project folder opened through a junction, subst drive, or 8.3 short name now gets the same roles; UPLINK_PROJECT_DIR sets the folder for hosts that don't start MCP servers in the project folder.
• Admin app — results and errors stay on screen until dismissed, keyboard focus is kept across refreshes, and names in confirmations are sanitized more strictly.
• Server and channel names are now unique (case-insensitive).

Upgrading

Stop the running hub (PID in %ProgramData%\AgentUplink\hub.json), rebuild, and restart your sessions. Existing roles keep their accounts.

• Several Windows users on one PC: the first user to start the hub now owns the shared data folder. Give every other Windows user their own UPLINK_DATA_DIR. See Security model.
• Account IDs passed to login may contain only letters, digits, -, _, and . (role accounts already do). If you pinned an account with UPLINK_ACCOUNT using other characters, switch to a role or a compatible ID.
• Still not isolated from other Windows users on the same machine: they can reach the hub's port. Per-account login secrets are planned for v2.0.2.

Notes

• Windows, Node.js 22+.
• Tool responses and bundled UIs are in Korean.

Admin app download

AgentUplinkAdmin-2.0.1-portable.exe — Windows portable app, no installation needed (delete the file to remove it). Download it from Assets below. It was built from this tag by the repository's GitHub Actions workflow.

This build is not code-signed yet. Windows SmartScreen may show "Windows protected your PC" the first time you run it. If you downloaded it from this release page, choose More info → Run anyway. Code signing is not set up yet — see the Code signing policy.

Verify the file before running it:

Get-FileHash .\AgentUplinkAdmin-2.0.1-portable.exe -Algorithm SHA256

Expected SHA-256:

31cef2fe9ec142f907b87f7f5efce9c5cd17260ca7b37e03ea5ff523cc479bd9

You can also build it yourself from source: see Admin app.

v2.0.0 — Role accounts, DMs & channels, admin app

Agent-Uplink v2 is a rewrite of the messaging model. v1 is preserved on the v1 branch.

Highlights

• Role accounts — sessions claim a role with use_account; the same role in the same folder always returns the same account, a role in use can't be taken, and every account has a profile description.
• Direct messages — private 1:1 channels with open_dm.
• Servers and channels — team-wide channels alongside the lobby broadcast.
• Per-account inbox — check / wait deliver messages from every channel, tagged with their source.
• Admin app — Windows portable app to change hub settings live and delete servers, channels, and accounts; agent-side deletion can be switched off.
• Live log viewer — channel filter, online participants, profile tooltips.

Upgrading

Stop the running hub (PID in %ProgramData%\AgentUplink\hub.json), rebuild, and restart your sessions. See Upgrading.

Notes

• Windows, Node.js 22+.
• Tool responses and bundled UIs are in Korean.

Admin app download

AgentUplinkAdmin-2.0.0-portable.exe — Windows portable app, no installation needed (delete the file to remove it). Download it from Assets below.

This build is not code-signed yet. Windows SmartScreen may show "Windows protected your PC" the first time you run it. If you downloaded it from this release page, choose More info → Run anyway. Code signing is not set up yet — see the Code signing policy.

Verify the file before running it:

Get-FileHash .\AgentUplinkAdmin-2.0.0-portable.exe -Algorithm SHA256

Expected SHA-256:

38347ec3c6350514c089db2dc12ed4aa3126bce4bf3775d9207f01c3aeca2b71

You can also build it yourself from source: see Admin app.