Async Parallel Antigravity for Codex & Claude Code

Name: Async Parallel Antigravity for Codex & Claude Code
Author: varadfromeast

作者：varadfromeast版本 0.1.12i★ –i在你的电脑上运行

注册名称io.github.varadfromeast/codex-agy-bridge

安装

概览

作者提供的说明（英文原文）

Run parallel, resumable, human-operable Antigravity CLI sessions from any MCP agent harness

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： AGY_CMD

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "codex-agy-bridge": {
      "command": "uvx",
      "args": [
        "codex-agy-bridge"
      ],
      "env": {
        "AGY_CMD": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add codex-agy-bridge --env AGY_CMD=your-value -- uvx codex-agy-bridge

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "codex-agy-bridge": {
      "command": "uvx",
      "args": [
        "codex-agy-bridge"
      ],
      "env": {
        "AGY_CMD": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "codex-agy-bridge": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "codex-agy-bridge"
      ],
      "env": {
        "AGY_CMD": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

AGY_CMD env
Absolute path to the authenticated Antigravity CLI executable

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 varadfromeast 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32686 个服务器的 0%
发布到注册中心的时间比此分类中其他 32686 个服务器的 44% 更新
基础检查结果等于或优于此分类中其他 32686 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Async Parallel Antigravity for Codex & Claude Code 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.12）于2个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Microsoft Exchange Online MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ 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前天更新

安装

Microsoft Exchange Online MCP

作者：servosity

Exchange Online admin for MSPs: forwarding audits, EWS posture and offboarding, no PowerShell

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

codex-agy-bridge

Run Antigravity from an agent harness as durable, parallel, human-operable agy sessions over MCP.

codex-agy-bridge wraps the official Antigravity CLI with a resumable MCP control plane. Agent harnesses like Codex, Claude Desktop, or your own GPT/Claude-powered MCP client can start agy runs, wait on sparse events, attach a real terminal, send guarded input, cancel safely, continue exact conversations, and collect final results later by run_id.

Quick Install

Prerequisites:

Codex CLI for the command below, or another local stdio MCP-capable harness
The official Antigravity CLI (agy), already authenticated locally
uv / uvx
tmux and a supported terminal launcher:

# macOS

brew install tmux

Debian/Ubuntu Linux (x-terminal-emulator is also supported)

sudo apt install tmux gnome-terminal

Check the required commands:

codex --version

agy --version agy models uvx --version tmux -V

Day 0 Authentication

agy --version only proves the binary exists. Before adding the MCP server, run agy models; if Antigravity asks you to sign in or reports that you are not logged in, start a visible session and complete the browser/login flow:

agy --prompt-interactive "Authenticate Antigravity and then exit."

agy models

After agy models succeeds, install or restart the MCP server. If a bridge run still hits auth, agy_run_start returns status="auth_required" and opens a visible agy authentication session by default. Complete sign-in there, then start a fresh run. You can also use agy_run_observe(view="terminal") or agy_admin(action="doctor") to inspect the auth-required status.

Install from PyPI with the Codex CLI:

codex mcp add codex-agy-bridge \

--env AGY_CMD="$(command -v agy)" \ -- "$(command -v uvx)" codex-agy-bridge@latest

Restart the harness, then verify in Codex if you used the command above:

codex mcp get codex-agy-bridge

codex mcp list

Remove it with:

codex mcp remove codex-agy-bridge

For Claude Desktop or a custom MCP client, use the same stdio command shape: uvx codex-agy-bridge@latest with AGY_CMD set to the authenticated agy executable.

What Makes It Different

Parallel Antigravity sessions: launch multiple independent agy runs, each with its own durable state, logs, transcript projection, and result.
Human-operable terminals: foreground runs live in persistent tmux sessions, so Terminal.app can attach without killing the agent.
Resumable MCP control: MCP calls can time out, the harness can restart, and the run can still be observed later by run_id.
Goal orchestration: create a goal, start named targets with bounded parallelism, and inspect the whole batch as one coordinated effort.
Sparse wake events: agy_run_wait short-polls lifecycle, attention, progress, and terminal events without transcript-polling spam.
Guarded input: agy_run_input can reject stale writes when event or transcript cursors changed after the caller observed the run.
Trajectory-aware observability: bounded transcript summaries and terminal evidence are exposed without private model reasoning.
Operational hygiene: duplicate active starts are deduplicated, process groups are cancelled safely, and completed result artifacts are preserved.

Install Details

If You Are An Agent Reading This

Help the user install it; do not silently mutate their machine.

Verify prerequisites first:

command -v codex

command -v agy command -v uvx command -v tmux agy --version agy models

If anything is missing, ask before installing it.
If agy models reports an auth error, help the user complete the Day 0 authentication flow above before adding the MCP server.
Then run:

codex mcp add codex-agy-bridge \

--env AGY_CMD="$(command -v agy)" \ -- "$(command -v uvx)" codex-agy-bridge@latest

Verify:

codex mcp get codex-agy-bridge

codex mcp list

Tell the user to restart their agent harness so the new MCP tools load.

PyPI

The Quick Install command stores an stdio MCP server definition. When the agent harness starts the server, uvx resolves codex-agy-bridge@latest from PyPI, installs it into an isolated cached environment, and runs the codex-agy-bridge console script. AGY_CMD pins the bridge to the user's already-installed and authenticated agy executable.

Do not replace $ or $(...) manually in the command. In POSIX shells, $(command -v agy) and $(command -v uvx) expand to absolute executable paths.

GitHub

Use this when you want the repository version directly:

codex mcp add codex-agy-bridge \

--env AGY_CMD="$(command -v agy)" \ -- uvx --from git+https://github.com/varadfromeast/codex-agy-bridge \ codex-agy-bridge

Local Development

git clone https://github.com/varadfromeast/codex-agy-bridge.git

cd codex-agy-bridge uv sync --extra dev

codex mcp add codex-agy-bridge \ --env AGY_CMD="$(command -v agy)" \ -- uv --directory "$PWD" run codex-agy-bridge

How It Works

flowchart LR

H["Agent harness (Codex, Claude, custom MCP client)"] M["codex-agy-bridge MCP stdio server"] S["Durable control plane runs, goals, events, results"] W["Detached run supervisor"] A["Antigravity CLI agy"] T["Persistent tmux session human attach/input"] L["Local Antigravity trajectory files"]

H <-->|"MCP tools"| M M <--> S S --> W W --> A W <--> T A --> L W -->|"bounded transcript projection"| S T -->|"terminal logs and attention prompts"| S

The bridge keeps the MCP server responsive while detached supervisors own the long-running agy processes. State and events are persisted locally, so a run can continue after the original MCP call returns. For the deeper process model, see docs/ARCHITECTURE.md. For the MCP control-loop vision, see docs/MCP_VISION.md.

MCP Tools

Tool	Purpose
`agy_run_start`	Start, continue, or open an interactive foreground run
`agy_run_wait`	Short-poll until selected runs emit sparse wake events
`agy_run_observe`	Read full, status, transcript, or raw terminal views
`agy_run_input`	Send input with optional event/transcript preconditions
`agy_run_cancel`	Cancel one active run
`agy_run_result`	Read final result metadata or bounded result chunks
`agy_goal`	Create goals, start targets, and read aggregate status
`agy_admin`	Read diagnostics, models, plugins, validation, and changelog

Omit model (or pass null) to let Agy choose its default: the bridge stores model: null and does not send --model. This applies to runs, review tools, and goals, whose targets inherit their goal's selection. Explicit selections are validated against agy models, including the bridge's former Gemini 3.5 Flash (Medium) default; unknown and empty selections are rejected. The bridge never substitutes the first catalog entry. agy_admin(action="models") reports default_model: null and default_model_source: "agy_cli"; this describes delegation, not an observed effective provider model.

Existing persisted runs and goals retain their model strings and remain readable. They are not silently migrated to a different model. New launches from an old goal revalidate its selection and reject it if it is no longer available; create a new goal with an available model or omit the selection to delegate to Agy. Previously reserved runs retain their original command policy. New delegated requests have distinct deduplication keys from explicitly selected models. Older bridge versions that require a string goal model cannot read new null-model goals; avoid downgrading with those goals in use.

Typical flow:

agy_run_start -> agy_run_wait -> agy_run_observe -> agy_run_result

In Codex MCP, tools may be exposed with the server prefix, for example codex_agy_bridge_agy_run_wait. Run responses include exact wait_call arguments; note that agy_run_wait always takes run_ids: ["..."], even for a single run. Supported wait conditions are any_attention, any_terminal, all_terminal, any_event, and aliases attention, terminal, finished, finish, complete, completed, result, all_finished, all_complete, and all_completed.

Use agy_goal when the harness should split work into named targets with a shared objective and bounded parallelism.

Configuration

Variable	Default	Purpose
`AGY_CMD`	`agy` on `PATH`	Exact Antigravity executable
`AGY_BRIDGE_STATE_DIR`	`~/.local/state/codex-agy-bridge`	Durable run and goal state
`AGY_BRIDGE_AGY_ROOT`	`~/.gemini/antigravity-cli`	Antigravity conversations and trajectories
`AGY_BRIDGE_MAX_PARALLEL`	`50`	Global concurrent-run limit
`AGY_BRIDGE_COMPLETION_STABILITY_SECONDS`	`150`	Time a final marker must remain stable
`AGY_BRIDGE_MCP_WAIT_SLICE_SECONDS`	`120`	Max seconds a single `agy_run_wait` MCP call blocks before returning a snapshot so gateways do not time out

Run state survives MCP server restarts under ~/.local/state/codex-agy-bridge/.

Status And Risk

This project is experimental. It currently targets Python 3.11+, macOS or Linux with a supported terminal launcher, tmux, and Antigravity CLI 1.0.8-compatible commands and trajectory files.

Antigravity is an agentic CLI. It can read and write files, execute commands, and access the network with the current user's privileges. This bridge is not a sandbox or security boundary.

The bridge always enables Antigravity's dangerous permission-skip policy so unattended runs do not stall on CLI approval prompts. Any dangerously_skip_permissions=false input is rejected; the only allowed value is true. sandbox=true and additional_directories are CLI policy hints, not filesystem containment.

The bridge does not read or copy Antigravity OAuth credentials. It invokes the installed agy binary and reads ordinary local conversation metadata and trajectory files.

Development

git clone https://github.com/varadfromeast/codex-agy-bridge.git

cd codex-agy-bridge uv sync --extra dev uv run pytest uv run ruff check . uv build

Run the server directly:

uv run codex-agy-bridge

The server uses stdio transport. Do not print diagnostic text to stdout; it would corrupt MCP framing.

Publishing

A pushed version tag runs .github/workflows/publish.yml, which verifies versions, runs checks, builds distributions, publishes to PyPI through GitHub OIDC, creates a GitHub release, and publishes server.json to the MCP Registry.

Compatibility

The current reader expects Antigravity trajectory JSONL under:

~/.gemini/antigravity-cli/brain/<conversation-id>/

.system_generated/logs/transcript.jsonl

If Antigravity moves to SQLite or a local daemon API, a new adapter can replace this reader without changing the MCP tool contract.

License

MIT