@agentify/cli

The Agentify CLI is the encrypted local runtime for delegating bounded Codex tasks through Agentify. This npm package distributes the executable; Agentify source code is not published or licensed for redistribution.

Support

• Product: https://agentify.sh
• Issues: https://github.com/agentify-sh/chat/issues
• Email: [email protected]

Install

npm install --global @agentify/cli
agentify auth login --method device
agentify doctor

The Agentify Codex plugin is the primary interface. It starts agentify mcp locally and supplies Owner and Operator workflows directly in Codex Desktop and Codex CLI.

Owner CLI fallback

agentify delegate sessions --workspace "$PWD" --json
agentify delegate --workspace "$PWD" --thread <codex-thread-id> \
  --goal "Complete the bounded task" \
  --must-have "The focused regression passes" \
  --verify "npm test -- signup" \
  --allow-command "npm test" \
  --allow-file-root "src/auth" \
  --save-draft --json

agentify delegate confirm <agentify-job-id> --operator-id <operator-user-id>
agentify delegate run <agentify-job-id> --watch
agentify delegate owner-approvals <agentify-job-id> --json
agentify delegate notifications --after 0 --json
agentify delegate review <agentify-job-id> --json
agentify delegate accept <agentify-job-id> --delivery-id <delivery-id> --json

Operator CLI fallback

agentify delegate operator-register --key-id founder_primary --json
agentify delegate operator-queue --json
agentify delegate operator-open <agentify-job-id> --json
agentify delegate intervene <agentify-job-id> \
  --kind send-instruction \
  --message "Run the next bounded repair and report the exact result" \
  --expected-effect "The focused check passes and stays inside scope" \
  --json

The Owner confirms one acceptance contract before delegation. Task content, grants, interventions, QA evidence, and delivery evidence are encrypted before cloud relay. Private keys, decrypted content, workspace access, signatures, and policy enforcement remain local. Production actions remain denied unless the Owner separately authorizes them and local policy permits them.

The hidden agentify finish command remains an exact compatibility alias for existing local state and scripts. Agentify Chat commands remain available for existing paired installations, but Chat is not the primary product interface.

Security Model

• Prompt and result payloads are encrypted before they leave the browser or local runner.
• The server does not receive the workspace encryption key.
• Poll tokens stay on the local machine.
• Browser enqueue tokens and approval state stay in the browser.
• V1 direct mode gives remote prompts the same local access as the selected CLI would have if you typed the prompt on this computer.
• Local logs stay on the paired computer.

Local Development

To exercise the npm wrapper against a local Rust build:

AGENTIFY_CLI_BIN=/absolute/path/to/agentify node ./bin/agentify.js --help

To stage the current Rust binary into the npm package layout:

cargo build --release
npm run stage:bin -- --force
node ./bin/agentify.js --help

To verify release readiness:

npm run release:check

Release automation

For one-command release prep across all supported platforms:

npm run release:all

From the workspace root, you can run the same flow with:

bash ../scripts/release-agentify-cli.sh

The release pipeline is non-publishing by default and runs:

• cross-platform Rust builds
• multi-target npm wrapper staging
• local version/release checks
• package verification
• release payload leak scan

Use explicit flags to publish:

npm run release:all:publish -- --npm-tag latest

or:

bash ./scripts/release-all.sh --publish-npm --publish-git --auto-commit --create-tag --push-git

Useful options:

--targets darwin-arm64,linux-x64
--publish-npm
--publish-git
--auto-commit
--create-tag
--push-git
--skip-leak-scan
--skip-cargo-test
--skip-npm-tests
--dry-run

Identity checks are enforced on publish:

• npm account must be agentify
• GitHub account must be waml

During local incubation, when only some platform binaries are staged, use:

npm run release:check -- --allow-missing-targets

Do not publish until the packed artifact has been inspected and the release check passes.