primcli 1.33.0 → 1.34.0

package/dist/oclif/root-signup-hint.js

@@ -1,4 +1,4 @@
-import { S as normalizeApiBaseUrl, c as resolveConfigEnvironment, i as loadCliConfig } from "../cli-config-Cv2-NAOd.js";
+import { S as normalizeApiBaseUrl, c as resolveConfigEnvironment, i as loadCliConfig } from "../cli-config-x39ZVsXJ.js";
 import { existsSync, readFileSync } from "node:fs";
 import { join } from "node:path";
 import { homedir } from "node:os";

package/man/primitive.1

@@ -34,11 +34,17 @@ credential. This mode requires WebSocket and the shared saved subscription;
 --transport poll and a custom --subscription are rejected. The local-mail-*
 subscription namespace is reserved for shared receiving. No runtime is launched. Repeat --sender or use comma-separated exact
 addresses. Routine authenticated status interactions do not notify the session.
+Verified receiver presence controls are answered deterministically while the
+exact session binding is eligible. They do not start model turns, wake Claude,
+complete chat waits, or consume --once or --number. Pending verification remains
+durably deferred and reconciles independently of ordinary mail.
 .PP
 .B primitive listen --status --notify-session UUID
 inspects local notification receipts without receiving mail or connecting to a
 session. Accepted means queued; unknown outcomes are held across restarts and are
 never automatically resent. Inspect the exact session before a manual resend.
+An explicit Codex Review or Compact refusal is recorded as not_submitted and
+retried after a short delay; a timeout remains unknown.
 Use --limit (default 100, maximum 1000) and --cursor with the returned nextCursor
 to page through receipts. Notification subscriptions accept email.received only;
 --once counts a candidate processed during this invocation, including filtered
@@ -233,6 +239,15 @@ stable idempotency key. After a lost send response, repeating the same command
 looks up that key without sending again. Timed-out exact-parent waits retain
 their claim for resume. A plain reply does not prove task completion.
 
+.SS Organization agent network
+.B primitive network peers --owner NAME --json
+finds listed agents owned by a coworker in the private default organization
+network. Results include address, owner name and last recorded API activity;
+activity is not live presence. Use the returned cursor for further pages.
+The owner can separately allow an agent to see peers or be seen. Contacts are
+saved addresses, not the network roster. Network listing and contact acceptance
+do not grant task authority. Known addresses can still exchange ordinary email.
+
 .SS Explicit communication signals
 .B primitive signal read --id EMAIL_ID --json
 reports that you read one authenticated plain email.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "primcli",
-  "version": "1.33.0",
+  "version": "1.34.0",
   "description": "Official Primitive CLI: deploy Primitive Functions, send and inspect mail, manage endpoints, all from the terminal. Wraps the @primitivedotdev/sdk runtime client with one-shot commands.",
   "type": "module",
   "sideEffects": false,
@@ -50,10 +50,10 @@
         "description": "Manage your account settings, storage, and webhook secret"
       },
       "agent-connections": {
-        "description": "Claim a private invitation from stdin or remove a revoked connection with an owner/admin login."
+        "description": "Create, list, invite, revoke, and remove connected agents; claim private invitations through stdin."
       },
       "agent": {
-        "description": "Connect an invited session, enroll a new session using a saved owner login, disconnect one saved profile, or manage contacts and signup."
+        "description": "Connect an invited session, enroll a new session using a saved member login, disconnect one saved profile, or manage contacts and signup."
       },
       "credits": {
         "description": "Redeem credit codes and check the organization credit balance"
@@ -64,6 +64,12 @@
       "registries": {
         "description": "Create and manage agent registries, publish and resolve agents by handle, and moderate publication requests"
       },
+      "network": {
+        "description": "Discover same-organization agents by email address and manage default network visibility. Use `primitive network` to see the commands."
+      },
+      "agent-networks": {
+        "description": "Generated agent network API operations. Prefer `primitive network` for discovery and visibility."
+      },
       "inbox": {
         "description": "Check inbound email setup and readiness, and work through mail awaiting your reply. Prefer `primitive inbox setup` for a guided setup path, `primitive inbox status` for the readiness table, and `primitive inbox next` for the oldest email awaiting your reply."
       },
@@ -129,7 +135,7 @@
         "description": "Schedule and send wake commands to your own functions over signed email, and manage which senders may wake them. Use `primitive wake schedules list|create|get|update|delete|run`, `primitive wake authorizations list|create|update|delete`, and `primitive wake dispatches list`."
       },
       "listen": {
-        "description": "Receive events locally as JSONL with JSON status responses by default; --json is accepted explicitly. Use --exec or --forward-to, or deliver external mail events as tool output, never user messages, to an exact loaded native session using --notify-session with --contacts or approved --sender addresses. Add --email-id to --status to explain one received email. Add --contact-requests for owner-enabled structured first-contact intake. Use --background for independent receiving, --status --notify-session for current receiver health and durable receipts, or --stop --notify-session to stop only that receiver."
+        "description": "Receive events locally as JSONL with JSON status responses by default; --json is accepted explicitly. Use --exec or --forward-to, or deliver external mail events as tool output, never user messages, to an exact loaded native session using --notify-session with --contacts or approved --sender addresses. Add --email-id to --status to explain one received email. Add --contact-requests for owner-enabled structured first-contact intake. Use --background for independent receiving, --status --notify-session for current receiver health and durable receipts, or --stop --notify-session to stop only that receiver. Verified presence controls use no model turns and do not consume --once or --number."
       },
       "contacts": {
         "description": "Shared organization contacts plus structured request, accept, and wait commands for connected agents. Directory list, get, add, update, and remove use conditional versions. Commands return JSON by default and accept explicit --json."