Devin (Cognition)
What Devin’s own help pages, docs and terms said on 1 October 2026, by the same six questions we ask of every agent. We didn’t test it for this page. “Not documented” means we didn’t find it on the vendor’s pages; it doesn’t mean the feature is missing.
Coding agent
- Can you limit it?
- Repo choice; CLI rules
- Does it ask first?
- CLI modes; cloud: approval for deploys
- Can you stop it?
- Terminate by API
- Is there a record someone outside can check?
- Not documented
- What about sub-agents?
- Managed Devins
- Can you test it yourself?
- Session API, MCP
What the vendor’s pages say
"Devin uses the permissions granted at the organization level", not each user's (GitHub integration). The CLI has five modes, from Normal (the default) to Bypass, and admin deny rules "remain active regardless of the user's permission mode" (CLI permissions). In the cloud, "every deploy requires your explicit approval" (deployments), and Devin can hand work to "a team of managed Devins" (advanced capabilities). A session can be ended through the API, after which it "cannot be resumed" (API).
Every statement above was checked on the vendor’s own page on 1 October 2026; each links to its source.
Run this test on yours
Delegus Check gives your agent a permission and a one-hour test server, then shows every action it tries and what was refused. It works today with agents that accept a custom MCP server, including Claude on any plan.
Corrections
Vendors and readers: if anything here is out of date, write to hello@delegus.ai and we’ll fix it. Each change is listed here with its date.
- 1 October 2026: first published. All vendor statements checked that day.