How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/dozaldevs/dozaldevs-skills --skill manage-ai-employeesBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Manage AI Employees
This lists and manages the human's existing AI employees and the account around them.
Prerequisite: loadoperate-ai-employeesfirst. It sets up thedozaldevsCLI and the key, and explains levels, paging and errors.
The CLI fills in the organization. For a command's arguments and body, run dozaldevs <command> --help. Error codes and concepts: ../operate-ai-employees/references/customer-api.md. This file is only the behavior you can't read off the spec. Answers are short; --detailed gives every field (a Dozal's execution_steps, for one). --detailed needs dozaldevs 0.5.0 or newer (an older CLI reads the flag as needing a value).
List employees
dozaldevs list-dozalsThe answer is { "items": [...], "page": { "next_cursor", "limit", "has_more" } }. A list shows one page; add --all to get every item. Useful fields:
role_name: the display name (renameable).slug: the stable identifierrun-ai-employeeneeds. It never changes, even after a rename.status:active(live),paused(was live, temporarily off),draft(saved, never activated),superseded(replaced).identity,overview: what it is, in plain language.
Present a friendly roster, not JSON.
Pause, reactivate, rename, edit
update-dozal takes the archetype UUID from the list (not the name) and needs Admin. Pausing keeps its "was live" identity, and a paused employee won't run, even on its schedule. Use paused for a live employee, never draft.
dozaldevs update-dozal "$DOZAL" --data status=paused--data status=active reactivates and re-checks connections.
Each content edit bumps the Dozal's version and must send the current one as base_version (else 400 BASE_VERSION_REQUIRED):
dozaldevs list-dozals --id "$DOZAL" --field items[0].version
dozaldevs update-dozal "$DOZAL" --data role_name="$NEW_NAME" --data base_version:="$VERSION"If someone changed it since, 409 VERSION_CONFLICT: read again and redo your change. Reverts and template updates need base_version too; a status-only update needs none. Approving or denying a suggested cleanup needs no version; 409 SUGGESTION_OUT_OF_DATE means it was withdrawn: re-read, don't retry.
Each save answers changes, what really changed; trust it. Test first: --validate_only true. edits, fields only update-dozal changes, what it's told, undoing: references/checking-and-undoing.md.
To change what the employee actually does ("make the summary shorter", "also post to Slack"), use the Hiring Dozal's edit chat described in hire-ai-employee:
dozaldevs start-hiring-chat --data kind=edit --data archetype_id="$DOZAL"The assistant holds each change for a check (the chat's held_change): read it, show the human each part's before and after, and decide it as hire-ai-employee describes under "Hiring the Dozal". Nothing changes on the live employee until then; if it changed elsewhere, the save fails 409 VERSION_CONFLICT and the assistant proposes it again.
Connections
dozaldevs list-app-connections
dozaldevs list-integrations
dozaldevs list-integrations-needing-attentionIn order: the connected apps (Gmail, Jira, Google Sheets and the rest, each account with its id and health), the connections made through DozalDevs' own integrations (Slack, GitHub, website sign-ins), and what needs fixing. For "is Gmail connected?", read list-app-connections: an app missing from list-integrations can still be connected.
Connecting is two steps and the second is a person's. Start it, which returns a url. Give it to the human, who opens it and approves. Then run list-app-connections (or list-integrations for Slack and GitHub) to see it connected. Don't claim it worked before you've seen that.
dozaldevs start-app-connection --toolkit "$APP" --field url
dozaldevs start-slack-install
dozaldevs start-github-installGitHub's "link an installation that already exists" is a person's job (403 PERSON_ONLY). Confirm before disconnecting anything: employees that use it stop working.
Schedules
dozaldevs list-schedules
dozaldevs get-dozal-schedule "$DOZAL"Scheduled employees with their next run, and one employee's next and last run. To change the timing, edit it as above. run-schedule-now (it takes the employee's $SLUG) makes the next scheduled run start now, and resume-dozal-schedule switches a scheduled employee back on after repeated failures paused it. Find out why it failed first (monitor-and-review-ai-employee-work).
dozaldevs run-schedule-now "$SLUG"
dozaldevs resume-dozal-schedule "$DOZAL"get-dozal-schedule also answers schedule_estimate. Over 24 runs a day needs the human's yes; an employee can start from a Slack tag. See references/schedule-estimate-and-slack-start.md.
Handoffs
A handoff makes one employee start another when it finishes. get-handoff-graph shows the whole workflow, list-dozal-handoffs one employee's. Say plainly which employee starts which.
dozaldevs get-handoff-graph
dozaldevs list-dozal-handoffs "$DOZAL"
dozaldevs create-handoff --data upstream_archetype_id="$UPSTREAM" --data downstream_archetype_id="$DOWNSTREAM"
dozaldevs update-handoff "$HANDOFF" --data status=inactive
dozaldevs delete-handoff "$HANDOFF"update-handoff turns one active or inactive; delete-handoff removes it.
Members and invitations
dozaldevs list-members
dozaldevs list-invitations
dozaldevs revoke-invitation "$INVITATION"revoke-invitation cancels a pending one; a key can't invite anyone or change or remove a member (403 API_KEY_NOT_ALLOWED): tell the human to do that in the dashboard.
Usage and bills
Read only. get-cost shows what the organization was charged over a date range (--from ... --to ...), list-run-costs the runs with what each cost, get-run-cost one run, get-billing the balance and status. Report figures as given. Paying, buying credits, billing accounts and moving the organization between accounts are a person's (PERSON_ONLY or API_KEY_NOT_ALLOWED).
dozaldevs get-cost --from "$FROM" --to "$TO"
dozaldevs list-run-costs --from "$FROM" --to "$TO"
dozaldevs get-run-cost "$TASK"
dozaldevs get-billingReview recent runs
dozaldevs list-tasks --limit 10Same items and page envelope. For a run's output or logs, use monitor-and-review-ai-employee-work with its id.
Removing an employee
delete-dozal is a recoverable soft-delete. Confirm with the human first; pausing is usually better.
dozaldevs delete-dozal "$DOZAL"Saved setups
save-org-snapshot stores the organization's employees, departments, handoffs, rules and knowledge under a label as the next version. Sites, connections, secrets, channels, members, keys, templates and billing are not saved and never touched. Needs Admin.
dozaldevs save-org-snapshot --data label="$LABEL"
dozaldevs list-org-snapshots
dozaldevs preview-org-snapshot-apply --label "$LABEL"
dozaldevs apply-latest-org-snapshot --data label="$LABEL"
dozaldevs get-org-snapshot-apply "$APPLY"Also get-org-snapshot, delete-org-snapshot, apply-org-snapshot (by id). Applying cancels every open run and deletes employees not in the saved setup: preview first (read-only), then confirm the deletes with the human. It answers 202 with an apply_id; poll get-org-snapshot-apply until status isn't running. Outcomes, errors, warm-up, preserved employees, pending rules: references/org-snapshots.md. Org access and agent boxes: references/agent-boxes.md.