ethos-cli 0.7.15 → 0.7.16

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ethos-cli",
-  "version": "0.7.15",
+  "version": "0.7.16",
   "description": "Commander-based CLI for Ethos table operations",
   "homepage": "https://github.com/cluster-software/ethos#readme",
   "repository": {

package/skills/find-people-at-companies.md

@@ -313,6 +313,9 @@ Do not assume that reusing the same agent id writes into the same column. A
 later `source-people` command without `--column-id` creates a new column.
 
 Only run the agent for 3 rows on the first run, so the user can give feedback.
+Tell the user this is a test run on the first 3 companies, that results will
+appear in a new people-finder column on the uploaded table, and that they can
+review the results before running it across the rest of the table.
 
 After you queue the run on the 3 rows, tell the user to review the results when
 done and decide whether you should:
@@ -324,7 +327,7 @@ done and decide whether you should:
 
 - If they queue a larger run after the first 3 rows look good, let them know it
   can take a few minutes to complete, and that they can navigate away and come
-  back later.
+  back later. Results continue filling into the same people-finder column.
 - IMPORTANT: If they were fine with the first agent you made, run the existing
   column. Do not create a new column.
 - Prefer the returned `response.same_column_empty_run_command` to run only rows
@@ -358,9 +361,10 @@ explicitly requested environment. In Codex, bring the in-app Browser back to
 that table URL. In Claude Code, Cursor, or another non-Codex shell-based client,
 open that table URL with `open` first, and only use MCP browser tools, Chrome
 connectors, in-app browser plugins, or other browser automation connectors if
-`open` fails. Then tell the user the agent is running on the first 3 rows. Do
-not surface agent ids, run ids, table ids, or similar internal ids unless the
-user asks for them or you are actively debugging.
+`open` fails. Then tell the user the agent is running on the first 3 rows and
+that results will appear in a new people-finder column on this table. Do not
+surface agent ids, run ids, table ids, or similar internal ids unless the user
+asks for them or you are actively debugging.
 
 ## How to communicate with the user
 

package/skills/find-people.md

@@ -135,7 +135,8 @@ Always invite adjustment before or while polling:
 
 ```text
 If any of that looks off, tell me what to change and I can interrupt or refine
-the search. I’ll poll this one now and send the table link when it’s ready.
+the search. I’ll poll this one now. Ethos is creating a people table where you
+can review, edit, and filter the results; I’ll send the link when it’s ready.
 ```
 
 When the search succeeds, lead with the result count and table link. If
@@ -161,6 +162,14 @@ interactive agent work, prefer repeated `get` calls every 10-20 seconds over a
 long-running `wait` command: `wait --json` is silent until the job reaches a
 terminal state, which makes the agent blind while the job is running.
 
+As soon as a poll returns `profileCount` and/or `companyCount`, surface the
+scope clearly before continuing to wait, for example:
+
+```text
+Matched 842 people across 210 companies. Ethos is creating a people table with
+the results now.
+```
+
 The job reaches one of these terminal statuses:
 
 - `succeeded`: linked company and people tables were created. Open