Match a job Paths Subjects Questions Quizzes Pricing
Overview Read Practice

Practice — Case Study: Design a Coding Agent (5 questions)

Pro content

Sign up free, then start a 14-day Pro trial — no card needed.

Advanced Open Free

Designing the Permission Model for a Coding Agent Permalink →

You are designing a terminal coding agent that can read files, edit files and run shell commands in a developer's repository. A colleague proposes: "Give it one bash tool and put 'never run destructive commands' in the system prompt — the model is smart enough."

  1. Explain why that is insufficient, using a concrete failure scenario.
  2. Design the permission model: how you classify actions, what the defaults are, and which mechanisms enforce them.
  3. How does the design change between an interactive session on a developer's laptop and an unattended run in CI?

Share this question

Advanced Open Pro

Fitting a 300k-Line Repository into a 200k-Token Window

Unlock this question →
Advanced Open Pro

Cost per Task and the Levers That Move It

Unlock this question →
Advanced Open Pro

Choosing and Shaping the Tool Set

Unlock this question →
Advanced Open Pro

Evaluating a Change to the Agent's System Prompt

Unlock this question →

We use cookies for product analytics to improve OmniAtlas. See our Privacy Policy.