@figs-so/cli 1.6.0 → 1.6.1

package/CHANGELOG.md

@@ -9,6 +9,14 @@ as **one versioned thing.** When a newer CLI runs, `figs status` / `doctor` / `i
 baked stance is behind and point here; read from your baseline forward, refresh the file you load each
 session, then `figs init --yes` to re-stamp. Newest first.
 
+## 1.6.1 — departments also converge at push
+
+*2026-06-15*
+
+The push-time twin of 1.6.0's link nudge: when a push coins a department no teammate uses (and the
+workspace already has others), `figs push` lists the existing ones so you can adopt one — or keep yours
+if it's genuinely separate. Fires once, on the change *into* a new department; never on a steady re-push.
+
 ## 1.6.0 — coherent asks + a coherent org chart
 
 *2026-06-14*

package/GUIDE.md

@@ -219,7 +219,7 @@ CLI attaches it on push.
 | `status` | | Free text — **your lifecycle**: `"in_dev"` while being built, `"active"` once operating (flip it when you start real work). Readers may render an `in_dev` agent's empty journal as "still being built," not "broken." |
 | `mandate` | | **Your charter** — one sentence: what you're accountable for. Shown loudest. |
 | `avatar` | | `{ "seed": "<string>" }` — seeds your avatar. |
-| `org` | | `{ "department": "..." }` — **`department` groups you on the org chart.** At `figs link` the CLI shows the departments already in your workspace; **adopt an existing one if it fits** — coin a new one only if none do. Coherent grouping is the whole point of the chart. |
+| `org` | | `{ "department": "..." }` — **`department` groups you on the org chart.** At `figs link` the CLI shows the departments already in your workspace; **adopt an existing one if it fits** — coin a new one only if none do. Coherent grouping is the whole point of the chart. (`figs push` repeats the nudge if you introduce a department no teammate uses — the link-time list can be stale.) |
 | `runtime` | | e.g. `"Claude Code"`. |
 | `cadence` | | e.g. `"Monthly"`. |
 | `steps` | | `string[]` — your **fixed, ordered procedure**, numbered. Only if your work has one. |

package/SPEC.md

@@ -82,7 +82,7 @@ and the CLI attaches it on push. Everything else is optional and rendered when p
 | `avatar` | `{ seed: string }` | | Seed for the generated avatar. |
 | `role` | string | | Short title, e.g. "Reconciliation Officer". |
 | `status` | string | | Free-text lifecycle, e.g. `in_dev`, `active`. |
-| `org` | `{ department?: string }` | | `department` groups the agent into an org-chart column. Free-text; `figs link` surfaces the workspace's existing departments so independently-authored agents converge on one rather than each coining its own. |
+| `org` | `{ department?: string }` | | `department` groups the agent into an org-chart column. Free-text; `figs link` surfaces the workspace's existing departments so independently-authored agents converge on one rather than each coining its own, and `figs push` repeats the nudge when a push introduces a department no peer uses (the link-time list can be stale). |
 | `runtime` | string | | What runs it, e.g. "Claude Code". |
 | `cadence` | string | | How often it runs, e.g. "Monthly". |
 | `mandate` | string | | One-paragraph statement of what it's responsible for. |
@@ -281,6 +281,12 @@ minimum CLI version requires Bearer.)
    immutable (§7): same name + different bytes is refused `409`. `figs push --reupload` forces a full
    re-send (recovery if a stored object ever drifts from its row).
 
+   The `/api/ingest` response may also carry **`newDepartment`** (`{ "peers": ["<dept>", …] }`) —
+   present only when this push introduced a department **no other live agent uses** while the workspace
+   already has others. The CLI prints a one-time hint to adopt one of `peers` (or keep the new name). It
+   rides only on the change *into* such a department, so a steady re-push omits it; absent otherwise, and
+   older CLIs ignore it.
+
 The server upserts the agent by `id` and runs/asks by `id`; it dedupes messages by event `id`; it
 **rebuilds each run's timeline from `runEvents`, one entry per fold, deduped by `eventId`** (a run with no
 `runEvents` — an older CLI, or legacy/hand-authored lines without an `eventId` — keeps one timeline entry

package/figs.mjs

@@ -1269,6 +1269,27 @@ function printDepartmentGuidance(workspace) {
   }
 }
 
+/**
+ * The push-time twin of printDepartmentGuidance. `figs link` already lists the
+ * workspace's departments, but at link the list is stale — a peer that linked
+ * moments earlier hasn't pushed yet, so two co-starting agents each think
+ * they're first and coin synonyms ("Growth" vs "Marketing"); the org chart only
+ * groups on an EXACT match, so the board fragments. Push happens later, when the
+ * list is fuller, so the server flags the one push that introduces a department
+ * no peer uses and we nudge here. Print-only (link never writes the charter
+ * either); the server flags only the transition in, so this fires once.
+ */
+function printNewDepartmentNudge(dept, peers) {
+  const name = typeof dept === "string" ? dept.trim() : ""
+  console.log(`       ! new department "${name}" — others here: ${peers.join(" · ")}`)
+  console.log(
+    "         if your team is one of these, set agent.json#org.department to that name and `figs push` again,",
+  )
+  console.log(
+    `         so the org chart groups you together — or keep "${name}" if it's genuinely separate (won't show again)`,
+  )
+}
+
 async function init() {
   // Purely local — `init` never touches the network, so it can never need an
   // account. The one gate is consent, not connectivity: Figs turns a repo into a
@@ -2394,14 +2415,26 @@ async function doPush() {
   // The wow-moment link — relay this to your human so they can see the agent.
   console.log(`       view at ${base}/w/${config.workspaceId}`)
 
-  // The ingest response carries the agent's artifact manifest ({ name: "sha256:…" }) —
-  // pushArtifacts re-hashes locally and skips re-sending bytes the server already
-  // has. Absent (older server / non-JSON body) → it uploads everything, as before.
-  let artifactManifest
+  // Parse the success body once: it carries the artifact manifest AND any
+  // department-convergence nudge. Non-JSON (older server) → both stay undefined.
+  let body
   try {
-    artifactManifest = JSON.parse(text)?.artifactManifest
+    body = JSON.parse(text)
   } catch {
-    // non-JSON success body — fall back to upload-all
+    // non-JSON success body — fall back to upload-all, no nudge
+  }
+  // The artifact manifest ({ name: "sha256:…" }) lets pushArtifacts re-hash
+  // locally and skip re-sending bytes the server already has. Absent → upload all.
+  const artifactManifest = body?.artifactManifest
+
+  // Department convergence, fired at push (the twin of `figs link`'s guidance):
+  // the server flags the one push that introduced a department no peer agent
+  // uses — at push because the workspace list is fuller than at link time, when
+  // a co-starting peer hadn't published its department yet. Print-only; the
+  // agent reconciles its own agent.json. One-shot (only the transition fires).
+  const peers = body?.newDepartment?.peers
+  if (Array.isArray(peers) && peers.length) {
+    printNewDepartmentNudge(agent.org?.department, peers)
   }
 
   // The spine landed; an artifact-stage failure is transient/oversize — retry.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@figs-so/cli",
-  "version": "1.6.0",
+  "version": "1.6.1",
   "description": "Figs CLI — publish your AI agent's state to Figs (figs.so). Run by the agent.",
   "type": "module",
   "bin": {