LOCAL PILOT / MACOS

Install Tico

These steps set up one company’s server, browser interface, and agent runner on a Mac. The runner needs a signed-in model CLI to execute bots.

Before you start

• macOS 13 or later, Python 3.12, and Git.
• A dedicated Mac or dedicated macOS account for this company. Agents run with that account’s file access.
• At least one supported model CLI installed and signed in. The current default is codex; claude, gemini, and grok are also supported.
• An approved, curated Tico source package. Do not use another company’s database, workspace, registry, or credentials.

1. Prepare the package

Open a terminal in the root of the reviewed package. Create the Python environment used by the server and runner:

cd /path/to/reviewed-tico-package
python3.12 -m venv runtime/runner-venv
runtime/runner-venv/bin/python -m pip install -r backend/requirements.txt

2. Create one local environment

Substitute your company and owner details. This command creates a company-specific environment under ~/.config/tico/environments/pilot/, including a local database and owner sign-in token.

scripts/tico env create pilot --company 'Pilot Company' \
  --app 'Pilot Hub' --assistant 'Pilot Assistant' --local \
  --owner-email owner@example.com --owner-name 'Pilot Owner'
scripts/tico -e pilot server install
scripts/tico -e pilot server status

The command prints the local URL. Keep the environment directory and owner token private. A local token server must stay on loopback; do not expose it through a public tunnel.

3. Finish setup in the browser

scripts/tico -e pilot open

open trades the local owner token for a browser session and starts the first-run wizard. Set the company details, answer the operating questions, and choose the bots you want. The assistant and BotOps are required. Finishing setup creates planned bots, not fully working ones.

4. Add this computer as a runner

In the setup wizard, choose Add computer and download its short-lived setup file. Run the commands shown there from the same checkout. The shape is:

scripts/tico -e pilot enroll --code-file "$HOME/Downloads/<setup-file>.json" --label 'Pilot Mac'
scripts/tico -e pilot profile add default
scripts/tico -e pilot profile login default codex
scripts/tico -e pilot install bot

Use the model provider you actually have; codex is only the example. The setup file expires after 15 minutes. Do not commit or share it.

5. Activate and verify

The runner materializes the assistant and BotOps repositories. Review their setup state in the browser, then activate them. BotOps can prepare the remaining selected bots. Check readiness and file one synthetic task addressed to an active bot:

scripts/tico -e pilot doctor
scripts/tico -e pilot status
scripts/tico -e pilot logs bot -f

A healthy server alone does not prove that an agent can run. Confirm that the synthetic task completes and its reply appears in the same task conversation. Restart the server and confirm the task remains. For a real pilot, also verify a backup and restore.

Other setups

The server can be self-hosted with a persistent SQLite volume, blob storage, and an identity-aware proxy. Per-company hosted provisioning and a container image are not shipped yet. A custom UI can use the same /api/v2 contract; see your own frontend.

Updates

For a local pilot, update only from a reviewed company release after an idle window and protected backup. The runner may fast-forward a clean checkout from its upstream, but scripts/tico -e pilot update does not update the local API and dependencies as one unit. Unattended external-company updates are not ready; leave self-update disabled unless the runner’s upstream is that company’s approved release channel. See the update procedure.