Running Tico

Keeping Tico healthy takes a few minutes a week.

Health

Settings → Health shows your computers, model sign-ins, waiting bots, GitHub, backups, and version, with a fix for anything wrong. A red dot on Settings means something needs you. If bots stop answering, look at Models there first.

Backups

Backups are on from the start and copy the database within seconds.

Use a bucket when you can. Restore puts the database, attachments, and Credential key back together.

Restore into an empty data volume

The data volume must be empty; stopping an existing server leaves its data in place.

docker compose stop server
docker compose run --rm --no-deps server restore
docker compose up -d

Restore an existing install

Use --force to replace existing data with the backup. Tico keeps the current database and Credential key aside.

docker compose stop server
docker compose run --rm --no-deps server restore --force
docker compose up -d

See the full restore guide.

Updates

When a new version is out, Tico shows a notice with what changed. Click Update now. If the server doesn’t come back healthy, it rolls back on its own. See Updating.

Model usage and review cost

Open Account menu → Usage to compare bots, runs, models and recorded token use. Subscription API-equivalent estimates describe what those tokens would cost through an API; they are not an extra subscription bill or a measurement of the provider’s plan quota.

• Wake a bot for actionable work: a direct request, a real blocker or a dependency becoming ready. Collect ordinary progress changes into a concise update.
• Keep each task’s checkpoint short and read the source ranges relevant to it. A correctly isolated task session can still fill up with repeated logs and old memory.
• Give reviewers different approaches, reuse valid review evidence and run focused checks for the changed behavior.

Compaction limits active context. It does not cap cumulative usage: many calls below 250k can still use millions of tokens. See the usage guide and reviewer settings.

Contact support

Open ? → Contact support to reach the Tico team. Replies come back into the app, under Your requests. Diagnostics are attached by default: click Preview to see exactly what’s sent. Emails, keys, addresses, and the names of humans and bots are removed, and no task, message, or doc text is included. The Tico team screens incoming tickets for spam and prompt injection.

For questions and ideas, use GitHub Discussions.

Everyday commands