Skip to main content
The Cloud Run service is agent-os, the Cloud SQL instance is agentos-db, and the Artifact Registry repo is agentos. The scripts target the current gcloud project and us-central1; override them with GCP_PROJECT_ID and GCP_REGION.

​
Manage

TaskCommand
Deploy code changes./scripts/gcp/redeploy.sh
Sync env variables./scripts/gcp/env-sync.sh (defaults to .env.production; pass .env to sync that instead)
Tail logsgcloud run services logs read agent-os --region us-central1 --limit 100
Resize the serviceEdit the --cpu/--memory flags in scripts/gcp/up.sh and rerun it
Tear down./scripts/gcp/down.sh (add --yes to skip the confirmation)

​
Production auth

Token-Based Authorization is on by default. Without a JWT_VERIFICATION_KEY or JWT_JWKS_FILE, the app refuses to serve traffic in production. The platform’s job is to keep your data private, so the safe default is refuse to start. Token-Based Auth gives you three things:
  1. No public access. The server rejects requests without a valid token.
  2. Per-request identity. Middleware parses the token and extracts the user_id, session_id, and custom claims. Each request is tied to a user and session, giving you auditability and traceability.
  3. Granular permissions. User tokens can run an agent and view their own sessions. Admin tokens read everyone’s sessions and test any agent.
To opt out (not recommended), set authorization=False in app/main.py and redeploy. Use this only inside a private VPC behind another auth layer. Without it, anyone who guesses your Cloud Run URL can access your platform.

​
Customize

Ask your coding agent to run /create-new-agent, or do it by hand. Create agents/my_agent.py:
from agno.agent import Agent

from app.settings import default_model
from db import get_postgres_db

INSTRUCTIONS = """\
What the agent does, which tools it uses, the rules to follow when answering.
"""

my_agent = Agent(
    id="my-agent",
    name="My Agent",
    model=default_model(),
    db=get_postgres_db(),
    instructions=INSTRUCTIONS,
    enable_agentic_memory=True,
    add_datetime_to_context=True,
    add_history_to_context=True,
    num_history_runs=5,
)
Register it in app/main.py:
from agents.my_agent import my_agent

agent_os = AgentOS(
    ...
    agents=[agent_builder, platform_manager, web_search, my_agent],
)
Local containers hot-reload on save. For production, run ./scripts/gcp/redeploy.sh.
app/settings.py defines default_model(), used by every agent. Change it in one place:
from agno.models.anthropic import Claude

def default_model():
    return Claude(id="claude-sonnet-5")
Add anthropic to pyproject.toml, set the provider key in your env, and regenerate pins:
./scripts/generate_requirements.sh
Rebuild locally with docker compose up -d --build. For production:
./scripts/gcp/env-sync.sh
./scripts/gcp/redeploy.sh
Agno ships 100+ toolkits. See Toolkits.
from agno.tools.slack import SlackTools

my_agent = Agent(
    ...
    tools=[SlackTools()],
)
  1. Edit pyproject.toml.
  2. Regenerate pins: ./scripts/generate_requirements.sh (add upgrade to refresh every pin).
  3. Rebuild locally with docker compose up -d --build, or redeploy with ./scripts/gcp/redeploy.sh.
Set both variables in your env file:
SLACK_BOT_TOKEN=xoxb-...
SLACK_SIGNING_SECRET=...
Sync with ./scripts/gcp/env-sync.sh. The interface activates automatically and routes messages to Agent Builder; change the agent= argument in app/main.py to point at another agent. See Slack setup.
The deployment check runs daily by default (ENABLE_DEPLOY_CHECK=True); it is deterministic and free. Scheduled evals are off by default (ENABLE_SCHEDULED_EVALS=False) because they use model calls. Both workflows stay runnable on demand regardless.

​
Format, validate, and run evals

The format, validate, and eval scripts run on the host and need a venv. Set it up once: 
./scripts/venv_setup.sh
source .venv/bin/activate
TaskCommand
Format./scripts/format.sh
Lint and type-check./scripts/validate.sh
Run smoke evalspython -m evals --tag smoke
./scripts/mcp_check.sh runs inside the container, so it needs no venv.

​
Environment variables

VariableRequiredDefaultDescription
OPENAI_API_KEYYes-Models and embeddings.
RUNTIME_ENVNoprddev disables JWT. Compose sets it for local. Never put it in an env file that syncs to Cloud Run, or production deploys unauthenticated.
JWT_VERIFICATION_KEYProduction-Public key from os.agno.com. Quote the value so the multi-line PEM parses as one variable.
JWT_JWKS_FILEProduction-Path to a JWKS file. Alternative to JWT_VERIFICATION_KEY.
MCP_CONNECT_SECRETNogenerated by up.shOAuth consent secret (16+ chars) for connecting claude.ai and ChatGPT to /mcp. up.sh generates one on deploy and writes it to .env.production.
AGENTOS_MCP_SIGNING_KEYNogeneratedOptional high-entropy signing-key material (32+ chars) for OAuth tokens. Unset, a strong key is generated and persisted in the database. Rotating it invalidates outstanding tokens.
AGENTOS_URLNohttp://127.0.0.1:8000Scheduler base URL. up.sh sets it to your Cloud Run URL. Scheduled jobs never fire if it stays at the default in production. Also the public origin OAuth metadata derives from when MCP_CONNECT_SECRET is set.
ENABLE_DEPLOY_CHECKNoTrueDaily deployment-check cron.
ENABLE_SCHEDULED_EVALSNoFalseDaily run-evals cron. Uses model calls.
EVALS_TAGNosmokeEval tag the run-evals workflow runs.
EVALS_CASE_TIMEOUT_SECONDSNo90Per-case timeout for run-evals runs.
EVALS_SUITE_TIMEOUT_SECONDSNo900Whole-suite timeout for run-evals runs.
PARALLEL_API_KEYNo-WebSearch uses the Parallel SDK when set, keyless MCP otherwise.
SLACK_BOT_TOKENNo-Set with the signing secret to enable Slack.
SLACK_SIGNING_SECRETNo-Set with the bot token to enable Slack.
GCP_PROJECT_ID / GCP_REGIONNocurrent project, us-central1Project and region the scripts/gcp/ scripts target. up.sh records GCP_REGION in your env file so down.sh finds the right region.
DB_HOST / DB_PORT / DB_USER / DB_PASS / DB_DATABASENomatches composePostgres connection.
DB_DRIVERNopostgresql+psycopgSQLAlchemy driver.
AGNO_DEBUGNoFalseVerbose Agno logs. Compose sets it for dev.
WAIT_FOR_DBNoFalseIf True, the entrypoint blocks on the database before starting. Compose sets it.

​
Troubleshooting

Install the Google Cloud SDK, then run gcloud auth login and gcloud config set project <id>.
Expected. The script deploys first because Cloud Run only reveals the URL once the service exists, then pauses so you can mint the key against it. Mint the key at os.agno.com: connect your OS (Connect OS → Live, enter your Cloud Run URL), then turn on Token-Based Authorization (JWT) under Settings → OS & Security and paste the full PEM. To do it later, skip the prompt, add JWT_VERIFICATION_KEY or JWT_JWKS_FILE to .env.production, and run ./scripts/gcp/env-sync.sh.
JWT auth is on whenever RUNTIME_ENV is not dev. Set JWT_VERIFICATION_KEY or JWT_JWKS_FILE and sync. To opt out inside a private VPC behind another auth layer, set authorization=False in app/main.py.
Your organization likely enforces Domain Restricted Sharing (constraints/iam.allowedPolicyMemberDomains), which silently rejects the allUsers binding that --allow-unauthenticated needs. The deploy still succeeds; the service just ships private. up.sh prints a warning when it detects this. Grant roles/run.invoker to specific principals, or ask an org admin for an allUsers exception.
Check that billing is enabled on the project. up.sh warns when it can’t confirm billing; Cloud SQL and Cloud Run creation both fail without it.
AGENTOS_URL is still the localhost default. up.sh sets it to your Cloud Run URL automatically; for a custom domain or tunnel, set it by hand and run ./scripts/gcp/env-sync.sh.
down.sh is targeting a different region than the one you deployed to. up.sh records GCP_REGION in your env file and down.sh reads it from there; if the file is gone, rerun with GCP_REGION=<region> ./scripts/gcp/down.sh. A wrong-region teardown looks clean while the real resources keep billing.