laohuang 0.5.1 → 0.7.0
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 +13 -0
- package/dist/bin.js +4550 -2132
- package/dist/bin.js.map +4 -4
- package/package.json +5 -5
package/README.md
CHANGED
|
@@ -4,6 +4,8 @@ A minimal coding-agent CLI for local software work.
|
|
|
4
4
|
|
|
5
5
|
## Install
|
|
6
6
|
|
|
7
|
+
Requires Node.js >=22.19.0.
|
|
8
|
+
|
|
7
9
|
```bash
|
|
8
10
|
npm install -g laohuang
|
|
9
11
|
```
|
|
@@ -21,5 +23,16 @@ Run `laohuang` in a project directory to start an interactive session. The CLI
|
|
|
21
23
|
loads local project instructions, uses saved provider profiles, and keeps file
|
|
22
24
|
and shell tool execution rooted in the current project.
|
|
23
25
|
|
|
26
|
+
Model providers come from the installed pi-ai API-key catalog. In pi-ai 0.83.0
|
|
27
|
+
the product exposes 35 available API-key providers, excluding Amazon Bedrock,
|
|
28
|
+
Google Vertex, OAuth-only providers, and OpenAI Codex. Use `/providers` to see
|
|
29
|
+
available, configured, and verified status independently.
|
|
30
|
+
|
|
31
|
+
`/login <provider>` stores API-key credentials, `/logout <provider>` removes
|
|
32
|
+
them, `/model <provider> <model>` switches the session, and `/apikey` remains a
|
|
33
|
+
compatibility alias. `verified` means an explicitly authorized live native
|
|
34
|
+
tool-call/tool-result E2E was recorded; no providers are checked in as verified
|
|
35
|
+
by default.
|
|
36
|
+
|
|
24
37
|
See the repository README for development and architecture details:
|
|
25
38
|
https://github.com/hxr223/laoHuangCode#readme
|