How it works

AI asks. Dvara governs.

Chat requests become controlled browser, workspace, and patch actions through one local policy layer.

Core loop

  • Ask in chat.
  • Dvara checks client, grant, domain, and tool policy.
  • The managed capability runs locally.
  • Result, artifact, and audit entry stay visible.

Simple flow

The product in six steps

01

Ask normally

You use Dvara like a normal LLM chat: research a site, inspect a repo, or prepare a local change.

02

Dvara detects local work

Browser, workspace, and patch requests become clear governed actions instead of hidden execution.

03

Policy checks the request

Client identity, tokens, grants, domains, blocked paths, redaction rules, and emergency stop are checked first.

04

The managed capability runs

Dvara uses an isolated browser, read-only workspace tools, or a patch artifact path under the desktop runtime.

05

You keep the write boundary

Agents can propose patches. Humans review and apply selected changes from the desktop UI.

06

Everything is auditable

Actions, approvals, failures, artifacts, and summaries stay visible in a local audit trail.

What it is

A control layer, not another standalone chatbot

It expands what LLMs can do on your computer.

It keeps browser and workspace actions inside a governed desktop layer.

It avoids personal Chrome profile access, passwords, cookies, terminal execution, and silent broad control.