GitHub Copilot CLI vs Verdent

GitHub Copilot CLI 72

Framework reading, adapted to a harness driven by a pipeline. --available-tools and --excluded-tools shape the tool list and --deny-tool removes tools, and MCP tool discovery recovers without a restart (20). --max-autopilot-continues caps autopilot, and a turn timeout applies to background work in -p (15). JSON output, and a 2026 release replaced a misleading auth error with the real cause (12). --resume and --continue, and permission prompts survive a resumed session (15). An SDK exists, per the changelog, but we didn't check its languages, and a headless run needs explicit allow flags to do anything (10).

Verdent 35

Harness reading. MCP servers per project or globally, subagents, skills and rules, but no per-tool disabling or deferred loading found (10). No output-size, turn-limit or budget controls for a run were found beyond credit balances (5). No exit codes or error format, since there is no headless mode (3). Parallel workers in git worktrees and a review column make runs reviewable and reversible, with no resume by ID documented (10). No CLI, API or SDK. A pipeline can only reach Manager through a paired Telegram, Slack or Feishu bot (7). 10+5+3+10+7 = 35.

GitHub Copilot CLI 65

Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. Since 1.0.100 (19 October 2026) --disable-client-telemetry turns off the telemetry the CLI sends, which the command reference says doesn't affect server-side telemetry. Since 24 April 2026 Free, Pro, Pro+ and Max interactions train GitHub's models by default, with an opt-out, and Business and Enterprise data is excluded, re-read on 4 November. A fine-grained token with only the Copilot Requests permission works for CI (16). Asks before the first use of each modifying tool, deny rules that beat --allow-all-tools, URL and path permissions, trusted directories and enterprise managed settings. Local sandboxing is generally available since 1.0.93 (7 October 2026) and off by default, enterprises can require it fail-closed, and since 1.0.100 the sandbox allows local network access by default. Assisted Permissions, where a model approves requests it judges safe, left experimental mode in 1.0.104. The CLI still can't enforce two organisation MCP policies (17). The sandbox proxy filters hosts, sandboxed shells withhold GITHUB_TOKEN since 1.0.92, and content exclusion applies, but we found no prompt-injection guidance for the CLI (9). OpenTelemetry export with GenAI spans, opt-in, with enterprise capture controls since 12 October, and session logs (13). Two advisories with CVEs in 2026 and none since on OSV, re-read on 4 November, but no SECURITY.md in the repository and an expired security.txt on github.com per the 26 September check, which the proxy still refuses. We didn't check GitHub's bug bounty (10). SOC 2 isn't scored on the framework reading. 16+17+9+13+10 = 65.

Verdent 33

Framework reading (telemetry defaults, approvals, guardrails, sandboxing). Conversation history and tool results go to Verdent's US servers and on to Azure, Bedrock or Vertex, with zero data retention stated for Vertex and Bedrock only. Event logging to log.verdent.ai has no documented opt-out. BYOA keys stay on the machine (10). Plan Mode is read-only, Agent Mode asks before destructive commands and edits outside scope, and workers are isolated by git worktree, but there is no sandbox or network control and the approval list isn't enumerated (9). No prompt-injection guidance found, while web search and fetch results enter the context (2). Usage history in the dashboard, no audit log found (5). A security page with a disclosure address and a five-day acknowledgement, SOC 2 and ISO/IEC 42001 being pursued rather than held, no security.txt and no bug bounty (7). 10+9+2+5+7 = 33.

GitHub Copilot CLI 40

Harness reading of the published rubric. No payment protocol (0). Plan prices are public without a login, re-read on the docs plans page on 4 November. Pro $10, Pro+ $39, Max $100 a month, Business $19 and Enterprise $39 a seat, with usage past an organisation's pool at $0.01 per AI credit (20). Copilot Free includes the CLI with an allowance of AI credits and auto model selection only, and no card per the 2 October check (20). A person signs in to GitHub or creates the token (0). 0+20+20+0 = 40.

Verdent 20

Harness reading of the published rubric, scored on the Verdent subscription the agent needs. No payment protocol (0). Plan prices from $5 a month, top-up prices and the credit value of about $0.059 are public without a login (20). Free Mode and the free trial ended on 29 October 2026, so there is no free tier (0). A person signs up in a browser (0). 0+20+0+0 = 20.

GitHub Copilot CLI 74

Proprietary licence with clear terms for running and redistributing (15). The data-use page dates the training change (24 April 2026), says which plans it covers and how to opt out, and says Business and Enterprise data isn't used, re-read on 4 November, but we didn't find retention periods for CLI sessions (18). On 15 October 2026 GitHub gave dated notice that Claude Opus 4.8, Claude Opus 5 and GPT-5.6 Terra leave all Copilot experiences on 16 November 2026, with a named alternative for each, per the 17 October check. Breaking changes are mostly marked in a dated changelog. There's no written deprecation policy or notice period, the same reading as openai-codex and gemini-cli (15). The command reference now lists --disable-client-telemetry, added in 1.0.100 on 19 October, so client telemetry is disclosed with an opt-out, but no page says what it sends. OpenTelemetry export is documented and opt-in (12). 15+18+15+12 = 60.

Verdent 55

Proprietary, under terms from Verdent AI, Inc. that are clear on use and ownership (15). The privacy policy and security page agree that data stays in the US and that input isn't trained on without consent, and the security page lists subprocessors. The privacy policy gives no retention periods, names MiniMax as a provider the security list leaves out, and deletion is by email request (14). The credit bonus carries a promise of 15 days' notice, but Free Mode was retired on the day v2.18.0 shipped and no deprecation policy was found (6). Subprocessors and their locations are listed, and the domains the app calls are named, with event logging undescribed (12). 15+14+6+12 = 47.

GitHub Copilot CLI 72

Framework reading. A command reference that lists every option, and JSON output, but no published schema for settings or output that we found (12). docs.github.com/llms.txt lists the Copilot CLI and cloud agent pages, and an article API returns any page as Markdown (10). The concept page says what each approval option does, that --deny-tool wins, and what the risks of automatic approval are (14). Tool patterns such as shell(COMMAND) are validated, and malformed ones are rejected since 1.0.x (10). Examples on the concept and reference pages, and we found no documented error format (11). A dated changelog per release with breaking changes marked (15).

Verdent 55

Framework reading for a harness. No schema for settings or output, only mcp.json examples in the standard mcpServers shape (5). Every current docs page has a Markdown twin at the same path with .md, though no llms.txt (10). The docs say when to use Agent Mode or Plan Mode and what Plan Mode can't do, but the Agent Mode page lists the actions that need approval only as "certain tool executions" and "destructive operations" (12). Modes and BYOA agent types are enumerated, permissions are not (5). Examples on the MCP, BYOA and messaging pages, and a recovery page, with no error codes (8). Version numbers and a dated public changelog (15). The archived 1.0 docs are still served beside the current ones. 5+10+12+5+8+15 = 55.

GitHub Copilot CLI 77

1.0.105 on 27 October 2026 per the changelog and its tag, 8 days before this check. Tags 1.0.106-1 to 1.0.106-8 (30 October) are pre-releases with no changelog entry and don't count (30). 25 dated releases from 1.0.79 (10 August) to 1.0.105 (27 October) in the 90 days from 6 August (20). Issues are labelled and triaged, with automation for stale and unanswered reports, though about 1,900 stay open, per the 1 October check (14). An SDK the changelog keeps updating (session APIs, MCP management, OAuth tokens), languages unchecked (10). Closed source and a bundled npm build, so no CI or dependency health to read (3). 30+20+14+10+3 = 77.

Verdent 61

Closed service. v2.18.0 on 29 October 2026, eight days before this check (30). More than three dated releases in the 90 days from 8 August, among them 2.10.0 to 2.18.0 (20). A dated public changelog, a support address, Discord and a subreddit, with no public tracker to read reply times (8). No official SDK or MCP server to keep current (0). No public packages or CI to judge (3). 30+20+8+0+3 = 61.