Skip to main content
Devin Coach helps your team get more out of every ACU by coaching users directly where they work. It checks prompts in the session input box before they’re sent and surfaces a suggestion when it spots a pattern that tends to waste usage — and gives admins visibility into how those suggestions land across the organization. Devin Coach pairs guidance with the enforcement side of cost management: see Usage policies for per-user ACU limits and efficiency-based approvals.

​
Suggestions in the input box

As a user writes a prompt, Devin Coach analyzes the draft and shows an inline suggestion below the input box when it detects an issue. Clicking the suggested action applies the fix in place.

​
Configuring Devin Coach

Admins control how prompt checking behaves with the Prompt precheck setting on the Devin Coach settings page:
  • Warning and confirmation — show the inline suggestion and ask the user to confirm before sending a flagged prompt.
  • Warning only (default) — show the inline suggestion but never block sending.
  • Off — don’t check prompts before sending.
For enterprises, the setting is managed at the enterprise level and inherited by all organizations. Changing it requires the enterprise settings management permission (or organization settings management for standalone organizations).

​
Coach analytics

Admins can see how users respond to coaching over the last 30 days:
  • Organization: Settings > Devin Coach (requires the view organization metrics permission).
  • Enterprise: Enterprise Settings > Devin Coach, with a filter to narrow to a single organization (requires the view account metrics permission).
  • Personal: each user sees their own suggestion outcomes on their My analytics page.
Each view shows the number of suggestions shown, accepted, and rejected, the acceptance rate, a daily trend by outcome, and a per-suggestion-type breakdown — select a row in the suggestions table to focus the trend on that type.

​
Blockers

The organization view also lists blockers — issues Devin reported hitting at runtime in the last 30 days, such as missing permissions, blocked network access, or broken environments. Recurring blockers are grouped so you can see what a single fix would unblock, and each entry links back to the session where it occurred.