Make a checked application live

Choose the target service#

Use the console address and agent-service endpoint supplied for your environment. The product server supports the console’s durable work and execution pool. The CLI’s local service is useful for development but does not support work lists or the catalog Dashboard.

The development walkthrough’s wrapper defaults to its product server. A standalone CLI may instead start a local service. Use an explicit target when deploying from the CLI so the destination is clear. Set HELIXOR_AGENT_ADMIN_TOKEN to the owner token obtained through your environment’s approved sign-in process. Keep its value out of shared commands and documentation.

Deploy from the console or CLI#

In Build, use Deploy application, resolve check failures, and confirm the reviewed changes. For CLI deployment, set HELIXOR_AGENT_URL to your intended service URL, then run:

helixor agent check customer-care
helixor agent deploy customer-care --to "$HELIXOR_AGENT_URL"

Confirm the reported application version and agent endpoints. Deployment is atomic for the application. An unchanged agent can retain its previous version while the application receives a new deployment version.

Open the application in the console, then the agent’s Talk to vN tab. A successful draft test does not prove that the live effect or approval path works; test those separately with practice data.

Connect a caller#

Use the agent’s Endpoint & keys tab to inspect its endpoint and manage access keys. The messages endpoint has the form POST /v1/agents/{name}/messages. A full key is shown when created; later listings show its prefix.

CLI deployments save created keys under the agent’s ignored .helixor/keys.json. Keep keys out of source control and shared transcripts. Revoking a key prevents subsequent requests using it; callers need a replacement key.

Update an existing application#

Open it in the editor, or pull its current live bundle before editing with the CLI:

helixor agent pull customer-care --to "$HELIXOR_AGENT_URL"
# Edit the pulled application, then check it.
helixor agent check customer-care
helixor agent deploy customer-care --to "$HELIXOR_AGENT_URL"

Use a clean destination when pulling. If you are editing an online draft, follow the draft round trip instead. A live deployment made after the draft began causes DRAFT_BASE_STALE; reconcile the draft with the current live application.

Return to an earlier version#

Review the application’s deployment history and choose the intended version. In the CLI, this example selects application version 1:

helixor agent history customer-care --to "$HELIXOR_AGENT_URL"
helixor agent rollback customer-care 1 --application --to "$HELIXOR_AGENT_URL"

Rollback creates a new application deployment record pointing to the earlier agents. It does not erase deployment history or undo tool effects already performed.

Retire an application#

An owner can archive an application to stop its agents, suspend their admissions, and discard its open draft. It leaves usage history in place. Archive is broader than discarding a draft; review the application before confirming. Redeployment can restore an archived application.