Skip to content

Usage

Once installed, Tegvia runs on its own: the background service starts it when you log in and keeps it running. There is nothing to type in Claude Code; you control Tegvia from the web console and from the service command.

To run it without the service, see Standalone deployment.

Pausing and resuming

What you want How
Pause inspection but keep Tegvia running Turn off the protection switch in the web console (Protection card in the menu, or Settings page). The proxy relays requests without inspecting or logging them. Turn it back on from the same page.
Stop Tegvia completely sh launch/tegvia-service.sh stop (launch\tegvia-service.cmd stop on Windows): stops the proxy and restores settings.json. It is not restarted automatically.
Start it again sh launch/tegvia-service.sh start (launch\tegvia-service.cmd start).
See the state sh launch/tegvia-service.sh status (launch\tegvia-service.cmd status): service active or not, settings.json redirected or not, console address, log paths and, if the proxy is down, the end of its error log.
Open the web console http://127.0.0.1:8736/tegvia/ui/ (printed by install and status).

All the service subcommands are described on the Background service page.

Restart Claude Code after start / stop

Claude Code reads settings.json at start-up. After a stop or a start, the current session keeps its old behaviour: open a new session (or restart Claude Code) for the change to apply.

When an action is blocked

Blocked tool call (for example a curl … | sh command): the response continues, but the call is replaced by a notice:

TEGVIA Protection

A tool call in this response was blocked by the `pipe_to_shell_check`
module (OWASP:LLM06) because it was judged unsafe to execute.

Reason: Bash command pipes into a shell: output is piped into a shell
interpreter ('sh')

The command is not run. Claude sees this message and can suggest an alternative (for example download the script, show it to you, then run it in two steps).

Blocked request (for example a canary token was found): the request is not sent to the API, and Claude Code shows an error containing the same kind of notice, with the module, the reason and the session id.

The language of these messages is set with TEGVIA_LANGUAGE.

If a block looks wrong, see Troubleshooting.

Session logs

Every exchange is recorded in a single SQLite database, ~/.tegvia/tegvia.db, in the Tegvia data folder (TEGVIA_HOME changes it). Nothing is purged.

You read them in the web console (Overview, Alerts, Tools, Sessions screens), or by querying the database yourself (see below). Times are shown in your local time.

Sensitive data

The database contains the full content of requests and responses: your messages, the code and files Claude read, and the model's answers. The x-api-key and Authorization headers are truncated, but nothing else is. The same goes for the tegvia.db.bak-v<n> copies and the tegvia.db.pending file next to the database. Protect this folder accordingly.

To query the database from a script.