Design the Agent-Computer Interface (ACI)
Agent Architecture
90-120 minutes0/5 steps0%
Step 1 of 5
Audit your current tool surface
You cannot design an interface you have not honestly measured.
First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.
Prompt Capsule
Audit my agent's current tools against ACI principles. For each tool record: typical output size in tokens, whether output is bounded, whether errors state a cause and suggested next action, whether misuse is guarded (e.g. editing a file never read), and 2-3 transcript examples where the tool confused the model. Score each tool 1-5 on model-friendliness. Research context: SWE-agent found that command simplicity, output windowing, and informative feedback measurably raise task success; raw shells underperform purpose-built commands. Deliver the audit as a table with a fix priority order.
Paste into EmergentFull Build: complete implementation prompt with explicit requirements
Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.
Actual change check
Expected after this step
A scored tool audit with prioritized fixes.
Should NOT happen
- An existing feature broke
- A button only logs to console
- Data disappears after refresh
- Errors fail silently with no visible state
This is what should exist before you continue. If reality does not match, do not move on.
Track what changed, failed, or needs follow-up. Notes export with the flow.
Pass the Verify Gate to complete this step