How would you reason about blast radius when giving a coding agent shell access?
Instruction: Explain what changes once a coding agent can run shell commands.
Context: Checks whether the candidate can explain the core concept clearly and connect it to real production decisions. Explain what changes once a coding agent can run shell commands.
Updated
Official answer available
Read the opening below, then unlock the full answer and practical guidance.
I'd map what the process can read, change, reach over the network, and invoke indirectly. A test command can execute repository code, load plugins, or call services; its harmless name does not make it read-only...
Your preparation path
Work through these questions in order. Read the answer aloud, then explain it in your own words.
1. Start with the foundations
Build the vocabulary and explain the core decisions.
2. Apply it to a real workflow
Practice diagnosis, validation, and everyday tradeoffs.
3. Prepare for senior discussions
Explain failure boundaries, recovery, and production choices.
- A coding agent can modify infrastructure, app code, and data access layers in one task. How do you constrain it? Member answer
- Two coding agents change an API and its client in parallel. How would you integrate their work safely? Member answer
- A coding-agent hook runs before the repository trust prompt. What is wrong with that design? Member answer
Related Questions
-
easy
-
easy
-
easy
-
easy
-
easy
-
easy