Talon logo Talon

Core loop

From the repository root:

docker compose up --build -d

This starts the local compose stack and brings up:

  • the gateway
  • the worker
  • Sightline UI
  • Postgres
  • the Pub/Sub emulator
  • a shared talon-objects volume for local object storage
  • the default template bootstrap

SQLite development

The default local stack still uses Postgres.

If you want to run Talon directly on a single machine without Postgres, configure:

  • control_plane.database.driver: sqlite
  • control_plane.database.data_dir: <local directory>
  • control_plane.message_broker.driver: local_socket
  • control_plane.object_store.driver: local
  • TALON_SCHEDULER_DRIVER=local_sqlite

Keep the SQLite database on a local filesystem and run the gateway and worker on the same host.

Useful endpoints

  • Gateway edge: http://localhost:50051
  • Sightline UI: http://localhost:3000

Common tasks

  • Inspect the gateway service reference when adding or consuming API surface
  • Use Sightline to verify sessions, schedules, namespaces, and tool activity
  • Use the CLI for admin flows that are easier from the terminal than the UI

Useful runtime ports

  • 3000: Sightline UI
  • 50051: gateway (native gRPC and gRPC-Web)

Docs workflow

  • Hand-written docs live in docs/.
  • Generated reference pages live in docs/reference/generated/.
  • If you change the gateway or schema protos, regenerate the reference pages with pnpm --filter @impalasys/talon-docs generate:reference.
  • Use the docs markdown itself as the source of truth for this open-source repository.