ethos-cli 0.1.4 → 0.1.5

package/package.json

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

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

@@ -11,11 +11,11 @@ pass `--api-url` for local development or an explicitly requested environment.
 
 ## Flow
 
-Always keep CSV upload browser-first:
+Always keep CSV upload in the Codex in-app Browser:
 
-1. Open Ethos in the browser with the CSV upload deep link.
+1. Open Ethos in the in-app Browser with the CSV upload deep link.
 2. Immediately ask the user for ICP, buying signals, person targets, and max contacts while they upload.
-3. Poll the browser URL until the upload-complete URL appears.
+3. Poll that same in-app Browser tab until the upload-complete URL appears.
 4. Save the uploaded table id from that URL.
 5. Create the `people_sourcing` agent and Codex-created column with the CLI.
 6. Run the column for the FIRST 3 ROWS ONLY. Tell the user you're running for 3 rows to see if the results are good. If yes, the next step is to run on the whole table. If not, refine the agent based on their feedback so it finds the right people.
@@ -43,7 +43,7 @@ the user explicitly wants a non-browser setup.
 
 ## Open Browser Upload
 
-Open this URL in the browser:
+Open this URL in the Codex in-app Browser:
 
 ```sh
 APP_BASE_URL="https://ethos.hello-cluster.com"
@@ -53,7 +53,9 @@ if [ -n "${CODEX_THREAD_ID:-}" ]; then
 fi
 ```
 
-Run `open "$UPLOAD_URL"` and tell the user to upload the CSV there.
+Use the Browser plugin/in-app Browser to navigate to `$UPLOAD_URL` and tell
+the user to upload the CSV there. Do not use `open`, Chrome, Safari, or any
+external/default browser for this flow.
 
 After opening the upload modal, immediately ask:
 
@@ -61,7 +63,7 @@ After opening the upload modal, immediately ask:
 Please describe your ICP, any signals that would make them a good fit for your product or service, and where that data may live. You can keep typing while the CSV uploads.
 ```
 
-Then poll the browser URL every 2 seconds while the user uploads and answers.
+Then poll the in-app Browser URL every 2 seconds while the user uploads and answers.
 The ONLY upload-completion indicator is this URL shape:
 
 ```text
@@ -171,16 +173,15 @@ After the `source-people` command succeeds, bring the browser back to the table:
 "$APP_BASE_URL/tables/$TABLE_ID"
 ```
 
-The table UI should hide the upload return modal once the Codex-created column
-appears, then auto-scroll to that column.
-
-Then report the table URL, run id, and agent id. Keep the response concise and
-mention that the Codex-created column should appear and auto-scroll into view in
-Ethos.
+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.
 
 ## How to communicate with the user
 
-While you execute the flow, keep communication with the user simple and approachable at all times. Do not mention internal ethos concepts  unless explicitly necessary.
+While you execute the flow, keep communication simple and approachable. Avoid
+explaining UI behavior that should happen automatically when everything is
+working. Do not mention internal Ethos concepts unless explicitly necessary.
 
 For example, instead of 
 
@@ -195,4 +196,3 @@ If you need input from the user, make it very clear by bolding it and maybe ment
 E.g.:
 
 "**Next, please give me the following information** ..."
-