oz0 memory person

Usage and flags for oz0 memory person.

For: Operators and developers looking up a command.

Turn memory about people on for an agent, for purposes its definition declares, each with a legal basis in the tenant's lists (oz0 inventory purposes); the agent's jobs keep it only when they run for one of those purposes. Its records about people stay in its own scope unless --share names another agent (agent:<name>, which then reads them), a project (project:<name>) or the tenant (tenant). --purpose and --share replace the lists; --off turns it off.

Turning it on or sharing it further waits for another admin with four eyes on, and always in works-council mode. Whether the tenant may keep such memory, for which purpose and on which legal basis, is the tenant's to decide.

Usage

oz0 memory person AGENT [flags]

Flags

FlagTypeDefaultDescription
--decision-refstringthe decision or case the change follows, such as a case number (at most 200 characters)
--jsonboolprint JSON instead of a table
--offboolturn memory about people off for the agent
--purposestringArraya purpose the agent keeps memory about people for (repeat for more)
--reasonstringwhy, required for every governance change (at most 500 characters; default $OZ0_REASON); the audit log keeps it
--sharestringArraywhere its records about people are shared: agent:<name>, project:<name> or tenant (repeat for more)

Inherited flags

FlagTypeDefaultDescription
--contextstring$OZ0_CONTEXT or <config dir>/orchestrator-zero/context.jsonCLI context file written by server init
--log-levelstringinfolog level: debug, info, warn or error
--tenantstringdefaultthe tenant

See all oz0 commands and the global flags.

On this page
Copyright © 2026