@appchy/jarvis 0.1.122 → 0.1.123

package/dist/bin.js

@@ -10286,7 +10286,7 @@ import { createRequire as createRequire2 } from "module";
 var _require = createRequire2(import.meta.url);
 var VERSION2 = _require("../package.json").version ?? "0.0.0";
 var IS_DEV = String(_require("../package.json").name ?? "").endsWith("-dev");
-var SHA = "63c9236";
+var SHA = "4d8962c";
 var BUILT = "2026-09-12";
 var BUILD = SHA ?? "source";
 var BUILD_LABEL = `${SHA ? `${VERSION2} (${SHA}${BUILT ? ` ${BUILT}` : ""})` : `${VERSION2} (source)`}${IS_DEV ? " \u2014 development build" : ""}`;

package/harness/harness/kickoff.py

@@ -167,15 +167,25 @@ def session_name(task) -> str:
     one Claude Code derives a name from the FOLDER — identical for every session
     in a repo, so several runs are told apart only by an id nobody reads.
 
+    **It is the item's NAME, not its title** (founder, 2026-09-12). A title is a
+    sentence — "The verify lock refuses cleanly but cannot say you are queued, or
+    that you were displaced" is 90 characters — and a picker truncates it to the
+    half that carries no information, so four sessions read as four rows of
+    near-identical prose. Worse, it is not a string a person can type: this name
+    is also what `ListAgents` lists and `SendMessage` addresses, so it has to be
+    something somebody can say out loud to point an agent at one session. The
+    item's name is already that — short, unique across the whole board by
+    construction, and the same word the person would use for the work itself.
+
     A run is numbered by how many have already worked the item, so the first is
-    just the title and the fifth says it is the fifth. The number leads because
+    just the name and the fifth says it is the fifth. The number leads because
     that is the column a picker never truncates, and the count comes off
     `sessions:` rather than being carried in the prompt: the wrap has just
     recorded the run doing the wrapping, so the successor is the next one along
     and nothing has to remember what number it is.
     """
     ordinal = len(task.sessions) + 1
-    return task.title if ordinal == 1 else f"{ordinal} · {task.title}"
+    return task.name if ordinal == 1 else f"{ordinal} · {task.name}"
 
 
 def cmd_kickoff(args) -> int:

package/harness/test_work.py

@@ -3566,6 +3566,32 @@ def test_a_slot_the_harness_cannot_write_is_not_reported_as_somebody_elses_run()
                 gate.VERIFY = old
 
 
+def test_a_session_is_named_for_the_work_not_for_its_title():
+    # The founder could see only prompts: a picker shows each session's FIRST prompt,
+    # which for a jarvis-started run is the whole kickoff block, so four sessions read
+    # as four walls of near-identical text. The name field existed and carried the
+    # TITLE — a 90-character sentence that truncates to the half saying nothing, and
+    # that nobody can type. It is also what `ListAgents` lists and `SendMessage`
+    # addresses, so it has to be a word a person can say out loud.
+    with tempfile.TemporaryDirectory() as tmp:
+        v = _tree(tmp)
+        e = _epic(v, "an-epic")
+        _task(e / "in-progress", "a-verify-says-whether-you-are-queued",
+              body="# The verify lock refuses cleanly but cannot say you are queued, "
+                   "or that you were displaced\n")
+        with _work_dir(tmp) as root:
+            task = model.locate(root, "a-verify-says-whether-you-are-queued")
+            assert kickoff.session_name(task) == "a-verify-says-whether-you-are-queued"
+            # The title is what it must NOT be, and the title is the long one.
+            assert len(task.title) > 60, task.title
+            assert task.title not in kickoff.session_name(task)
+
+            # A second run on the same item leads with the number, because that is the
+            # column a picker never truncates.
+            task.sessions.append("2026-09-12  aaaa")
+            assert kickoff.session_name(task) == "2 · a-verify-says-whether-you-are-queued"
+
+
 def test_a_pid_somebody_else_owns_is_alive_not_dead():
     # Two readings of one pid: `peers._live` treats a kernel refusal as alive and
     # this treated it as dead, so a run owned by another user read as over and a

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@appchy/jarvis",
-  "version": "0.1.122",
+  "version": "0.1.123",
   "description": "Jarvis — local AI coding assistant CLI",
   "private": false,
   "type": "module",
@@ -63,10 +63,10 @@
     "@jarvis/errors": "1.0.0",
     "@jarvis/logger": "1.0.0",
     "@jarvis/rpc": "1.0.0",
-    "@jarvis/types": "1.0.0",
+    "@jarvis/vitest-config": "1.0.0",
     "@jarvis/typescript-config": "1.0.0",
     "@jarvis/ui": "0.1.0",
-    "@jarvis/vitest-config": "1.0.0"
+    "@jarvis/types": "1.0.0"
   },
   "scripts": {
     "dev": "tsx watch src/bin.ts start --foreground",