Skip to content

feat(core): read [privacy] from uteke.toml in the CLI, server and MCP (#1464, part 2b-2a) - #1508

Merged
ajianaz merged 1 commit into
developfrom
feat/privacy-config-and-reporting
Oct 21, 2026
Merged

ajianaz merged 1 commit into
developfrom
feat/privacy-config-and-reporting

Conversation

@ajianaz

@ajianaz ajianaz commented Oct 21, 2026

Copy link
Copy Markdown
Collaborator

What

[privacy] in uteke.toml (mode = redact | strict | off, allowlist regexes) and UTEKE_PRIVACY_MODE now configure the secret filter. One loader, privacy::load_config(), is used by the CLI, uteke-serve and uteke-mcp. The section is in the untrusted project keys: only the global file is read for it, so a cloned repository cannot switch the filter off or allowlist everything. An unknown mode or an invalid regex falls back to the default for that setting (a bad regex keeps strict, a bad mode keeps the allowlist); the filter never turns itself off because of a typo. Documented in docs/configuration.md.

Why

Part of #1464. Until now the write path used the built-in default (redact) with no way to change it. Response fields and the strict 400 body follow in 2b-2b. Refs #1464.

Testing

  • clippy -D warnings, fmt and cargo test --workspace pass; cargo run -p docgen changes nothing
  • new tests: settings to config, per-setting fallback, and the project file being ignored for [privacy] (reported in ignored_untrusted)

@github-actions

Copy link
Copy Markdown

🔍 Cora AI Code Review

✅ No issues found. Code looks good!


Review powered by cora-code · BYOK · MIT

@ajianaz
ajianaz merged commit 367d3dd into develop Oct 21, 2026
15 checks passed
@ajianaz
ajianaz deleted the feat/privacy-config-and-reporting branch October 21, 2026 07:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant