As agents act for you, personal and work AI need separate boundaries
sujingshen · x · 2026-09-23
- Responding to Freda Duan, the author argues bundling personal + work in one chatbot super-app is fine (ChatGPT consumer usage is 70% non-work) since chat is passive and the split is only context.
- But once agents can place orders, edit files, and speak on your behalf, mixing the two worlds risks identity, permissions, data ownership, and liability. He proposes four boundaries to check: separate personal vs work identity; per-silo permissions instead of a master key; work red lines leaking into personal long-term memory; and data portability when you change jobs.
- Takeaway: sharing a window is fine, but personas and red lines shouldn't share a bed forever.
More from coding & agent
- Formally verify code with Opus 5.5 + Lean: a few prompts yield 16 bug-fix PRs — julianweisser · 2026-09-23
- Sergey Karayev: Google 'took itself out of the coding agent game' — sergeykarayev · 2026-09-23
- mcp-server-devutils: Zero-auth MCP server bundling base64, UUID, JWT decode, cron and more — modelcontextprotocol · 2026-09-23
- Why flat multi-agent design failed: a 3-level hierarchy from a hospital ops system — Repulsive_Sugar_5252 · 2026-09-23
- Kiso: an open-source agent runtime that makes crash-window tool executions explicitly uncertain — niurenwangdadan · 2026-09-23
- Open-source GUI agents top out at 8% task success on composite cross-device tasks — maier_ak · 2026-09-23