SDKs
Choose conversation or MCP capture, set up a source SDK and inspect the recorded data.
Watch the workflow: Read a recorded session and tool trace · Authored dummy data
Read authored agent inputs and outputs, open the recorded trace and inspect one tool run. Role, completion and customer outcome remain unknown. No evidence or feedback is saved.
This video shows the matching app inspection workflow with authored dummy data. It does not execute an SDK example or prove successful delivery from your application. Read the matching command examples separately.
Read the walkthrough transcript
- 00:00 — Read recorded agent inputs and outputs in Tensile. This is an authored demo session.
- 00:05 — Open Trace to see the recorded runs. The session outcome remains unknown.
- 00:11 — Read one tool run's input and output. Saving evidence is a separate action.
The SDK registry release is pending. These instructions require a trusted source checkout supplied by your team. They do not install a package from the public registry. Without SDK source access, use the capture API instead.
Choose a capture surface
Use conversation capture when your application controls each agent turn. Use the MCP wrapper when tools run through a supported MCP server. Both write sessions and events to Tensile. The wrapper captures tool invocations; it does not capture resource reads or prompt calls.
Source setup
For Python:
python3 -m venv .venv
source .venv/bin/activate
python -m pip install ./sdks/pythonRun these commands from the source checkout with Python 3.12 or later. For an application in a different virtual environment, install the SDK folder there.
For TypeScript:
pnpm install --frozen-lockfile
pnpm --filter @withtensile/sdk buildRun these commands from the source checkout with Node.js 22 or later. In the consuming application, install the built SDK folder:
npm install /absolute/path/to/source/sdks/typescriptReplace the path with the trusted checkout on your machine. The import name is @withtensile/sdk.
Configure capture
Create a scoped API key in Settings. Set TENSILE_API_KEY in the application environment. The default endpoint is https://api.withtensile.com. Set TENSILE_ENDPOINT to change it, including for an isolated local test. Never put a real key in source code or a recording.
Set TENSILE_ENV=staging, or pass the environment explicitly. The explicit setting wins. Without a stage tag, the app cannot treat the record as production traffic.
Read a recorded result
Open User Stories to inspect a captured conversation. Use its trace view to read recorded events. Or open Raw Logs, select the matching stage and inspect the input and output of one event. Missing records are not successful delivery. A tool success flag does not prove a customer outcome.