Interview Bank

Mastering Codex and the OpenAI Agents SDK in 5 Days

D2 Codex, Level Up: Cloud Tasks, Code Review, MCP Integration, Custom Instructions, IDE Integration

• A cloud coding agent can run many tasks in parallel with nobody around to approve steps. Where should its approval boundary sit?云端 coding agent 能同时跑很多任务，但没有人在旁边点头。它的审批边界应该画在哪里？

  Common in ChinaCommon overseasIntermediate#coding-agent#cloud#approvals

  How to reason about it · think before answering

  1. This checks whether you noticed the approval model changed: local means step-by-step approval, cloud means authorize upfront and review afterwards.
  2. Split the boundary across three moments: before the task (environment config decides network, variables, dependencies), during (container isolation), after (a human reviews the diff before any PR).
  3. Conclude that the cloud boundary is two gates, environment config plus pre-PR human review, with nobody in between; hence no production secrets, network off by default, merge rights stay human.
  4. Add the engineering angle: draw boundaries between parallel tasks too; tasks that touch the same files should not run concurrently.
  5. Expect the follow-up: can it auto-merge? Only in low-risk repos for fully green PRs, with rollback in place, and treat enabling auto-merge as a change that itself needs approval.

  分析过程 · 先想清楚再作答

  1. 这题考的是你有没有意识到「审批模型变了」：本地是逐步审批，云端只能事先授权、事后审阅。答成「跟本地一样弹窗」说明没用过。
  2. 拆法是把边界分成三个时间点：任务开始前（环境配置决定能联网什么、有哪些变量、装什么依赖）、任务执行中（容器隔离，改动只在容器里）、任务结束后（人审 diff 再决定开不开 PR）。
  3. 结论是：云端的审批边界就是「环境配置 + PR 前人工审阅」这两道门，中间不再有人；所以生产密钥不能进环境、公网默认关、合并权限保留在人手里。
  4. 补一条工程视角：并行任务之间的边界也要画——互相会改同一批文件的任务不要同时派，否则合并成本吃掉并行收益。
  5. 可预期的追问：能不能让它自动合并？可以在低风险仓库对通过全部测试的 PR 这么做，但要保留回滚手段，并且把「自动合并」本身当成一个需要审批的配置变更。

  Key points

  • No step-wise approval in the cloud; the boundary becomes upfront environment config plus post-hoc human review
  • Keep production secrets out, network off by default, merge rights with humans
  • Draw boundaries between parallel tasks: never run file-overlapping tasks concurrently
  • Auto-merge only for low-risk repos with fully green PRs, with rollback ready

  答题要点

  • 云端没有逐步审批，边界变成事前的环境配置与事后的人工审阅两道门
  • 环境里不放生产密钥、公网默认关、合并权限保留给人
  • 并行任务之间也要画边界：会改同一批文件的任务不同时派
  • 自动合并只适用于低风险仓库且全绿的 PR，并保留回滚