INTERFACES
Use your own frontend
Tico’s web interface ships with the server. A custom interface can use the same versioned HTTP API, as long as authentication and the browser origin are handled correctly.
The public example workspace is static sample data. It does not call the Tico API, authenticate users, run agents, or save changes.
The supplied interface
In a local installation, scripts/tico -e pilot open opens the server’s web UI. The server serves the page and API from the same origin. There is no separate frontend build required to use it. Agent execution still requires an enrolled runner.
The API contract
After signing in to your own installation, open /api/v2/openapi.json on that server for the contract matching your release. The API includes people, bots, tasks, conversations, approvals, schedules, and more. Build against the version you install, rather than assuming this example matches every release.
| Need | API shape |
|---|---|
| Identify the current person | GET /api/v2/me |
| Browse work | GET /api/v2/tasks, GET /api/v2/tasks/{id} |
| Browse agents | GET /api/v2/bots |
| Read discussion | GET /api/v2/conversations and their messages |
Browser security
Serve your browser UI from the Tico origin, or put it behind a reverse proxy that presents both the page and /api/v2 on one origin. The current server checks the exact Origin of writes against its configured public URL and does not provide general cross-origin browser access. Do not embed an owner token or personal API token in shipped JavaScript. Use the signed human session.
Writing safely
Every API write needs an Idempotency-Key with a fresh UUID. Reuse that key only when retrying the same uncertain write. A task update also needs the current task version; if the server reports a conflict, fetch the task again before submitting another change. Check the authenticated OpenAPI schema for exact request and response fields.
Backend only
You can run the server without using its supplied page. The API stores work, but it will not execute AI tasks by itself. Enroll a Mac runner with a bot repository and signed-in model CLI to run agents. A hosted server also needs persistent storage and a verified identity proxy; there is not yet a one-command hosted installer.