[!] TOPIC ARCHIVE // #PERMISSIONS
#Permissions
All 9 guides, operator dossiers, and signals tagged with #Permissions.
four places to keep the operator in the loop
A phone file editor, Rome’s first-run boundary, uniTerm’s shell approvals, and OpenHuman’s searchable tool-result handles.
an agent gets a family account; another stops spending turns on a waiting room
Google turns CC into a shared household agent, Unreal Agent moves tool waits into its harness, and Stroq adds retrospective session inspection.
Who gets to control the agent?
Three tools make agent work more inspectable: an orchestration layer, a sidecar for instructions, and a deck that checks its claims against the code.
agent records
A signature, a task journal, and a persistent workspace answer different questions. Only one says who is answerable for the work.
memory needs a boundary
Agent memory is becoming a system of record: what survives a session, who can inspect it, and where an agent must stop.
intent files, runtime logs, and agent plugins
Huzzah, Apache Maka, and Cursor plugins move intent, execution records, and external-system access out of the disposable chat transcript.
the permission prompt lost its job
Claude Code will use auto mode by default for new Pro, Max, and Team sessions from August 14, moving safety from a stream of prompts into configurable standing rules.
agent traces, permission profiles, and orchestrated PRs
TraceLab measures real coding-agent loops, Codex points users to beta filesystem and network permission profiles, and Agentic Orchestrator turns feature prompts into gated PR workflows.
Claude Code Session Preflight
Ten read-only checks to run before a serious Claude Code session: version, model, permissions, MCP servers, context, and rollback.