Skip to main content

​
Prerequisites

  • Node.js 20+
  • Python 3.12+ (a 3.14 venv works)
  • gcloud CLI with the Firestore and Pub/Sub emulators (use a currently supported JRE)
  • ffmpeg and ffprobe on PATH
  • yt-dlp on PATH (for YouTube ingestion)

​
Choose a run mode

Local inspection and authenticated execution are different claims: Fixtures are never submission evidence for a provider invocation or deployment. Authenticated execution can incur provider charges; inspect pricing and quota before enabling it.

​
Start the local services

This single script starts everything: The script sources .env.local if present. The web and worker must share a non-empty internal token:

​
Run an authenticated cognitive job

Before this path can succeed, configure the values documented in Configuration, including Google Identity Platform, application credentials, AGENT_SERVICE_URL, the shared INTERNAL_API_TOKEN, AGENT_ENGINE_RESOURCE, and the exact regional model and memory resources used by the worker. There is no in-process ADK fallback. Open http://localhost:3000 and send the console:
Watch the job progress through collect_sources → extract_sources → understand → strategize and stop for digest-bound strategy approval. A failed source pauses for explicit retry, removal, replacement, or reconnection. After approval, Temi plans and the production team drafts before the separate effect-approval boundary. In chat, an approval phrase opens the same deterministic confirmation; model-parsed text cannot authorize strategy or an effect by itself. After approval, only configured actions can execute. An export can be verified by digest; X requires authorized credentials and is verified by a fresh provider read. A failed or unavailable integration stays visible as an unresolved failure rather than becoming simulated success.

​
Run checks

Next: read Development to work fully offline, or jump to Configuration for the full environment variable reference.
Last modified on August 28, 2026