geondongkim/geond-agent-protocol

Geond Agent Protocol
Shared memory and coordination for AI agents that work on the same repo.
Geond gives Copilot Chat, Codex, Claude Code, Antigravity, Manus, CLI agents,
and MCP-capable tools a durable place to share what happened, why it happened,
what changed, what is reserved, how it was validated, and what the next agent or
reviewer should do.
Geond is local-first by default. Your editor, CLI, MCP server, dashboard, and
importers can run on your machine against local PostgreSQL. When a team wants
multi-machine collaboration, those same local processes can point at a shared
PostgreSQL-compatible profile such as Azure Database for PostgreSQL.
Geond is alpha software. Repository-centered memory, MCP, CLI, dashboard read
models, reservations, handoffs, code graph indexing, usage evidence, benchmarks,
and shared PostgreSQL validation are implemented today. Enterprise IAM,
row-level security, dedicated MCP audit streams, broad SaaS adapters, and
dependency-expanded automatic reservations are roadmap areas.
> About the name: Geond is inspired by an Old English root of "beyond" and is
> pronounced "Jee-ond". The project helps agents go beyond stateless prompts by
> connecting them to inspectable shared memory.
Quick Start
Prerequisites: Python 3.11+, uv, Docker with Compose, Git, and ripgrep. See
docs/developer_setup.md for OS-specific notes.
Start the MCP server:
Preview or write MCP client config:
Serve the read-only dashboard:
Open the printed localhost URL. More MCP client examples are in
docs/mcp_client_config.md.
MCP Server And Glama Release
Run the stdio MCP server directly:
Run it from a Docker image:
GEOND_DATABASE_URL points Geond at PostgreSQL. Local development usually uses
the Compose database from the quick start. Team mode can use
GEOND_DATABASE_PROFILE=azure plus AZURE_GEOND_DATABASE_URL to share memory
across machines while keeping each MCP process local.
For registry validation, Glama should deploy this repository's Dockerfile,
create a Glama release, and call get_geond_server_info first. That tool does
not require a database connection, so it is safe for browser-based smoke tests.
Three representative MCP workflows:
1. **Start coordinated work:** review_workspace_context -> reserve_files -> edit -> record_changeset.
1. **Explain prior context:** search_dev_memory -> explain_change -> get_changeset_detail.
1. **Leave a handoff:** record_agent_action -> record_handoff_summary -> list_handoff_summaries.
What Geond Makes Possible
| Scenario | What you can do | Proof and entrypoint |
| --- | --- | --- |
| AI pair coding across agent tools | Let different agents work on the same repo through shared memory, reservations, handoffs, and review context. Verified locally with Codex and Antigravity; the same pattern applies to Copilot, Claude Code, Continue, Manus, or custom MCP agents. | docs/antigravity_codex_geond_verification.md, docs/mcp_client_config.md |
| Multi-PC collaboration | Run geond-mcp, CLI, and dashboard locally on each machine while Windows, MacBook, CI, or another teammate all read and write the same shared PostgreSQL profile. | docs/azure_validation/team_collab_validation.md, docs/azure_validation/README.md |
| PM and reviewer dashboard | Review agent lanes, sessions, handoffs, changesets, code risk, usage evidence, timeline, and lineage without reading raw MCP JSON. | uv run geond dashboard serve, docs/agent_activity_dashboard.md |
| Safe parallel editing | Ask agents to review current context, reserve files or symbols, record changesets, and leave structured handoffs before another agent edits the same target. | docs/agent_operating_loop.md, uv run geond review-context ... |
| Cross-agent memory import | Import Copilot Chat, Codex, Claude Code, Antigravity, and Manus task evidence into one redacted search and evidence model. | docs/agent_testbeds.md, docs/manus_integration.md |