AI
Active Agent · File · Terminal · Workspace

Not a plugin. Not a chatbot.

THE ROBOT
LIVES INSIDE
THE IDE.

HalfBuilder is a local IDE where the agent is bound to your active file, your terminal output, and your workspace law—so it produces actions, not essays.

Boot the Agent Read the Decree →
ContractIf a tab is open, it is THE file.
LawNo writes outside workspace root.
ModeStreaming + Execution Feed.
AI● SYSON
halfbuilder://agent ● live
$boot: higher-court decree loaded
wire: workspace → allowed roots ✓
wire: active file → context pack ✓
wire: console output → context pack ✓
protocol: FILE_CHANGE / OPERATION / RESULT
status: agent is inside the computer
 
Context
file · console · rules
Identity
inside the editor
Deps
none — stands alone
Feed
streaming
01
What HalfBuilder Is

A real agent. In a real machine.

HalfBuilder is built for builders who ship. The agent doesn't "roleplay" productivity—it receives a strict context pack (active file + terminal evidence + workspace rules) and responds with structured actions your IDE can apply safely.

1
Active File
One File.
No Ambiguity.

If a file is open, it is THE file. No "Which file?" No "Upload it." The active tab is the truth.

2
Workspace
Sovereign
Territory.

No write outside root. No Desktop. No escape. The workspace boundary is law.

3
Terminal
Terminal
Is Evidence.

The last output must be visible to the Agent on every request. No guessing what ran.

4
Pipeline
One Truth.
Every Mode.

Streaming, non-streaming, custom provider, AutoDrive — all must carry the same context pack.

02

Because "chat in a browser" isn't an IDE.

Most AI tools are disconnected from your actual build reality. They guess context, forget constraints, and output vague advice. HalfBuilder anchors the agent to the same reality you live in: the file, the errors, the workspace boundary.

03

Early Access: Real foundation, expanding fast.

  • • Account + sign-in (to manage access, updates, and downloads)
  • • Product docs (how it works, safety model, workflows)
  • • Contact + support channel (real replies)
  • • Roadmap visibility (what's next, what's locked)
04

Roadmap

  • Next: Downloads area + build releases + changelog
  • Next: License keys / seats (for Pro/Team)
  • Next: Extensions + templates + project bootstraps
  • Later: Team workspaces + audit logs + policy packs
THE HIGHER COURT — DECREE Six Laws
01
There is only one agent.
Not a chatbot. Not a helper. The AI inside the computer.
02
If a file is open, it is THE file.
No "Which file?" No "Upload it." The active tab is the truth.
03
The workspace is sovereign territory.
No write outside root. No Desktop. No escape.
04
The terminal is evidence.
The last output must be visible to the Agent on every request.
05
One pipeline. One context pack.
Streaming, non-streaming, custom, AutoDrive — all carry the same truth.
06
When the agent acts, it shows the act.
FILE_CHANGE / OPERATION / RESULT. No silent writes.
The Oath
We do not build toys.
We build systems that behave.
We ship what is real.
"Command your build universe."
File-Change
Protocol

Your agent outputs structured actions the IDE can apply directly. Clean, parseable, unambiguous — every time.

Protocol · Required FormatSTRUCTURED OUTPUT
FILE_CHANGE:
path: relative/to/workspace/index.html OPERATION:
edit PATCH:
(diff or full replacement) END_FILE_CHANGE
—
Never absolute paths.
—
Never Desktop.
—
Always open the changed file after apply.
Design Notes

This page treats the computer itself as the character. The robot is not "on the web" — it is physically inside the monitor frame, with circuitry that pulses only when the agent boots.

Motif
Monitor-as-body, core-as-eye, circuits-as-intent.
Feel
A calm command center — dark, powerful, precise.
Rule
No external dependencies. The page stands alone.