pd integration <command>
Publish or inspect cross-agent ready/needs signals.
Run pd integration <command> like this
pd integration statusCommand contract
pd integration <command>
/docs/cli/integration
Ports, Services, Projects, And Orchestration
daemon-backed CLI command
cli/commands/services.ts, cli/commands/projects.ts, cli/commands/orchestration.ts, cli/commands/integration.ts, cli/commands/dns.ts
none
human display with command-specific state changes
generated API spec from the source-backed catalog
This clip shows the daemon health check, command discovery, and message-loop patterns that recur across the CLI reference. Here it grounds the pd integration <command> reference: daemon health, discovery, and message-loop patterns these pages keep pointing back to.
Common ways this command shows up in practice
pd integration <command> belongs to Ports, Services, Projects, And Orchestration. Claim deterministic ports, discover services, manage project records, start stacks, and publish readiness.
daemon-backed CLI command. Validate live behavior from the daemon and handler source when changing this command.
Use this page as the stable public contract for pd integration <command>; aliases resolve to the same contract.
Options that change command behavior
ready
Publish a readiness signal.
needs
Publish a dependency or missing-readiness signal.
list
List records for this command family.
Examples
Run pd integration <command> from a coordinated checkout
pd integration status
Runs the pd integration <command> command family and prints the resulting Port Daddy state, ids, or readiness/error details.
Find this command from the full CLI reference
pd help integrationopen /docs/cli/integration
The help topic and docs route both describe pd integration <command>, including aliases, flags, and source provenance.