agent-mailbox — Mailbox and Wake System for AI Agent Teams

Name: agent-mailbox — Mailbox and Wake System for AI Agent Teams
Author: polaris-smart

제작자: polaris-smart버전 0.7.6i★ –i내 컴퓨터에서 실행

레지스트리 이름io.github.polaris-smart/agent-mailbox

설치

개요

제작자가 쓴 설명(영어 원문)

Mailbox + wake system for AI agent teams: letters always land, right agent wakes, quiet otherwise.

PopNx MCP의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

사용자 의견i아직 리뷰가 없어요리뷰는 다음 단계에서 계정 기능과 함께 열려요
우리의 기본 점검i1개 중 1개 통과공개된 정보로 점검했으며, 코드는 아직 스캔하지 않았어요
사용 정도i아직 측정 안 함★ –

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

연결 방식: 내 컴퓨터에서 실행
전송 방식: stdio
카테고리: 기타

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

설치하기 전에

기본 점검: 1개 중 1개 통과
내 컴퓨터에서 내 사용자 계정의 권한(파일, 네트워크, 앱)으로 실행돼요.
레지스트리에 입력해야 할 키가 나와 있지 않아요.

필요한 것

PyPIPython의 uv 설치(uvx 명령어용)

어떤 앱을 쓰세요?

ClaudeClaude CodeCursorVS CodeChatGPT

위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.

Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요

{
  "mcpServers": {
    "agent-mailbox": {
      "command": "uvx",
      "args": [
        "agent-mailbox"
      ]
    }
  }
}

터미널에서 이 명령어를 실행하세요

claude mcp add agent-mailbox -- uvx agent-mailbox

Cursor에서 열기

또는 설정을 직접 복사하기

프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요

{
  "mcpServers": {
    "agent-mailbox": {
      "command": "uvx",
      "args": [
        "agent-mailbox"
      ]
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

VS Code에서 열기

또는 설정을 직접 복사하기

프로젝트의 .vscode/mcp.json에 붙여 넣으세요

{
  "servers": {
    "agent-mailbox": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "agent-mailbox"
      ]
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검

✓ 통과
제작자와 저장소 일치
레지스트리 이름이 GitHub 계정 polaris-smart 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
… 아직 점검 안 함
계속 관리되고 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
… 아직 점검 안 함
라이선스 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
– 해당 없음
엔드포인트 응답
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
– 해당 없음
OAuth로 로그인
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
… 아직 점검 안 함
도구 설명에 숨겨진 지시 없음
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요

기타 카테고리의 다른 서버와 비교i

이 카테고리의 다른 서버 18326개 중 0%보다 스타가 많아요
이 카테고리의 다른 서버 18326개 중 55%보다 최근에 레지스트리에 공개됐어요
기본 점검 결과가 이 카테고리의 다른 서버 18326개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

agent-mailbox — Mailbox and Wake System for AI Agent Teams, 안전한가요?

해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.7.6)은 38일 전 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Python (uv)도 있어야 해요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Signoff

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

Spec Driven Development

제작자: formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

내 컴퓨터에서 실행★ 440MIT14개월 전 업데이트

설치

Remote Desktop Commander

제작자: desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

클라우드에서 실행★ 211그저께 업데이트

설치

Signoff

제작자: ayuanxx-max

Five gates that make an agent's 'done' provable: run them, read the verdict, audit the record.

내 컴퓨터에서 실행오늘 업데이트

설치

제작자의 README

README 열기

제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.

agent-mailbox

Give your existing AI agents a shared project. Keep the final decision yours.

Working across DeepSeek Harness, Workbuddy, Doubao, ZCode, Claude Code or Codex? agent-mailbox brings their messages, tasks, approved documents, and submitted results into one local workbench. Keep working in the agent tools you already use, with a clear record of who accepted the work and what still needs your review.

Assign → accept → work from approved versions → submit → Human review.

中文 · Downloads and platform scope · Local Web · Quick start

Watch the 60-second portrait introduction (Mandarin narration and captions; synthetic demo data)

Stop carrying context between conversations

You ask one agent to implement a change, then bring another in to review it. The requirements have changed, the conversation history is scattered, and “done” could mean anything from “I read your message” to “the work passed review.”

agent-mailbox gives each project a place for that handoff:

Project mailboxes: connect an existing agent session through MCP, scoped to one member and one project.
Explicit task acceptance: reading a message does not accept a task.
Approved document versions: accepting a task records a resource manifest; the agent reads its exact version IDs.
Reviewable results: submission leaves the task waiting for your decision. You decide whether to accept it or request further work.

Which agents can join?

Since v0.8.0, agent-mailbox has supported collaboration across existing agent App / CLI sessions through project mailbox MCP. Later versions retain that capability; support has not been narrowed to two agents. DeepSeek Harness, Workbuddy, Doubao, ZCode, Claude Code, Codex, Hermes and other hosts can join through their MCP integration.

Layer	Support and verification
Project mailbox collaboration	Agent sessions that load the project stdio MCP can exchange mail, explicitly accept tasks, read pinned resources and submit results. The workbench does not need to launch the agent.
Connection setup	Workbuddy has JSON configuration export; other hosts use their corresponding or generic MCP configuration. Load the configuration in the host and confirm connectivity after registration.
Full workflow rechecked for 0.8.1	This round used two real local hosts: Claude Code and Codex. Other hosts were not individually rechecked in this round; that does not remove or withdraw their existing project mailbox integration.

Optional: let the workbench launch a CLI. This is separate from collaboration through existing sessions. Its built-in execution adapters are Claude Code CLI and Codex CLI; this adapter list is not the list of agents supported by project mailboxes.

The host must support and load the project stdio MCP configuration; registration alone does not establish connectivity. Proactive wake-up also requires a separate host hook. agent-mailbox does not prescribe the model behind an agent.

See the workbench

These screenshots show a synthetic demonstration project in the 0.8.1 local Web UI, without private projects or internal configuration.

The video uses magnified excerpts from the released 0.8.1 interface. It explains the product workflow; it is not a recording of live agent execution or evidence of 0.8.2 platform acceptance.

Choose the correct package

0.8.2 provides separate builds for each platform and chip. macOS Apple Silicon is the established App distribution; Intel, Windows and Linux are additional preview platforms.

Platform	Interface	Current validation boundary
macOS Apple Silicon / arm64	Native App with an embedded workbench, plus local Web	Native regression and extracted-package HTTP/MCP checks; upgrade and embedded UI checked locally before publication.
macOS Intel / x86_64	Separately built native App, plus local Web	Preview: built and launched on a real Intel runner. Full user installation and GUI acceptance are not established.
Windows x64	Packaged local service and browser workbench	Preview: native regression, locking, PowerShell hooks and HTTP/MCP startup checked; not the macOS embedded App shell. Optional CodeGraph is unsupported.
Linux x64	Packaged local service and browser workbench	Preview: native regression and HTTP/MCP startup checked; not the macOS embedded App shell.

These checks do not establish feature parity across all optional managed CLI integrations. Choose the archive matching your operating system and architecture. Preview packages have not received full GUI, original-release upgrade or real-agent acceptance on those platforms. See 0.8.2 scope.

macOS App

Download the macOS archive matching your chip and `SHA256SUMS` from the 0.8.2 release page. Check the archive's SHA-256 against the published list.
Quit an older Agent Mailbox instance before replacing its App. Extract the ZIP, move Agent Mailbox.app into Applications, then open it.
Create a project, register your agents, and add them as members.
Export a separate project mailbox MCP configuration for each agent and load it in that host. Ask it to call project_context and check its mailbox to verify the connection.
Approve a small shared document, assign a mailbox task, and have its recipient explicitly accept, read the pinned version, and submit a result. Review the delivery in the workbench.

The App includes its Python runtime. You do not need a separate Python installation for this path. Existing-session mailboxes use your agent host's own login and execution environment; optional managed execution has separate runtime requirements.

This macOS package is not Developer ID signed or notarized. See the installation guide for the distribution boundary and upgrade steps. Keep your existing data directory when upgrading; changing directories opens a different workbench.

npm launcher

With Node.js 22.13+, use the official scoped package:

npx @polaris-smart/agent-mailbox@0.8.2 --version

npx @polaris-smart/agent-mailbox@0.8.2

On first launch it downloads the matching GitHub Release bundle, verifies its pinned SHA-256, and caches the program with its included Python runtime. GitHub downloads must be reachable. The platform and preview boundaries above still apply. Quit an older instance before switching versions; continue passing your existing --home if you use a custom data directory.

Use the full scoped name: the unscoped agent-mailbox npm package is unrelated. The separate dsh-agent-mailbox integration is not this workbench launcher. See the published npm package.

A handoff from implementation to review

Suppose Claude Code implements a change and Codex reviews it:

You assign the implementation. Attach approved requirements to the project and assign a mailbox task to Claude Code.
Claude Code accepts and reads the pinned versions. It works in its own authorized environment, then submits a report describing the change and its checks.
You assign a separate review. Give Codex the implementation task ID, review criteria, and access to the relevant checkout or commit. Codex can read the delivery through project_delivery(target_task_id=...) and submit its review.
You decide. Accept or reject the result. If further work is needed, the separate follow-up action creates a linked task that must be explicitly accepted again.

A mailbox delivery is an agent's report. It does not automatically capture code changes or prove that tests passed. Second-agent review is a task you arrange, not an automatic approval stage.

Notification is a separate connection

Loading MCP tools does not itself wake an idle conversation. Ask the agent to check its mailbox, or configure a host-specific wake hook. Keep the workbench running while agents use it.

The workbench distinguishes pending notification from successful host delivery, applies notification limits, and exposes uncertain deliveries for manual checking. A successful notification does not mean the agent accepted or completed the task.

Local Web

The Web interface runs on your own machine; it is not a hosted cloud service. Choose a platform from the verified release scope above; a successful Python installation alone does not prove all optional integrations work on that platform.

On macOS or Linux, with Python 3.10+ installed:

python3 -m venv ~/.venvs/agent-mailbox

. ~/.venvs/agent-mailbox/bin/activate python -m pip install 'agent-mailbox==0.8.2' agent-mailbox --version AGENT_MAILBOX_BROWSER=1 agent-mailbox --home ~/.agent-mailbox

The environment flag requests a browser window. Keep the terminal running, and keep the local access URL private. Use the same --home on subsequent launches. If you already use a different data directory, keep that path instead.

The Python package is distributed on PyPI. Native App downloads and Python packages are separate artifacts of the same release.

Optional managed CLI execution

If you want the workbench to launch a coding task, the managed CLI path is separate from connecting an existing session. Prepare its runtime first. Python/source installations require Node.js 22.13+ for that path; follow the managed execution guide.

Eligible local editing tasks run in a separate Git worktree and capture a patch for review. Applying that patch to the original checkout is a separate Human action. A worktree is not an operating-system sandbox, and the workbench does not automatically commit or push.

What stays under your control

Acceptance: submission is not final approval. Human review remains explicit.
Permissions: a member's descriptive responsibility does not grant project-owner or administrator powers.
Data: project records stay locally. Agent hosts may send the material they read to their configured services; local storage does not mean all processing is offline. See Security.
Connections: the existing-session mailbox path is for members registered on the local device. Discovery alone does not prove a live MCP connection. Other hosts need their own verification.
Recovery: keep backups of the workbench home and external project files. Database backups do not include every repository, worktree, or host login. Program replacement and restoration remain manual. Do not open an upgraded database with an older executable; restore a compatible backup first.

The 0.8.1 candidate was checked with two real local agent hosts, explicit acceptance, pinned-resource reads, delivery, and a service restart between acceptance and submission. This bounded test does not establish cross-machine support or recovery at every possible interruption point. See 0.8.1 scope and validation.

Documentation and feedback

[Quick start](docs/GI

앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요

agent-mailbox — Mailbox and Wake System for AI Agent Teams

개요

PopNx MCP의 세 기둥

할 수 있는 일

설치

설치하기 전에

할 수 있는 일

기본 점검i

제작자와 저장소 일치

계속 관리되고 있음

라이선스 있음

엔드포인트 응답

OAuth로 로그인

도구 설명에 숨겨진 지시 없음

기타 카테고리의 다른 서버와 비교i

자주 묻는 질문

대안

Spec Driven Development

Remote Desktop Commander

Signoff

제작자의 README

agent-mailbox

Stop carrying context between conversations

Which agents can join?

See the workbench

Choose the correct package

macOS App

npm launcher

A handoff from implementation to review

Notification is a separate connection

Local Web

Optional managed CLI execution

What stays under your control

Documentation and feedback