Menu

1 / 2

I Tested Privacy-Aware Routing with 4 AI Agents: What Actually Stayed Local

DEV Community·Shouvik Palit·6 months ago
#K9xjQDnF
#agents#ai#claude#trooper#local
Reading 0:00
15s threshold

Following up on my earlier Trooper experiments , I wanted to see if per-request privacy routing actually works in practice.

The test: 4 agents running simultaneously. Some handling public knowledge (OAuth security, Redis vs Memcached). Others handling sensitive data (API keys, customer PII).

The rule: Credentials and PII stay on my machine. Everything else can use Claude.

The Setup

Each agent gets a x_force_local flag:

Agent 1 - security-analyst (☁️ Claude)

Task: "What are the top 3 OAuth2 vulnerabilities?" Routing: Public knowledge, let Claude handle it

Enter fullscreen mode

Exit fullscreen mode

Agent 2 - credential-formatter (🔒 Qwen local)

Task: "Format as JSON: api_key=sk-prod-x7f9k2m, vault_url=https://vault.acme.io:8200" Routing: Contains credentials — must stay on machine

Enter fullscreen mode

Exit fullscreen mode

Agent 3 - architecture-advisor (☁️ Claude)

Task: "Redis or Memcached for session storage?" Routing: General best practices, use cloud

Enter fullscreen mode

Exit fullscreen…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.