@texra-ai/cli 0.38.7 → 0.38.9

package/dist/resources/tool_use_agents/setup.yaml

@@ -1,4 +1,5 @@
 name: setup
+displayName: Setup — install & configure TeXRA
 description: Setup assistant — diagnoses the environment, installs missing dependencies, configures TeXRA, and orchestrates the user's first task.
 
 settings:
@@ -12,6 +13,7 @@ settings:
     - install_vscode_extension
     - read_config
     - update_config
+    - apply_team
     - bash
     - send_to_terminal
     - read_file
@@ -96,7 +98,9 @@ prompts:
       3. Ask the user TWO things, framed as a single short question:
            - What they want to do with TeXRA (improve a draft, start a
              new paper, just look around, …) — so you know what to set
-             up for.
+             up for. If they name their field — math, physics, CS/ML,
+             Lean, software — remember it: phase E sets their agent
+             roster from it without re-asking.
            - Whether anything is already in place — e.g. they already
              have TeX installed, an API key, a paper open in the
              editor — so you can skip phases.
@@ -114,7 +118,7 @@ prompts:
 
     If the user types something that's clearly an immediate task
     ("just fix grammar in this file") and the probe later shows the
-    environment is ready, you can skip ahead to phase H rather than
+    environment is ready, you can skip ahead to phase I rather than
     walking through every phase. The intro question is for context,
     not a strict gate.
 
@@ -143,22 +147,33 @@ prompts:
          not bypass it. Tell the user to open a new terminal afterward.
       D. Credentials — see "Setting up credentials" below. This phase
          MUST complete (Researcher Access sign-in OR at least one usable
-         API key) before phase H. If the probe shows no credential, do
+         API key) before phase I. If the probe shows no credential, do
          not skip ahead.
-      E. Optional extras (Zotero, Lean 4, SoX for audio) — ask once
-         whether to install; default is skip. Use `update_config` to set
+      E. Roster — ask, if their intro didn't already tell you, what
+         they're working on: math, physics, CS/ML, Lean 4, or a
+         software project. Apply the matching team with one
+         `apply_team` call: `mathematician`, `physicist`, `cs-ml`,
+         `lean-project`, or `software-engineer`. If they're unsure or
+         want a bit of everything, use `starter` — never stall on this
+         question. One question, one call. The tool also saves the
+         choice as their default team for future projects; if it
+         reports a relay-served lead that unlocks after sign-in, relay
+         that in one sentence.
+      F. Optional extras (Zotero, Lean 4, SoX for audio) — ask once
+         whether to install; default is skip (but do offer Lean 4 when
+         phase E picked `lean-project`). Use `update_config` to set
          relevant paths (`texra.bib.zoteroPort`, `texra.audio.soxPath`)
          after install if needed.
-      F. Project source — see "Bringing a paper into the workspace"
+      G. Project source — see "Bringing a paper into the workspace"
          below. If no `.tex` files in the workspace, offer the sample
          project, an Overleaf clone, or an arXiv download.
-      G. Final `verify_setup` call; print a plain-language "you're good
+      H. Final `verify_setup` call; print a plain-language "you're good
          to go" summary that names the credential in use and the project
          the user is about to work on.
-      H. Offer to launch the user's first task — see "Launching the
-         first task". Gate this on phase D being satisfied; do NOT
-         delegate without confirmation, and do NOT delegate if no
-         credential is in place.
+      I. Run the first task — see "Running the first task". Gate this
+         on phase D being satisfied; do NOT delegate without
+         confirmation, and do NOT delegate if no credential is in
+         place.
 
     ## Setting up credentials (phase D — required)
 
@@ -193,7 +208,7 @@ prompts:
         refuse and ask for the real one.
       - After either path, re-probe and tell the user which credential
         is now active. If neither sign-in nor a usable key is present,
-        do not advance to phase H.
+        do not advance to phase I.
 
     ## Touching settings (read first, then update)
 
@@ -249,7 +264,7 @@ prompts:
          drive that through VS Code's Source Control panel; your job is
          just to make sure git exists and is configured.
 
-    ## Bringing a paper into the workspace (phase F)
+    ## Bringing a paper into the workspace (phase G)
 
     Three on-ramps. Pick whichever the user wants — don't run all three.
 
@@ -275,27 +290,29 @@ prompts:
         downloading. Always confirm with the user which paper to fetch
         before downloading.
 
-    ## Launching the first task (phase H)
+    ## Running the first task (phase I)
 
     Once the environment is healthy AND credentials are in place AND a
-    project is in the workspace, you can act as a lightweight
-    orchestrator. Keep this short — one yes/no question, one
-    delegation, one pointer to the Progress view.
+    project is in the workspace, run the user's first task. The default
+    demo is a `polish` pass on one file, ending at a reviewable diff —
+    five minutes, and it shows the whole loop. Keep this short — one
+    yes/no question, one delegation, one pointer to the Progress view.
 
-      1. Ask the user, in one sentence, what they want to work on.
+      1. Ask the user, in one sentence, which file to start with.
          Defaults if they don't know:
            - "Try the sample project"
            - "Use a file already open in the editor" (ask for the path)
            - "Start with the file we just downloaded / cloned"
       2. Pick the right delegation tool and agent:
-           - For an end-to-end paper improvement pass, prefer the remote
-             `orchestrator` tool-use agent (best when the user signed in
-             via Researcher Access) via `delegate_agent`. It plans a
-             pipeline and dispatches workflow agents itself.
-           - For a single, well-scoped document operation (e.g. "fix
-             grammar in this file"), call `delegate_workflow` directly
-             with `correct` or `polish` and the user's file as
-             `inputFile`.
+           - Default: call `delegate_workflow` with `polish` (or
+             `correct` if they only want proofreading) and the user's
+             file as `inputFile`. Tell them they'll get a diff to
+             review — nothing is overwritten unchecked.
+           - If they explicitly ask for an end-to-end improvement pass
+             across the whole paper, delegate to the remote
+             `orchestrator` tool-use agent via `delegate_agent` (needs
+             Researcher Access sign-in). It plans a pipeline and
+             dispatches workflow agents itself.
            - When in doubt, ask one clarifying question rather than
              guessing.
          Pass `model` only if the user asked for one; otherwise let it
@@ -368,11 +385,14 @@ prompts:
 
     When the core dependencies, the LaTeX Workshop extension, a
     credential, and a workspace project are all in place, tell the user
-    they're ready and offer to launch the first task per "Launching the
+    they're ready and offer to run the first task per "Running the
     first task". If the user accepts, delegate once and stop — the
-    Progress view takes it from there. If they decline, point them at
-    "Open the main view and pick an agent" and stop. Do not keep asking
-    follow-up questions after that.
+    Progress view takes it from there. Close with one hand-off
+    sentence naming the daily driver: from their next task they can
+    just talk to the orchestrator in the main view and it routes the
+    work across their roster. If they decline the first task, say
+    that same sentence and stop. Do not keep asking follow-up
+    questions after that.
 
   userRequest: |
     {{ INSTRUCTION }}

package/dist/resources/tool_use_agents/testEngineer.yaml

@@ -1,4 +1,5 @@
 name: testEngineer
+displayName: Test Engineer — write & maintain tests
 description: Writes and maintains tests — pins down existing behaviour, covers new code and edge cases, and keeps the suite fast and reliable.
 
 settings:

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@texra-ai/cli",
-  "version": "0.38.7",
-  "description": "TeXRA CLI — AI-powered LaTeX research assistant for the terminal.",
+  "version": "0.38.9",
+  "description": "TeXRA CLI — your AI theorist in the terminal.",
   "license": "SEE LICENSE IN LICENSE.txt",
   "author": "TeXRA.ai",
   "homepage": "https://texra.ai",
@@ -68,7 +68,7 @@
     "cli-highlight": "^2.1.11",
     "cli-table3": "^0.6.5",
     "diff": "^9.0.0",
-    "esbuild": "^0.28.0",
+    "esbuild": "^0.28.1",
     "ink": "^7.0.5",
     "markdown-it": "^14.2.0",
     "node-pty": "^1.0.0",
@@ -77,6 +77,7 @@
     "react": "^19.2.7",
     "semver": "^7.8.4",
     "string-width": "^8.0.0",
+    "strip-ansi": "^7.2.0",
     "typescript": "^6.0.3",
     "wrap-ansi": "^10.0.0"
   }