Tool request summaries
Stored as local operational evidence without exposing API keys, raw prompts, or unredacted secret content.
Trust model
Powerful local tools need visible boundaries.
Dvara expands LLM capability while keeping local execution explicit, inspectable, and interruptible.
Alpha boundaries
- Local desktop runtime is the execution layer; the website never controls the user's computer.
- Managed browser uses an isolated profile instead of the user's personal Chrome profile.
- Workspace tools are read-only until a human applies a validated patch from the desktop UI.
- Emergency stop blocks browser, workspace, patch, MCP, and chat tool execution.
Boundaries in the alpha
- Local desktop runtime is the execution layer; the website never controls the user's computer.
- Managed browser uses an isolated profile instead of the user's personal Chrome profile.
- Workspace tools are read-only until a human applies a validated patch from the desktop UI.
- Emergency stop blocks browser, workspace, patch, MCP, and chat tool execution.
- Dvara does not provide terminal execution, cookie/password access, broad silent control, remote gateway, marketplace, billing automation, or team admin in the alpha.
What gets recorded
Approval and denial decisions
Stored as local operational evidence without exposing API keys, raw prompts, or unredacted secret content.
Artifact references
Stored as local operational evidence without exposing API keys, raw prompts, or unredacted secret content.
Failures and recovery states
Stored as local operational evidence without exposing API keys, raw prompts, or unredacted secret content.
Emergency stop changes
Stored as local operational evidence without exposing API keys, raw prompts, or unredacted secret content.
Patch hashes and hunk counts
Stored as local operational evidence without exposing API keys, raw prompts, or unredacted secret content.