Security & data handling

How Fettl handles your code.

Your source does not need to leave your machine for Fettl to inspect it. Local analysis and account services have distinct roles.

Review the source, access, and repair boundaries before introducing Fettl to your workflow.

Data handling

Local analysis and connected services.

ON YOUR MACHINE

Code analysis and local findings

The full-local OSS product includes checks and supported agent hooks without an account, subscription, or lifetime scan meter. Local findings and repair verification stay in your workflow.

ACCOUNT SERVICES

Identity and managed access

Managed login uses the browser and account service to issue signed grants. These grants authorize managed capabilities; they do not gate the OSS local toolkit. The CLI stores credentials through the operating system’s secure credential store. Local access does not grant hosted resources or authorize wider data disclosure.

Deterministic repairs

Apply. Check. Keep or restore.

Repairs use staged changes by default. Broader scope requires explicit --full; preview and --safe controls remain available. Explore verification and recovery below.

normalize.tsRepair example · CQ003
// TODO: implement normalizeLabel  export function normalizeLabel(label: string) {
    return label.trim().toLowerCase();
  }
fettl fix --filter CQ003 --dry-run
Planned

Remove the stale TODO.

The function already works. Only its outdated comment needs to go.

If recovery needs attention

If Fettl cannot confirm that the original files were restored, it keeps backups and reports what needs recovery.

Fettl fixes eligible defects. Architecture and product decisions stay with you.

Agent hooks

Checks at the moments that matter.

Five native events across three agents, included in the full-local OSS product.

Claude CodePreToolUsePostToolUseStop
PreToolUse
Checks a proposed shell command or edit. Can block an unsafe action before it runs.
PostToolUse
Checks the result of a shell command or edit and returns findings to the agent.
Stop
Checks completion evidence when the assistant finishes.
Codex CLIPostToolUse
PostToolUse
Checks completed tool work and returns findings for the agent’s next action.
Hermespost_tool_call
post_tool_call
Checks code after write_file or patch completes and returns findings to the agent.

Post-tool checks act on completed work. Missing or incomplete analysis is reported explicitly.

Planned: richer agent steering

User-configured model providers, confirmed rules from your feedback, questions when intent is unclear, and synced profiles.

Security questions

Discuss your security requirements.

Ask about data handling, access, or repairs.

Ask a security question

Choose what you share. Privacy notice