Interview Bank

From Frontend Engineer to Agent Engineer in 30 Days

D3 Getting Started With the Pi SDK: the Three-Layer Architecture, Comparing It to the Agent Loop (dg P01/P02/M02/M03)

• What problems does an agent framework's built-in agent loop have to solve?Agent 框架内部的 Agent Loop 一般要解决哪些问题？

  Common in ChinaCommon overseasBasic#agent-loop#framework-design

  How to reason about it · think before answering

  1. This looks like a checklist question, but the real signal is whether you have written such a loop yourself. 'Call the model repeatedly until it stops' reads as documentation-only knowledge.
  2. The safest structure is to walk down your own hand-written loop line by line, because every line is one problem the kernel must own: issue the model request, maintain message history, decide from the stop reason whether to continue, dispatch by tool name, validate arguments against the schema, fold the tool result back in as a message, and cap the number of turns.
  3. Naming the stop reason explicitly scores well: the loop exits not when 'the model finished talking' but when the turn's stop reason is not a tool-use one. Most candidates blur past this, and it is the switch that drives the whole loop.
  4. Then add the three things a hand-rolled version usually skips but a framework cannot: running a batch of tool calls concurrently, emitting the whole run as an event stream so callers are not staring at a black box, and compaction plus session persistence once the context outgrows the window.
  5. Close on tool errors, which is where production experience shows: a failing tool should raise, and the kernel should turn that into a tool result flagged as an error so the model can fix its arguments and retry. Swallowing the exception and returning 'operation failed' as a normal result makes the model believe the tool succeeded.
  6. Expect the follow-up: how do you stop runaway loops? A max-turn cap is only a backstop; per-run token and wall-clock budgets plus a pre-execution hook that can block a call and hand the reason back to the model are what actually work.

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

  1. 这题看着像背清单，区分度其实在「你有没有自己写过一遍」。只答「循环调用模型直到结束」会被认为读过文档但没写过代码。
  2. 最稳的拆法是把手写版的代码从上往下念一遍，每一行都是内核必须解决的一件事：发模型请求、维护消息历史、判断停止原因决定继不继续、按工具名分派、按 schema 校验参数、把工具结果回填成一条消息、控制最大轮数。这条链路念完，答案自然是完整的。
  3. 点名停止原因这一环最能加分：循环的出口条件不是「模型说完了」，而是这一轮的停止原因是不是「要调工具」。很多人把它含糊过去，而它恰恰是整个循环的开关。
  4. 然后补上手写版通常没做、但框架必须做的三件：并发执行同一批工具调用、把每一步以事件形式播报出去（否则外部完全是黑箱）、以及上下文超限时的压缩与会话持久化。
  5. 最后落到工具报错这一条，它是最能体现工程经验的：工具异常不应该被吞掉，要转成一条带错误标记的工具结果回给模型，让模型自己改参数重试；吞掉异常返回一句「操作失败」，模型会以为工具成功了。
  6. 可以预期的追问：怎么防死循环？答最大轮数只是兜底，更实际的是给单次运行设 token 与耗时预算，并在工具调用前留一个可以拦截的钩子，触发条件时把拦截原因回传给模型让它改道。

  Key points

  • The skeleton: call the model, maintain history, branch on the stop reason, dispatch tools, validate arguments, fold results back in
  • The stop reason is the loop's exit condition — a tool-use reason means one more turn, anything else means done
  • Tool execution details: batch calls can run concurrently, hooks belong before and after, and exceptions become error-flagged tool results the model can react to
  • An event stream is mandatory, otherwise callers see a black box and observability is impossible
  • Safety valves: max turns, token and latency budgets, context compaction, and session persistence for resume

  答题要点

  • 循环骨架：调模型、维护消息历史、按停止原因判断继不继续、分派工具、校验参数、回填工具结果
  • 停止原因是循环的出口条件，工具分支意味着还要再来一轮，其他取值意味着结束
  • 工具执行的工程细节：同一批调用可以并发、执行前后要留钩子、异常要转成带错误标记的工具结果回给模型
  • 对外要有事件流，否则调用方看不到 Agent 在做什么，也没法做可观测性
  • 安全阀：最大轮数、token 与耗时预算、上下文超限时的压缩，以及会话的持久化与恢复
• What are the responsibilities of Pi SDK's three layers, and what does that layering buy you?Pi SDK 的三层架构分别对应什么职责？这样分层解决了什么问题？

  Common in ChinaCommon overseasBasic#framework-design#architecture

  How to reason about it · think before answering

  1. The first half is recall; the second half carries the signal. Reciting three package names without explaining the cut suggests you only skimmed the docs.
  2. State the layers precisely: the bottom is a unified model layer that normalizes each provider's request format, auth and streaming into one interface while tracking tokens and cost; the middle is the agent kernel built on top of it, owning the agent loop, tool execution, state and the event stream; the top is the application layer, owning session storage, extension and resource loading, built-in tools, and the interactive, print, RPC and embedded-SDK run modes. Dependencies point strictly downward.
  3. Then answer what it buys: layering lets you take only half. Want just a unified model layer and your own loop? Stop at the bottom. Want the full loop but none of the terminal UX? Stop in the middle. That test generalizes to any framework and is worth far more than the package names.
  4. Add the practical payoff: when something breaks, first place it in a layer. A stack trace through the model layer points at auth, a wrong model id or a malformed request; one through the kernel points at the loop or tool execution. The two investigations look nothing alike.
  5. Expect the follow-up: how does this map onto the loop you wrote by hand? All three layers were collapsed into one file — the fetch calls were the model layer, the while loop and tool dispatch were the kernel, and the CLI was the application layer. Making that mapping live is more convincing than any recitation.

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

  1. 前半句是记忆题，后半句才有区分度。只背出三个包名而说不出「为什么这么切」，面试官会判断你只是照着文档看了一遍。
  2. 先把三层说准：最底层是统一的模型调用层，负责把各家 provider 的请求格式、鉴权、流式分包收敛成一套接口，还统计 token 与成本；中间是 Agent 内核层，构建在模型层之上，负责 Agent 循环、工具执行、状态管理和事件流；最上层是应用层，负责会话存取、扩展与资源装载、内置工具，以及交互式、打印、进程间调用、嵌入式 SDK 这几种运行模式。依赖方向严格单向向下。
  3. 然后回答「解决了什么」：分层的价值是让你能「只要一半」——只想要统一的模型调用层就停在最底层，想要完整循环但不要终端交互就停在中间层。这条判据可以用来评估任何框架，比复述包名有用得多。
  4. 补一个很实际的收益：排障时先判断问题落在哪一层。报错栈里出现模型层，多半是鉴权、模型 id 或请求格式；出现内核层，那是循环或工具执行；两者的排查方向完全不同。
  5. 可以预期的追问：这套分层跟你手写的版本怎么对应？答手写版把三层揉在了一个文件里——fetch 那几行是模型层，while 循环和工具分派是内核层，命令行交互是应用层。能当场做这个映射，比任何背诵都有说服力。

  Key points

  • Model layer: normalizes provider request formats, auth and streaming, tracks tokens and cost, and only ships tool-calling models
  • Kernel layer: the agent loop, tool execution and result folding, state management and the event stream, built on the model layer
  • Application layer: session storage, extension and resource loading, built-in tools, and the interactive, print, RPC and embedded-SDK run modes
  • Dependencies point one way, so each layer is replaceable and testable on its own and you can adopt only part of the stack
  • For debugging, place the failure in a layer first — model-layer and kernel-layer investigations diverge immediately

  答题要点

  • 模型层：统一各家 provider 的请求格式、鉴权与流式，附带 token 与成本统计，只收录支持工具调用的模型
  • 内核层：Agent 循环、工具执行与结果回填、状态管理、事件流，构建在模型层之上
  • 应用层：会话存取、扩展与资源装载、内置工具，以及交互式、打印、进程间调用、嵌入式 SDK 几种运行模式
  • 依赖单向向下，好处是每层可单独替换、单独测试，也能「只要一半」
  • 排障时先定位问题落在哪一层，模型层和内核层的排查方向完全不同