Work from your terminal
Status: Upcoming — not yet available.
Section: DOC-DX-local-tooling#overview.
Debug a chat integration without rebuilding your application after every request. Start a terminal session, submit a controlled conversation, inspect its result and receive its events in your local handler.
Availability: The customer CLI and local event-forwarding service are not released yet, so installation and command names are not supplied here. Use the HTTP development setup and Postman collection for those available workflows today. This page describes the CLI experience.
Start a development session
Status: Upcoming — not yet available.
Section: DOC-DX-local-tooling#development-session.
- Sign in and choose a saved deployment profile. Inspect the selected API origin, account and project before making requests.
- Select your authorized test environment and use controlled data and recipients. Test work can still call paid models or tools; review spending controls.
- Run a conversation operation and inspect its conversation ID, run ID and status. Use the first conversation guide for the workflow.
- Check the result, then exercise an interrupted request or denied action using integration testing.
The session is ready when the controlled message reaches the expected conversation result and you can recover its identity after an interrupted wait.
For CI, supply credentials and required inputs explicitly. Noninteractive commands return structured results without opening a browser or waiting for input. A missing input returns an error and a nonzero exit status.
The current HTTP API does not provide separate test projects or test keys. Follow the current testing guide until those controls are available; naming a local profile “test” does not create an isolated environment.
Receive events in your local webhook handler
Status: Upcoming — not yet available.
Section: DOC-DX-local-tooling#local-event-forwarding.
Select the project, event types and local handler URL for a forwarding session. The session shows deliveries and your handler's responses so you can debug your integration while it runs locally.
For example, subscribe to llm.message_published and inspect how your handler processes a new message. After a disconnect, the session identifies deliveries you can recover and any gap that has expired. Redelivering an event keeps its original identity; it does not repeat the action that produced the event.
Synthetic fixtures, event redelivery and a new business action are separate choices. Your receiver still verifies and deduplicates deliveries.
Until local forwarding is available, use an explicitly registered HTTPS receiver through webhook setup.
Resolve a failed request
Status: Upcoming — not yet available.
Section: DOC-DX-local-tooling#request-diagnostics.
| What you see | What to do |
|---|---|
| Authentication rejected | Check the selected API origin and credentials. Refresh an expired user token; replace a revoked key through its supported recovery process. |
| Permission denied | Check that the selected account and key can perform the action on that resource. |
| Rate limit reached | Follow the returned retry guidance within your request deadline. Request limits and spending budgets are separate controls. |
| Connection lost after submission | Keep the known request or run ID and check its outcome before submitting another action. |
| API unavailable | Retain the request ID and time for your Travila operator. Self-hosted operators can use their deployment's troubleshooting guide. |
The CLI keeps structured results separate from diagnostic messages and returns a failure exit status for unsuccessful commands. An interrupted action reports its known identity and recovery information, so automation can stop or recover without treating an unknown result as a completed request.
Finish development and sign out
Status: Upcoming — not yet available.
Section: DOC-DX-local-tooling#session-cleanup.
Remove the test resources you created through their supported operations and check whether cleanup completed. Signing out does not delete resources or cancel persistent schedules.
Logout removes local credentials and reports remote revocation separately. If your machine is offline, remote revocation remains unconfirmed. This lets you distinguish a cleared workstation from a credential that may still work elsewhere.
For an operator-controlled installation, see deployment and operations. Use SDKs to embed the same application workflows in code or developer skills to work with a coding agent.
Document ID: DOC-DX-local-tooling. Section identities and revisions.