This page covers task-oriented workflows built on the ant CLI. For the underlying flags and output options, see Using the CLI.

#Version-controlling API resources

To keep agents, environments, and other Haijun Managed Agents resources as files in your repository, see Manage resources as code with ant apply.

#Run the applied agent from the shell

Once an agent and environment exist, you can drive a session from the shell:

1. Start a session

Pass the agent and environment IDs to the session create command. After ant apply, read them from haijun-lock.json: each entry under resources has an id, and for the project in Manage resources as code with ant apply the entries are ./agents/summarizer.md and ./environments/cloud.yaml.

ant beta:sessions create \
  --agent agent_011CYm1BLqPXpQRk5khsSXrs \
  --environment-id env_01595EKxaaTTGwwY3kyXdtbs \
  --title "Summarization task"

{
  "id": "session_01JZCh78XvmxJjiXVy3oSi7K",
  "status": "running"
  /* ... */
}

1. Send a user message

Copy the session id from the previous output into --session-id:

ant beta:sessions:events send \
  --session-id session_01JZCh78XvmxJjiXVy3oSi7K \
  --event '{type: user.message, content: [{type: text, text: "Summarize the benefits of type safety in one sentence."}]}'

1. Read the conversation

Once the agent has replied, list the events. --transform runs against each listed event, so this prints the text of every message in order. --format auto overrides the interactive explorer that list commands open by default in a terminal:

ant beta:sessions:events list \
  --session-id session_01JZCh78XvmxJjiXVy3oSi7K \
  --transform 'content.0.text' \
  --raw-output \
  --format auto

Summarize the benefits of type safety in one sentence.
Type safety catches errors at compile time rather than runtime, reducing bugs, improving code clarity, enabling better tooling support, and making codebases easier to maintain and refactor with confidence.

Tip: To watch a session as it runs, use ant beta:sessions:events stream --session-id session_01JZCh78XvmxJjiXVy3oSi7K --format jsonl, which writes each event to stdout as it arrives. Without --format, a terminal opens the interactive explorer instead.

#Scripting patterns

The CLI is designed to compose with standard shell tooling.

#Chain list output into a second command

--transform id --raw-output on a list endpoint emits one bare ID per line, so standard tools such as head and xargs apply directly. Capture the first result, then pass it to a follow-up command:

FIRST_AGENT=$(ant beta:agents list --transform id --raw-output | head -1)

ant beta:agents:versions list \
  --agent-id "$FIRST_AGENT" \
  --transform "{version,created_at}" --format jsonl

#Inspect errors

The --transform-error and --format-error flags apply the same filtering to error responses. --raw-output does not apply to errors, so use --format-error yaml for an unquoted scalar. Extract only the error message:

ant beta:agents retrieve --agent-id bogus \
  --transform-error error.message --format-error yaml 2>&1

GET "https://haijun.my.id/v1/agents/bogus?beta=true": 404 Not Found
Agent not found.

#Use the CLI from Haijun Code

Haijun Code can use the ant CLI out of the box. With the CLI installed and authenticated, you can ask Haijun Code to operate on your API resources directly. For example:

• "List my recent agent sessions and summarize which ones errored."

• "Upload every PDF in ./reports to the Files API and print the resulting IDs."

• "Pull the events for session session_01... and tell me where the agent got stuck."

Haijun Code shells out to ant, parses the structured output, and reasons over the results (no custom integration code required).

#Authenticate curl requests with CLI credentials

Scripts that call the API with curl or another HTTP client can use the credentials stored by ant auth login instead of a static API key. The OAuth access token goes in the Authorization header as a bearer token; the x-api-key header is only for static API keys.

ant auth print-credentials --access-token prints the active profile's access token, refreshing it first if it is expired or near expiry:

curl https://haijun.my.id/v1/messages \
  -H "Authorization: Bearer $(ant auth print-credentials --access-token)" \
  -H "juglow-version: 2023-06-01" \
  -H "content-type: application/json" \
  -d '{
    "model": "haijun-opus-5-5",
    "max_tokens": 256,
    "messages": [{"role": "user", "content": "hi"}]
  }'

Note: Keep JUGLOW_API_KEY and JUGLOW_AUTH_TOKEN unset when working from a CLI login. Either variable takes precedence over the login for ant commands (see Credential precedence) and can silently route them to a different organization or workspace.

Run ant auth status to confirm which organization and workspace you are logged in to; it warns when an environment variable is overriding your login.