Docs
⌘ K
Get started Deploy to AGNT5 Cloud

Deploy to AGNT5 Cloud

Promote the workflow you ran in your dev session to a managed environment and trigger it remotely.

You will take the project from Your first workflow and run it on a managed environment. Same code, same workflow — only the session host changes from your laptop to AGNT5’s managed runtime.

Time: about five minutes.

You’ll learn:

  • Push your API key as a project-scoped secret
  • Build and ship the project to a managed environment
  • Trigger the deployed workflow and view its trace

Prerequisites:

Step 1: Push the OpenAI key as a secret

Local .env files do not travel to the cloud. From inside the project directory:

agnt5 secrets set --name OPENAI_API_KEY --type api_key

The CLI prompts for the value and stores it scoped to this project. Confirm:

agnt5 secrets list

Step 2: Deploy

agnt5 deploy

agnt5 deploy defaults to the preview environment. The command:

  1. Builds your project image with a managed BuildKit instance.
  2. Pushes the image to the registry.
  3. Creates a deployment record.
  4. Provisions workers and waits until they report ready.

Output streams progress in real time. When it finishes you get a deployment ID.

✓ Build complete
✓ Image pushed
✓ Deployment created: d8f3a2b1-1234-5678-9abc-def012345678
✓ Workers ready (1/1)

Step 3: Verify the deployment

agnt5 deploy status <deployment-id>

The output names the environment, the replica count, and the worker health. Use --watch to refresh every two seconds.

You can also list every deployment in the project:

agnt5 deployments

Step 4: Trigger the workflow remotely

agnt5 run research --env preview --input '{"url": "https://en.wikipedia.org/wiki/Durable_function"}'

Without --env preview the CLI routes to your active dev session; with it the request hits the deployed environment.

Step 5: Inspect the deployed run

agnt5 inspect runs ls --env preview
agnt5 inspect trace -r <run-id>

Same trace shape as your dev run, now sourced from the deployed environment.

What you built

The same workflow you ran in your dev session is now running under managed workers. Updates flow with another agnt5 deploy. Promote preview to staging or production by passing --env.

What you did not write or configure:

  • Container build pipeline
  • Image registry credentials
  • Worker process supervision and health checks
  • Secret distribution

Next steps