| FMRS | 67 / 100 · C | 76 / 100 · B |
|---|
| Reliability | 10 / 20 | 13 / 20 |
|---|
| Security and permissions | 14 / 20 | 14 / 20 |
|---|
| Maintenance | 13 / 20 | 18 / 20 |
|---|
| Documentation | 17 / 20 | 17 / 20 |
|---|
| Setup experience | 13 / 20 | 14 / 20 |
|---|
| Best for | - Large repositories and document collections
- Multi-turn, log-heavy AI agent sessions
- Teams requiring evidence traceability, recovery, and audit records
- Developers who want local processing and control over the model integration path
| - 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 | - Small projects or prompts already within budget
- MCP-only setups that require automatic interception of every model request
- Tasks that require the full context to remain visible at all times
- Treating scoped benchmark results as guarantees across all models and production workloads
| - 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 | - Requires access to configured local project code, documents, logs, or other context data
- MCP attachments can be scoped by project and grant scope, given an expiry, and revoked
- Proxy mode requires the user to configure the relevant provider API key; Entroly does not choose the provider or receive its credentials
| - 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 | - Compression can omit relevant evidence; review Context Receipts and verification results
- Exact recovery depends on retained receipts and the local recovery store; deleting that state removes the recovery path
- MCP integrations do not automatically intercept every model request; provider savings require routing through the Entroly proxy
- Unknown or ambiguous structures pass through unchanged, and unsafe overflow may produce HTTP 413
- README benchmarks are scoped to particular datasets, budgets, models, and versions, not universal guarantees
| - 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 Desktop, Claude Code, Codex, OpenClaw, Cursor, Windsurf, VS Code MCP clients, Zed, GitHub Copilot CLI | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp |
|---|
| Tools | 0 | 15 |
|---|