[P1] Implement model routing policies and optional remote providers #23

Closed
opened 2026-07-18 00:01:33 +00:00 by lost-rob0t · 0 comments
lost-rob0t commented 2026-07-18 00:01:33 +00:00 (Migrated from github.com)

Goal

Support popular AI providers without weakening local-first privacy guarantees.

Requirements

  • Routing policies: local-only, local-first, remote-explicit, and privacy-strict.
  • Provider strategies for OpenAI-compatible APIs, OpenRouter, Anthropic, and Google where practical.
  • Remote providers disabled by default and never selected merely because local inference failed.
  • Separate permission gates for redacted text, metadata, and images; images denied remotely by default.
  • Egress payload inspection, size limits, secret scanning, and sanitized audit records.
  • Provider credentials resolved through key providers.
  • Optional per-query confirmation/preview before remote egress.

Acceptance criteria

  • Local-only and privacy-strict modes make zero remote requests under failure conditions.
  • Remote calls contain only the explicitly allowed, already-redacted payload.
  • Tests use mock servers and verify headers, payload filtering, retries, and cancellation.
  • Provider errors cannot cause fallback to a less-private route.

Depends on

## Goal Support popular AI providers without weakening local-first privacy guarantees. ## Requirements - Routing policies: `local-only`, `local-first`, `remote-explicit`, and `privacy-strict`. - Provider strategies for OpenAI-compatible APIs, OpenRouter, Anthropic, and Google where practical. - Remote providers disabled by default and never selected merely because local inference failed. - Separate permission gates for redacted text, metadata, and images; images denied remotely by default. - Egress payload inspection, size limits, secret scanning, and sanitized audit records. - Provider credentials resolved through key providers. - Optional per-query confirmation/preview before remote egress. ## Acceptance criteria - Local-only and privacy-strict modes make zero remote requests under failure conditions. - Remote calls contain only the explicitly allowed, already-redacted payload. - Tests use mock servers and verify headers, payload filtering, retries, and cancellation. - Provider errors cannot cause fallback to a less-private route. ## Depends on - #6 - #9 - #21 - #22
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nsaspy/local-recall#23
No description provided.