Run SAT locally

Clone and install JavaScript dependenciesCopy Anchor Link

git clone https://github.com/YarlisAISolutions/smart-agent-teams.git
cd smart-agent-teams
npm login                                   # once; needed for @yarlisai/ui
bun install

If bun install fails with a 404 or 403 for @yarlisai/ui, your npm login is missing or lacks access to the package.

Create the API environmentCopy Anchor Link

cd apps/api
uv venv -p 3.12 .venv
uv pip install -p .venv/bin/python -r requirements-production.txt
cd ../..

Start PostgreSQLCopy Anchor Link

With Docker:

docker compose -f docker-compose.db.yml up -d postgres redis

This creates database sat_main on localhost:5432 with user sat_admin; the password is in docker-compose.db.yml. Redis is not required to run the API locally: live events use it only when EVENTS_BACKEND=redis, and without it the health snapshot reports Redis as degraded.

With a local PostgreSQL install, create an empty database and note its connection URL. If port 5432 is taken by another project, run PostgreSQL on another port and use that port in DATABASE_URL.

Start the API on port 8080Copy Anchor Link

The simplest way is the local starter at the repository root. Its defaults match docker-compose.db.yml (database, Redis URL, DEBUG=true so /docs is served, and CORS for port 4200), and any variable you set yourself wins:

apps/api/.venv/bin/python start_api_local.py

Or run uvicorn directly with your own database URL:

cd apps/api
export DATABASE_URL='postgresql://<user>:<password>@localhost:5432/sat_main'
.venv/bin/uvicorn main:app --reload --port 8080

On startup the API runs the Alembic migrations (alembic upgrade head), so the schema is always current. Check that it is up:

curl -s http://localhost:8080/health

API docs are at http://localhost:8080/docs when DEBUG=true. Without JWT_SECRET_KEY, the API signs tokens with a development-only secret; that is fine locally and refused in staging and production.

Seed the demo company (optional)Copy Anchor Link

export DATABASE_URL='postgresql://<user>:<password>@localhost:5432/sat_main'
apps/api/.venv/bin/python apps/api/scripts/seed_demo.py

The seed signs in as (or registers) demo@example.com with password DemoPassword123! and creates NoteFlow (prefix NF, budget $1,500 a month):

• Agents Ada (CEO), Linus (CTO), Maya (CMO), Grace (Senior Engineer), Ken (Engineer), Margaret (QA Lead) and Toni (Content Writer), plus Iris (Product Designer) waiting in Approvals as a hire request.
• Three goals, two projects ("Web app" and "Marketing site"), 20 tasks, two routines, and two weeks of finished runs with costs.
• Three runs left running (for Grace, Ken and Maya) so the dashboard has live activity.

Use --email, --password, --name and --company to change the defaults. Each time you run the seed it creates another company, so run it once.

Start the web app on port 4200Copy Anchor Link

In another terminal, from the repository root:

bun run dev

Vite serves the app on http://localhost:4200 and proxies /api and /health to http://localhost:8080. To proxy elsewhere, run SAT_API_URL=http://host:port bun run --cwd apps/web dev instead. Sign in as demo@example.com / DemoPassword123!, or select Sign up to start empty.

Use the CLI from sourceCopy Anchor Link

The local profile points at http://localhost:8080 and is the default.

bun run sat -- login --email demo@example.com      # prompts for the password
bun run sat -- company use NoteFlow
bun run sat -- dashboard
bun run sat -- doctor

sat doctor checks the profile, API health, your sign-in, the default company, the live event stream, the agent CLIs (claude, codex) and git, and exits with code 1 if any check fails. To get a sat binary instead of bun run sat --, run bun run --cwd apps/cli build and put apps/cli/dist on your PATH.