| FMRS | 64 / 100 · C | 76 / 100 · B |
|---|
| Reliability | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 9 / 20 | 14 / 20 |
|---|
| Maintenance | 14 / 20 | 18 / 20 |
|---|
| Documentation | 16 / 20 | 17 / 20 |
|---|
| Setup experience | 13 / 20 | 14 / 20 |
|---|
| Best for | - Long, multi-turn coding agent sessions
- Developers using several CLI clients at once
- Teams that need local-only operation, no telemetry, and a commercially usable license
- Teams that want to verify compression claims with a reproducible benchmark rather than vendor assertions
| - Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
- Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
|
|---|
| Not for | - Anyone who wants a bare MCP server without installing client hooks or plugins (the README states adding the server alone does not enforce anything)
- Scenarios where no request content may ever be written to local disk (the proxy writes elided payloads to spill files in the OS temp directory)
- Users who need a hosted service or cloud account
- Environments that cannot run Node.js 22+
| - Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
- Environments with strict network isolation for private repos that can't reach the official remote endpoint
|
|---|
| Required permissions | - Read and write project files for smart reads, diffs and edits
- Install and run client lifecycle hooks that intercept or re-route tool calls before execution
- Write cache, knowledge graph, logs and elided-content spill files to local disk
- Optionally start a compression proxy process bound to the local loopback address
- Read native CLI usage receipts for token accounting and pricing
| - A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
- Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
|
|---|
| Risks and side effects | - The server refuses or rewrites built-in tool calls (Read, Grep, Glob, Edit, Write, and shell cat/head/grep -r), which in enforce mode can interrupt existing workflows
- Recoverable elided content is written with 0600 permissions under token-optimizer-spill/ in the OS temp directory and is not deleted while the proxy runs; a kill signal or power loss leaves the directory behind to be cleaned up by hand
- The proxy does not inspect written content for secrets, so a secret in your conversation can reach a spill file like any other text
- The local knowledge graph and cache hold project structure, content hashes and derived findings
- Several comparisons in the README are development-stage or incomplete studies; the project itself states that superiority was not established and that aggregate intervals still span 1.0
| - Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
- In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
|
|---|
| Supported clients | Claude Code, Codex, GitHub Copilot CLI, Gemini CLI, Qwen Code, Cursor, Cline, OpenCode, Kilo, Windsurf, Roo Code, Zed, Amp, Continue, Crush, Droid | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp |
|---|
| Tools | 11 | 15 |
|---|