Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.mistle.dev/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Sessions are interactive agent workspaces started from a sandbox profile. Use sessions for work such as:
  • debugging failing tests
  • reviewing code changes
  • implementing repository changes
  • investigating logs or provider state through integrations
  • preparing pull requests
Each session runs in a sandbox environment with the tools, setup, and integration access defined by the selected sandbox profile and organization configuration.

​
How Sessions Start

When a user starts a session, Mistle selects the requested sandbox profile version and creates a sandbox for the agent. If the profile version has a usable snapshot, the sandbox can start from that prepared image. This avoids repeating setup work that was already captured by the profile snapshot.

​
Start A Session

To start interactive agent work:
  1. Open Sessions.
  2. Create a new session.
  3. Choose the sandbox profile for the work.
  4. Choose the repository or workspace when the profile provides options.
  5. Describe the task for the agent.
  6. Start the session.
If the profile is not available for new sessions, check that the profile has a published version and a ready snapshot.

​
Agent Access

Agents can use configured integrations to interact with external systems. Credentials are managed by Mistle and are not placed directly inside the sandbox as long-lived secrets. The exact tools and provider access available in a session come from the profile, organization settings, and connected integrations. When an agent writes back to supported external systems, Mistle adds a link back to the session where the work happened. For example, Slack messages, GitHub comments or pull requests, Jira issues or comments, and Linear issues or comments can include a View session link. That link lets teammates open the Mistle session behind the external update and inspect the work context.

​
Persistence

Sessions are workspaces for ongoing agent work. By default, session sandboxes are ephemeral. Use Snapshots when a workflow needs a reusable prepared environment for many future sessions. Use Persistent Sandboxes when a specific session’s working state should survive compute stops, resumes, or provider expiry. Persistent sandboxes are experimental and require both organization-level enablement and profile-level opt-in.

​
Next Steps