You usually don’t rewrite the business service
With an API document, the assistant calls systems you already run. Steps show in the web console; writes can wait for approve or reject.
-
API docs become callable abilities
Import common API documents and the assistant invokes those operations. Incomplete docs can use a small companion service or a callback to your URL.
-
Creates and status changes can wait
Sensitive writes pause on a console card until a teammate approves or rejects, with a trail.
-
Console, inbox, and messaging share one path
Approvals, memory, and outbound replies are shared. Personal WeChat ships; Feishu and DingTalk examples are included.
-
Downstream login
Sign in in a browser; passwords never hit the model. Export wired abilities to clients like Cursor; when login expires, open the returned link.
Works on phone
Two paths, not substitutes: remote the full console, or embed trimmed orchestration in your own app.
| Remote console | Open reachable /ui/ in a browser, or wrap it with the Capacitor shell in the repo. |
|---|---|
| Your UI + on-device SDK | Go-built mobileagent (AAR / XCFramework); you draw the Kotlin / Swift interface. |
Many systems and long chats
Narrow what this turn needs, group domains, compare API re-imports, and inspect what a turn used.
-
Judge first, then the main model
With Matching & decisions and Smart speed-up, send a shorter ability list first; on failure use the full list.
-
Group by business domain
Group finance, commerce, and similar systems. Start a sub-task when approvals must not collide.
-
Compare API changes; open a turn’s binding
After re-import, see what changed. Beside each chat turn, open which model and abilities were used.
-
Summaries, schedules, eval
Long threads get summaries; set daily or weekly instructions; admins can collect failed chats for review.
Get started
Download a release for your platform, set secrets, and start. No Go toolchain required.
cp .env.example .env
# set model key and settings key
./baize serve
# open http://127.0.0.1:8080/ui