Skip to main content
Start with the data that was actually stored. Connect a conversation record to its agent configuration, inspect the available transcript and media, and describe an observed issue before proposing a change.

​
Review process

1

Find the relevant record

Use the conversation list’s supported filters and pagination. Check the workspace and identifier before inspecting private data.
2

Trace the configuration

Keep the agent, branch, and version identifiers with the record. Compare the stored configuration with the behavior you expected.
3

Inspect available evidence

Read details and summary coverage. Retrieve audio only when it exists and you have access. Treat stored analysis as existing data rather than a newly computed result.
4

Propose a focused change

Describe the observed behavior, intended outcome, and relevant prompt or resource change. Review the complete configuration diff before publication.

Inspect conversations

Read transcripts, summaries, metadata, and available recordings.

Review versions

Connect an issue to an identifiable configuration snapshot.

Improve instructions

Revise one clear task or boundary at a time.

​
Current limits

Message search, topic aggregation, and generated analysis are not complete implementations in the documented source. Automated response-test execution is also gated. Use direct record reads and manual review for the workflow above; do not infer a measured improvement from configuration acceptance.

​
Frequently asked questions

The current search implementations are placeholders. Use supported list filters and follow the returned pagination cursor.
No. A saved test definition and a completed invocation are different. Automated execution requires its own released path and recorded results.