Skip to content

News

Devin CLI: 2026.7.16

Product: Devin CLI

Teams can define terminal command allow/deny lists, enforced through CLI permission scopes with exact-command matching and * wildcards.

What changed

  • Teams can define terminal command allow/deny lists, enforced through CLI permission scopes with exact-command matching and * wildcards.
  • Org-level control to disable Devin CLI plugins: when set, the CLI refuses to install or update plugins and skips the skills from any installed plugins.
  • The “Disable CLI access” team setting is now enforced for Devin Local (the CLI hosted in Windsurf), including the bundled agent registry and the allowed-MCP-server allowlist.
  • devin plugins install <source> installs a plugin (and its required plugins) from a GitHub owner/repo, a git URL, or a local path.
  • devin plugins list shows installed plugins with their version and whether they are currently blocked by policy.
  • devin plugins info <plugin> shows the skills a plugin provides and its required, optional, and forbidden lists.
  • devin plugins update [plugin] re-fetches a plugin (or all plugins) at the latest version; local plugins are linked to their source folder so edits are live without re-installing.
  • devin plugins remove <plugin> uninstalls a plugin, leaving any auto-installed required plugins in place.

Source

Why it matters

If you use Devin CLI, skim the official notes above and decide what to try in your next session. Tag the right surface — Cloud vs Desktop vs CLI — before you change workflows.

Fan coverage from Devin Central — not an official Cognition announcement. Devin is a trademark of Cognition.