zdev config

Read or change project settings and the worker profiles used by coding agents. The effective view combines repository settings, user settings, and defaults, so you can see what a worker will actually use.

Examples

zdev config show
zdev config set project.default-area greeting

Read and change settings

Form	Effect
`zdev config show [–local	–global]`
`zdev config get KEY [–local	–global]`
`zdev config set KEY VALUE… [–local	–global]`
`zdev config unset KEY [–local	–global]`
zdev config trunk [BRANCH]	Set trunk to a named branch or the checked-out branch.

Project keys include project.trunk, project.default-area, and project.guidance. Project name and record policy are set at initialization and are read-only afterward. Worker keys have the form worker.HARNESS.ROLE; their value is either inherit or a model and effort provided together.

Project settings are repository-only. Worker settings can be local or global; use an explicit scope when changing them. --allow-divergent on set or trunk permits a project-trunk ancestry discontinuity. The configuration reference defines all keys, default write scopes, precedence, and validation rules.

Execution profiles

Named profiles collect role choices for a harness. Inspect available profiles with zdev config profile list, then use zdev config profile show normal codex to see resolved roles.

Subcommand	Arguments and purpose
list	List built-in and configured names.
show NAME HARNESS	Show resolved roles in one profile.
set NAME HARNESS ROLE MODEL EFFORT	Set a role; use inherit in place of MODEL EFFORT to inherit it.
unset NAME HARNESS ROLE	Remove a custom role row.
set-default NAME	Save a default profile.
unset-default	Clear the saved default.
resolve HARNESS ROLE	Resolve a concrete role without changing settings.
dispatch-spec ROUTE	Produce a worker dispatch sequence for a task and stored context.

These subcommands follow zdev config profile. Profile writes default to repository-local configuration; add --global for user configuration. resolve accepts --profile, --run-profile, and --area to model a specific selection. dispatch-spec supports plan-next-task and implement, and requires --harness, --area, --task, and --snapshot.

See worker profiles for role selection and work-context for stored snapshots. Run zdev config profile dispatch-spec --help for retained-plan and role-override options.