01
Install
Obtain Xihe and its dependencies.
Bootstrap the foundation every agent stands on.
Get started
Begin in the realm
No install walls, no config archaeology — just the essential path from nothing to a working, crafted agent.
From zero to your first agent
Five steps, no fluff
02
Init
Scaffold a project skeleton.
Standardise structure so every Wright starts from the same solid ground.
03
Choose a Wright
Select or customise an archetype.
Different tasks demand different dispositions. Pick the one that fits.
04
Run
Execute your first orchestration.
Watch DAG leaves deploy and graft in real time.
05
Observe
Examine the memory graph and drift status.
Understanding prevents accidents. The system shows you its internal state.
Quickstart
Four commands to a working fleet
Bun-native. No platform lock-in. Bring your own models and your own taste.
01Clone the realm
$
git clone https://github.com/AbyssCN/xihe copy 02Install with Bun
$
bun install copy 03Point it at your models
$
cp .env.example .env # set keys copy 04Wake the first Wright
$
bun run dev copy 
The working loop
How you actually build with Wright
Not a toy demo — the real loop a developer runs every day. Six moves from intent to a verified build.
01
Enter plan mode
Start every new feature in the read-only plan cockpit.
It reads and reasons but cannot write, so you shape the work before a single token is spent on code — and contradictions surface while they are still cheap to fix.
02
Pick your model
Point the conductor at a SOTA model for the sharpest plan.
The best plans come from a frontier model, but any capable one works — roles are decoupled from models, so this is a dial, never a lock-in.
03
Brief it richly
Describe what you want in detail, then hand it the raw material: articles, context, even the video that convinced you.
The more grounding Wright has to sift, the better it filters. Rich context is the single biggest lever on plan quality.
04
Shape the framework together
Chat, push back, refine. Keep going until the architecture is settled and you both agree on its shape.
The plan is a negotiation, not a handoff. Disagreement here is far cheaper than disagreement in code.
05
Lock the SDD + TDD contract
Freeze the agreed design as a contract: types, validation, a state machine, acceptance.
Now correctness has a definition. Everything downstream is measured against it; passing it is the floor, not the ceiling.
06
Hand off to the conductor
Give the contract to the conductor. It decomposes the SDD into a DAG and dispatches leaf agents to build each piece.
You stop typing and start reviewing. The conductor drives execution and gates every leaf against the contract you locked.