可隨時重新開啟的 Agent 執行記錄。

Switch on session capture and every run through the gateway becomes a trace you can open, export, share and re-ask step by step on another model — and the open-source CLI records the shell, filesystem and MCP calls a gateway never sees.

Once capture is on, every run carries the routing and cost truth: every turn, every model call, and what each one actually cost.
步驟層級的假設情境分析：針對單一對話輪次重新向其他模型提問，並將回答內容、延遲時間與費用並排比較。
將任何執行記錄匯出為 orca-trace v0 封存檔，或透過附有過期時間且可撤銷的分享連結傳遞給他人。

兩個半部。一種追蹤格式。

本地端的 orca record 指令能擷取閘道器所無法取得的資訊：Shell 環境、檔案系統與 MCP 呼叫。閘道器則能擷取本地端永遠觸及不到的資料——每一組金鑰、每位團隊成員、每個 CI 任務——並附上路由決策與實際費用。兩者均寫入相同的 orca-trace 封存格式，無論從哪一端產生的執行記錄，開啟方式都完全一致。

提出那個事後才想到的問題。

Find the turn where it went wrong and re-ask that one step on a different model. The comparison runs through your own gateway on your own keys, so what comes back is what you would actually have shipped — with the token bill next to it.