Skip to main content
An agent has a name and immutable versions. Each version records the agent’s instructions, model, and tool definitions. Chronicle also records runs: what happened each time the agent was invoked. Use a configured SDK client. The examples share that client and the IDs returned by earlier steps.

Methods

Registering and recording runs need a key with agents:write. Reads use a platform key.

Before you register

Have your agent code and service tools ready. Registration records a version’s configuration; to execute it in Chronicle, configure its run command and package its dependencies. Use billing-agent@1.0.0 consistently in the examples below and the evaluation guide. Inspect the task it will run: moving ENG-2 and posting the handoff requires actual Linear and Slack tool calls.

Register from your agent code

The simplest way is an adapter that captures the configuration straight from your agent object and records its runs automatically.
register-agent.ts
@chroniclelabs/agentforce observes Salesforce Agentforce agents the same way; those can’t run in evaluations.

Register any agent

For frameworks without an adapter, or from a build pipeline, describe the version yourself. This is what the adapters send under the hood.
Python
Registering the same name and version with identical content is a no-op; with different content it’s a 409. Bump the version when the agent changes. Registering a new current version moves the old one to stable.

Run in an evaluation

Registration does not upload code or configure execution. Package the selected agent version and its dependencies, supply its model credentials, and configure a command that starts its entry point inside the evaluation sandbox. Chronicle sets these variables for each trial: For tasks in a world, use the service credentials injected into the trial instead of production credentials. Your HTTP clients must respect HTTP_PROXY, HTTPS_PROXY, and the supplied CA settings (NODE_EXTRA_CA_CERTS, SSL_CERT_FILE, REQUESTS_CA_BUNDLE). Standard output and error are captured as diagnostics. A clean exit means the agent finished; attached scorers determine whether it completed the task. See Run an evaluation to configure the test.

Record runs

Adapters do this for you. From your own code, record each invocation after it finishes:
Python
Up to 100 runs per call. A run_id is write-once: send the same body again to retry, use a new ID for a new run.

Read the registry

Python
Run stats describe observed invocations. Task pass rates come from evaluations.

Chat with an agent

A quick way to confirm Chronicle can run the agent at all. Requires a run command on the agent; see Connect your agent.
Python
The reply includes the messages so far, tool steps, and a trace_id you can open in Timeline. Chat runs the agent without a world; to test it against a task, run an evaluation.