Before you begin
Before you start, make sure you have:- Agent: an Atlan Trident agent ID for the runtime to report against.
- Claude environment: access to the environment where the Agent runs.
- Access: OAuth access to the Atlan gateway, with permission to read the agent and create its sessions.
Record completed run
1
Run agent
Run the Claude Managed Agent in its configured external environment. Create the Agent record in Atlan Trident if it does not exist yet.
2
Upload session
Upload the final session with
POST /agent/v1/sessions, in the Agent category of the Public API. Send name, workspace_id set to the agent’s workspace, subject_kind set to agent, subject_id set to the agent ID, and session_status set to completed or failed. Record the original execution timestamp in source_created_at, and the run’s stop_reason, usage, and any error.Set external_session_id to the session ID the run emitted on its OpenTelemetry spans. Without it the session’s traces do not appear.Keep credentials out of application source and request URLs.3
Upload transcript
Skip this step unless your harness captures a transcript. Upload
session_message records with POST /agent/v1/sessions/{session_id}/messages. Each needs workspace_id, a sequence_number, a message_role, and a name that no other session message in the workspace uses.An uploaded session’s events are its session_message records, so a session uploaded without messages has none.4
Verify session
Retrieve the session with
GET /agent/v1/sessions/{session_id} and confirm its subject_id, session_status, and source_created_at match the external run. Inspect its event stream and traces through the Agent API reference before you use its output downstream.Limitations
- Atlan Trident does not execute Claude Managed Agent workloads itself. Uploading a record does not cause the agent to run.
- A session cannot be edited or deleted after creation.
- The documentation playground is disabled; run requests from an approved environment.
Troubleshooting
For request and status errors, see Errors and retries. For gateway errors from scripted calls, see MCP Gateway errors.Next steps
- Record session: record runs from other runtimes through the API.