@texra-ai/cli 0.38.1 → 0.38.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -21,21 +21,28 @@
21
21
  > [Buy Me a Coffee](https://buymeacoffee.com/texra.ai) to keep the program
22
22
  > open for everyone.
23
23
 
24
- **TeXRA is a multi-agent research assistant for theorists (Physics, Math, CS, Engineering, etc.)— in VS Code and the
25
- terminal.** Instead of chatting with a single model, you direct an
24
+ **TeXRA is a multi-agent research assistant for theorists (Physics, Math, CS,
25
+ Engineering, etc.).** Instead of chatting with a single model, you direct an
26
26
  **Orchestrator** that delegates to a team of specialists—researchers,
27
27
  numericists, reviewers, formalizers, LaTeX fixers, presenters—each with their
28
28
  own tools, prompts, and model. The result is a coordinated lab that drafts,
29
29
  reviews, computes, and formalizes rigorous scientific work alongside its LaTeX,
30
30
  code, figures, and PRs.
31
31
 
32
- TeXRA runs as a **VS Code extension** and as a **terminal CLI**
33
- (`@texra-ai/cli`) that share the same agents and sign-in — see
34
- [Use TeXRA from the terminal](#use-texra-from-the-terminal) below.
32
+ ### One assistant, two surfaces
35
33
 
36
- See [texra.ai](https://texra.ai) or the
37
- [full documentation](https://texra.ai/guide/) for tutorials, agent recipes, and
38
- a web-based launch page.
34
+ The same agents, account, and model providers are available wherever you work:
35
+
36
+ | | **VS Code extension** | **Terminal CLI** |
37
+ | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- |
38
+ | Best for | Interactive writing, side-by-side diffs, figure previews | Scripts, CI, remote/headless machines, the keyboard-first |
39
+ | Install | [Marketplace](https://marketplace.visualstudio.com/items?itemName=texra-ai.texra) / [Open VSX](https://open-vsx.org/extension/texra-ai/texra) | `npm install -g @texra-ai/cli` |
40
+ | Drive it with | Sidebar chat + the **progress board** | `texra chat` (TUI) and `texra run` (headless) |
41
+
42
+ Pick whichever fits the moment—both run the same teams on the same `.tex`
43
+ projects. The deeper walkthroughs live at
44
+ [texra.ai](https://texra.ai) and the
45
+ [full documentation](https://texra.ai/guide/).
39
46
 
40
47
  ## Why TeXRA
41
48
 
@@ -47,8 +54,9 @@ a web-based launch page.
47
54
  sessions.
48
55
  - **Curated team presets** – switch to **Physicist**, **Mathematician**,
49
56
  **Computer Scientist (ML)**, or **Lean Project** in one click from the
50
- Multi-Agent settings tab. Each preset is a preconfigured roster of workflow
51
- and tool-use agents tuned for that discipline; you can also save your own.
57
+ Multi-Agent settings tab, or with `texra multi-agent run <preset>` in the
58
+ terminal. Each preset is a preconfigured roster of workflow and tool-use
59
+ agents tuned for that discipline; you can also save your own.
52
60
  - **A full cast of specialists** – locally bundled tool-use agents include
53
61
  `research`, `numerics`, `review`, `presenter`, `latexFixer`, `latexDiff`,
54
62
  `creator`, `lean`, `chat`, and the **Setup Wizard** (`setup`); workflow
@@ -62,13 +70,13 @@ a web-based launch page.
62
70
  GitHub PR subscriptions, and can delegate reasoning turns to the Codex
63
71
  CLI—each tool call gated by per-stream approval (with an optional YOLO
64
72
  bypass).
65
- - **Live, persistent runs** – the **progress board** streams reasoning, tool
66
- calls, sub-agent file diffs, and per-run token usage and cost for active
67
- and recently completed runs in your workspace. Saved task state can be
68
- reopened later via **Show Agent Execution History**, tool-use agents can
69
- be resumed via **Resume Tool-Use Agent**, and **Pack Output into History
70
- Folder** archives a finished run's outputs into the workspace's `History/`
71
- directory.
73
+ - **Live, persistent runs** – watch reasoning, tool calls, sub-agent file
74
+ diffs, and per-run token usage and cost stream in real time—on the VS Code
75
+ **progress board** or in the `texra chat` terminal UI. Each surface saves its
76
+ runs so you can reopen and resume them later: via **Show Agent Execution
77
+ History** and **Resume Tool-Use Agent** in VS Code, or `texra history` and
78
+ `texra resume <id>` in the terminal. Finished outputs can be archived into
79
+ the workspace's `History/` directory.
72
80
  - **Odyssey mode (experimental)** – let a tool-use agent run a long task to
73
81
  completion on its own. A configurable budget auto-pauses the run for your
74
82
  approval before going further, and a dedicated panel shows progress so
@@ -90,13 +98,19 @@ a web-based launch page.
90
98
  | **Computer Scientist (ML)** | Algorithm design, experiments and ablations, literature search, critical review, and reproducibility. |
91
99
  | **Lean Project** | Lean 4 projects—theorem search, tactic simplification, and blueprint-driven formalization. |
92
100
 
93
- Switch teams from the Multi-Agent tab in Settings, or build your own roster of
94
- workflow and tool-use agents. Teams that include remote specialists (e.g. the
101
+ Switch teams from the Multi-Agent tab in Settings (or `texra multi-agent` in
102
+ the terminal), or build your own roster of workflow and tool-use agents. Teams
103
+ that include remote specialists (e.g. the
95
104
  Orchestrator, `search`, `simplifier`) require sign-in or your own API keys
96
105
  configured for the providers those agents use.
97
106
 
98
107
  ## Quick Start
99
108
 
109
+ Both surfaces share the same sign-in and agents, so set up whichever you'll
110
+ use—or both.
111
+
112
+ ### In VS Code
113
+
100
114
  1. Install the extension from the [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=texra-ai.texra)
101
115
  or [Open VSX](https://open-vsx.org/extension/texra-ai/texra).
102
116
  2. Launch the **Setup Wizard**. Pick whichever is easiest:
@@ -127,41 +141,38 @@ New here? Use the **Create Sample Project** button in the Getting Started
127
141
  banner (also available as `TeXRA: Create Sample Project` from the command
128
142
  palette) to spin up a fully configured workspace.
129
143
 
130
- ## Use TeXRA from the terminal
144
+ ### In the terminal
131
145
 
132
- TeXRA also ships as a standalone CLI for running the same agents on your `.tex`
133
- projects without an editor — useful for scripts, CI, and remote machines.
146
+ Run the same agents on your `.tex` projects without an editor—ideal for
147
+ scripts, CI, and remote machines.
134
148
 
135
149
  ```sh
136
150
  npm install -g @texra-ai/cli # requires Node.js >= 22
137
- texra --help
138
- ```
139
-
140
- Authenticate the same way as the extension — sign in for the Researcher Access
141
- Program, or use your own provider keys (environment or a workspace `.env`, same
142
- `<PROVIDER>_API_KEY` convention as [Configuring Models](#configuring-models)
143
- below):
144
151
 
145
- ```sh
146
- texra login # included access; or set <PROVIDER>_API_KEY and pass --api-mode personal
152
+ texra login # Researcher Access sign-in; or set <PROVIDER>_API_KEY and use --api-mode personal
147
153
  texra doctor # verify environment, sign-in, models, and LaTeX tooling
148
154
  ```
149
155
 
150
- Run a workflow agent, or start an interactive tool-use session:
156
+ Then drive a whole research team from the prompt:
151
157
 
152
158
  ```sh
159
+ texra # interactive launcher: pick a chat, team, or run to resume
160
+ texra chat # interactive tool-use session (Orchestrator and specialists)
153
161
  texra run polish --input paper.tex --output paper.polished.tex --print
154
- texra chat
155
162
  ```
156
163
 
157
- Use `--output-format json|ndjson` for scriptable output, and `texra history` to
158
- inspect or resume stored runs. See the
164
+ The CLI exposes the full toolkit—`texra agents`, `models`, `tools`, and
165
+ `multi-agent` to inspect and launch teams; `texra history` and `texra resume`
166
+ to revisit or re-run past work; `texra init` to drop a project `.texra/config.json`.
167
+ For automation, every headless command takes `--output-format json|ndjson` and
168
+ `--approval-policy never|ask|yolo`. Run `texra --help` or see the
159
169
  [documentation](https://texra.ai/guide/) for the full command reference.
160
170
 
161
171
  ## Requirements
162
172
 
163
- - **VS Code** 1.105+ (also runs in compatible editors such as Cursor,
164
- Windsurf, and Google Antigravity)
173
+ - **VS Code** 1.105+ for the extension (also runs in compatible editors such
174
+ as Cursor, Windsurf, and Google Antigravity), **or Node.js 22+** for the
175
+ terminal CLI
165
176
  - **LaTeX distribution** (TeX Live, MiKTeX, or MacTeX) for compilation and
166
177
  related tooling
167
178
  - **Perl** (required by `latexindent` and `latexdiff`)
@@ -173,10 +184,13 @@ The Setup Wizard checks for and helps install most of the above for you.
173
184
 
174
185
  ## Configuring Models
175
186
 
176
- Sign in through the Profile view to use the Researcher Access Program (which
177
- also unlocks the hosted Orchestrator and remote specialists), or store your
178
- own API keys via the **`TeXRA: Set API Key`** command (kept in VS Code's
179
- encrypted SecretStorage), or place them in a workspace `.env` file:
187
+ Sign in to the Researcher Access Program—via the Profile view in VS Code or
188
+ `texra login` in the terminal—to use the hosted Orchestrator and remote
189
+ specialists. To bring your own keys instead, the extension reads them from the
190
+ **`TeXRA: Set API Key`** command (stored in VS Code's encrypted SecretStorage)
191
+ or a workspace `.env` file it loads automatically; the CLI reads the same
192
+ `<PROVIDER>_API_KEY` variables from your environment when run with
193
+ `--api-mode personal`:
180
194
 
181
195
  ```env
182
196
  OPENAI_API_KEY=your_openai_key_here
@@ -189,7 +203,7 @@ OPENROUTER_API_KEY=your_openrouter_key_here
189
203
 
190
204
  Other supported providers follow the same `<PROVIDER>_API_KEY` convention:
191
205
  `MOONSHOT_API_KEY`, `DASHSCOPE_API_KEY` (Qwen), `MINIMAX_API_KEY`,
192
- `GLM_API_KEY`. TeXRA loads the `.env` file automatically at startup. Each
206
+ `GLM_API_KEY`. Each
193
207
  agent in a team can use a different model, so you can pair a flagship reasoner
194
208
  for the orchestrator with cheaper, faster models for routine sub-tasks. See
195
209
  the [installation guide](https://texra.ai/guide/installation.html) and the
@@ -201,8 +215,10 @@ Configure agents, prompts, models, and reliability policy in VS Code settings
201
215
  or the unified Settings view (Memory, History, Models, Agents, Multi-Agent,
202
216
  Tools, Git, LaTeX tabs). The Multi-Agent tab covers team presets, parallel
203
217
  tool-call limits, compaction thresholds, retry/backoff, and the orchestrator
204
- kill toggle. Power users can define new workflow or tool-use agents in YAML
205
- or register new model handlers.
218
+ kill toggle. In the terminal, `texra init` writes a project
219
+ `.texra/config.json` with the same knobs, and any setting can be overridden
220
+ per run with a command-line flag. Power users on either surface can define new
221
+ workflow or tool-use agents in YAML or register new model handlers.
206
222
 
207
223
  ## Support & Feedback
208
224