CommandAGI · commandagi.com/for/one-file

CommandAGI
Open the workbench
Menu
Open the workbenchSign in

One file, not a thousand calls

The agent writes the design.

A part, a board, a world or a dashboard is one .tsx file in the SDK's declarative code. An agent writes the file once; the editors open it and write each edit back into it. No call per extrude, no schema per feature.

Read the SDKOpen the workbench

Two ways to make a part

One write, or a call per feature.

The same part, two ways. Written as code, it is one file that the sandbox runs into its feature graph. Made by calls, each feature is a tool call whose schema the agent must fetch first, and some of what the file says has no call at all.

A part as one file or as many callsOn the left, an agent writes one .3d.tsx file; the code sandbox runs it into the part's feature graph, with its checks and drawings. On the right, the agent fetches each feature kind's schema with describe_tool, then sends one add call per feature and one set call per parameter; the checks, drawings and body data in the file have no call.The agentone designShell.3d.tsxone write · 17,096 bytes35 tool callsafter 7 describe_tool schemasThe feature graphthe same 33 featuresA part as one file or as many callsOn the left, an agent writes one .3d.tsx file; the code sandbox runs it into the part's feature graph, with its checks and drawings. On the right, the agent fetches each feature kind's schema with describe_tool, then sends one add call per feature and one set call per parameter; the checks, drawings and body data in the file have no call.The agentone designShell.3d.tsxone write · 17,096bytes35 tool callsafter 7 describe_toolschemasThe feature graphthe same 33 features

Measured on a real part

17 KB of code or 65 KB of calls.

The shell of the CommandAGI-Cam-001 camera, as it is in the repository. commandagi code eval ran it: 49 nodes, 33 of them features with an add tool. The study built the call each feature needs and asked the platform for each kind's schema.

the file, 214 lines, written once
17,096 bytes
calls to make it by tools: 33 features and 2 parameters, 19,173 bytes
35
the schemas of the 7 feature kinds the calls use
45,736 bytes
the file's size, before any call's answer is counted
3.8×
Bytes an agent sends to make CommandAGI-Cam-001's shell
The numbers
Bytes an agent sends to make CommandAGI-Cam-001's shell
WayBytes
One file17096 B
Calls only19173 B
Calls and schemas64909 B
ProvenanceFile hardware/CommandAGI-Cam-001/cad/Shell.3d.tsxOutput case-studies/one-file/stats.jsonTool commandagi code eval; describe_tool on the hosted MCPRan on This computer (dell-gb10-1) and api.commandagi.comWhen

What a call cannot say

The checks and the drawings have no call.

Four of the file's declarations have no add tool on the platform: the part's design checks, its drawings, its accepted findings and its body data. An agent that works only by calls cannot make this part as it is.

The sizes are bytes, measured; a model's token count depends on its tokenizer and is not measured here. Each call's answer would add more.

Read the SDKHosted MCP

kinds of declaration with no add tool: checks, drawings, accepted, body data
4
nodes in the graph the file runs into
49
write, against 35 round trips
1
ProvenanceFile hardware/CommandAGI-Cam-001/cad/Shell.3d.tsxOutput case-studies/one-file/stats.jsonTool commandagi code eval; describe_toolRan on This computer (dell-gb10-1) and api.commandagi.comWhen

Write the part as code.

Open any .3d.tsx in the workbench: the editor builds it, and each edit you make is written back into the file.

Open the workbenchRead the SDK