Skip to main content
Devin CLI is a local agent that runs on your machine with access to your local files, tools, and environment — similar to Cascade in Devin Desktop. It shares the same agent harness as the Devin Local agent. Because it is a newer agent, Devin CLI does not yet implement all of the same features and controls as Cascade. Many of Cascade’s controls are replaced by more flexible mechanisms — for example, permissions, hooks, and team settings.

​
Limitations

The following features are not currently supported with the Devin Local agent:
  • Memories — The Devin Local agent does not persist memories between sessions. Migrate your critical memories to skills.
  • Workflows — Workflows are not available with the Devin Local agent. Migrate your workflows to skills.
  • Codemaps — The Devin Local agent does not yet read codemaps.
  • Code Lenses - Currently code lenses do not yet trigger the Devin Local agent.
  • Fast Context - Devin Local uses subagents to explore code, but doesn’t have the same fast context UI as Cascade.
  • App Deploys - The Devin Local agent does not support app deploys.
  • Conversation Sharing - Conversation sharing is not yet available with the Devin Local agent.
The Devin Local agent does support rules and AGENTS.md files as well as skills for providing persistent context and reusable workflows.

​
Analytics

The Devin Local agent does not yet report all of the analytics that Cascade collects. The following data is collected for Cascade but not for Devin Local:
  • Tool usage — The cascade_tool_usage data source (per-tool call counts such as Code Edit, Run Command, Search Web, and MCP Tool) only includes Cascade sessions. Tool calls made by the Devin Local agent are not reported. To monitor or restrict tool usage with the Devin Local agent, use hooks and permissions instead.
  • Lines suggested and accepted — The cascade_lines data source (daily lines of code suggested and accepted) does not include code written by the Devin Local agent.
  • Write/Read mode — The Devin Local agent does not report a Cascade mode, so the mode field in the cascade_runs data source is not populated for Devin Local activity.
Devin Local activity is still included in the cascade_runs data source (model usage, messages sent, and credit consumption) and in the Cascade Data source of the Custom Analytics API. The Devin CLI does not report analytics for hybrid deployments.

​
Enterprise controls

Enterprise admins can configure the Devin Local agent through team settings, including new controls only available with the Devin Local agent:
  • Sandbox enforcement - Require sandbox mode for all users and configure organization-wide domain filtering rules
  • Granular permissions - Control which actions the agent can take with more fine-grained permissions
  • Network enforcement - Control network access with allowed and denied domains
Additionally, the “Enable Cascade” control can be used to disable the legacy Cascade agent entirely to ensure your team follows the new controls available with Devin CLI.

​
Unsupported enterprise controls

The following legacy enterprise controls are not available with the Devin Local agent:
  • Restrict Tool Calls to Workspace - by default, the Devin Local agent can only read/edit files within the workspace. Custom permissions are a more flexible replacement that can be used to replicate the same rules.
  • App Deploys - App deploys are not yet supported with the Devin Local agent.
  • Conversation Sharing - Conversation sharing is not yet supported with the Devin Local agent.
  • Auto Run Terminal Commands - The Devin Local agent uses its own permissions model instead of auto-execution levels.
  • Attribution Filtering - Attribution filtering is not yet supported with the Devin Local agent.
  • Enable or disable Cascade for your team - This setting only controls the legacy Cascade agent and does not apply to the Devin Local agent or the Devin CLI.
  • Global tool calling disabled - If you previously disabled tool calling entirely, write an equivalent permission policy for Devin CLI instead.
  • Terminal allow lists - Implement an equivalent permission policy for Devin CLI to allow specific terminal commands.
  • Terminal deny lists - Implement an equivalent permission policy for Devin CLI to deny specific terminal commands.

​
Further reading