@renxqoo/renx-code 0.0.10 → 0.0.13
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 +31 -157
- package/bin/renx.exe +0 -0
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -1,9 +1,20 @@
|
|
|
1
|
-
# Renx
|
|
1
|
+
# Renx Code
|
|
2
2
|
|
|
3
|
-
`renx` is a terminal AI coding assistant
|
|
3
|
+
`renx` is a terminal AI coding assistant.
|
|
4
4
|
|
|
5
|
-
-
|
|
6
|
-
-
|
|
5
|
+
- Package: `@renxqoo/renx-code`
|
|
6
|
+
- Command: `renx`
|
|
7
|
+
|
|
8
|
+
## Features
|
|
9
|
+
|
|
10
|
+
`renx` can help you:
|
|
11
|
+
|
|
12
|
+
- read and explain a codebase
|
|
13
|
+
- edit files directly in your project
|
|
14
|
+
- fix build errors and runtime errors
|
|
15
|
+
- generate code, tests, and scripts
|
|
16
|
+
- inspect logs and terminal output
|
|
17
|
+
- work inside the current directory as the active workspace
|
|
7
18
|
|
|
8
19
|
## Install
|
|
9
20
|
|
|
@@ -11,81 +22,33 @@ Requirements:
|
|
|
11
22
|
|
|
12
23
|
- Node.js `20+`
|
|
13
24
|
|
|
14
|
-
Install
|
|
25
|
+
Install:
|
|
15
26
|
|
|
16
27
|
```bash
|
|
17
28
|
npm i -g @renxqoo/renx-code --registry=https://registry.npmjs.org
|
|
18
29
|
```
|
|
19
30
|
|
|
20
|
-
|
|
31
|
+
Run:
|
|
21
32
|
|
|
22
33
|
```bash
|
|
23
34
|
renx
|
|
24
35
|
```
|
|
25
36
|
|
|
26
|
-
Published npm packages include a prebuilt executable, so end users do not need to install Bun.
|
|
27
|
-
|
|
28
|
-
## Quick Start
|
|
29
|
-
|
|
30
|
-
Open a project directory and run:
|
|
31
|
-
|
|
32
|
-
```bash
|
|
33
|
-
cd your-project
|
|
34
|
-
renx
|
|
35
|
-
```
|
|
36
|
-
|
|
37
|
-
`renx` uses the current terminal directory as the workspace by default.
|
|
38
|
-
|
|
39
|
-
Common things you can ask it to do:
|
|
40
|
-
|
|
41
|
-
- explain a codebase or a single file
|
|
42
|
-
- fix build or runtime errors
|
|
43
|
-
- modify files directly
|
|
44
|
-
- help write features, tests, and scripts
|
|
45
|
-
- investigate logs and terminal output
|
|
46
|
-
|
|
47
|
-
Built-in commands:
|
|
48
|
-
|
|
49
|
-
- `/help`
|
|
50
|
-
- `/clear`
|
|
51
|
-
- `/exit`
|
|
52
|
-
|
|
53
|
-
Keyboard shortcuts:
|
|
54
|
-
|
|
55
|
-
- `Esc`: stop the current response, or clear the current input
|
|
56
|
-
- `Ctrl + L`: clear the current conversation
|
|
57
|
-
|
|
58
37
|
## Configuration
|
|
59
38
|
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
1. process environment variables and `.env` / `.env.development`
|
|
63
|
-
2. project config: `<workspace>/.renx/config.json`
|
|
64
|
-
3. global config: `RENX_HOME/config.json`
|
|
65
|
-
4. built-in defaults
|
|
66
|
-
|
|
67
|
-
Default user data locations:
|
|
39
|
+
Config locations:
|
|
68
40
|
|
|
69
|
-
-
|
|
70
|
-
-
|
|
71
|
-
- `RENX_HOME/logs/`
|
|
72
|
-
- `RENX_HOME/storage/`
|
|
73
|
-
- `RENX_HOME/task/`
|
|
74
|
-
- `RENX_HOME/data.db`
|
|
75
|
-
|
|
76
|
-
Project config example:
|
|
77
|
-
|
|
78
|
-
```text
|
|
79
|
-
your-project/.renx/config.json
|
|
80
|
-
```
|
|
41
|
+
- global: `~/.renx/config.json`
|
|
42
|
+
- project: `<your-project>/.renx/config.json`
|
|
81
43
|
|
|
82
|
-
|
|
44
|
+
Priority:
|
|
83
45
|
|
|
84
|
-
|
|
85
|
-
|
|
86
|
-
|
|
46
|
+
1. environment variables
|
|
47
|
+
2. project config
|
|
48
|
+
3. global config
|
|
49
|
+
4. defaults
|
|
87
50
|
|
|
88
|
-
|
|
51
|
+
Example:
|
|
89
52
|
|
|
90
53
|
```json
|
|
91
54
|
{
|
|
@@ -94,95 +57,18 @@ Global config example:
|
|
|
94
57
|
"maxSteps": 10000,
|
|
95
58
|
"confirmationMode": "manual"
|
|
96
59
|
},
|
|
97
|
-
"log": {
|
|
98
|
-
"level": "INFO",
|
|
99
|
-
"format": "pretty",
|
|
100
|
-
"console": true,
|
|
101
|
-
"file": false
|
|
102
|
-
},
|
|
103
|
-
"storage": {
|
|
104
|
-
"fileHistory": {
|
|
105
|
-
"enabled": true,
|
|
106
|
-
"maxPerFile": 20,
|
|
107
|
-
"maxAgeDays": 14,
|
|
108
|
-
"maxTotalMb": 500
|
|
109
|
-
}
|
|
110
|
-
}
|
|
111
|
-
}
|
|
112
|
-
```
|
|
113
|
-
|
|
114
|
-
## Custom Model Config
|
|
115
|
-
|
|
116
|
-
You can define your own model in global or project `config.json` and then point `agent.defaultModel` to it.
|
|
117
|
-
|
|
118
|
-
Example:
|
|
119
|
-
|
|
120
|
-
```json
|
|
121
|
-
{
|
|
122
|
-
"agent": {
|
|
123
|
-
"defaultModel": "my-openai-compatible"
|
|
124
|
-
},
|
|
125
60
|
"models": {
|
|
126
|
-
"my-
|
|
61
|
+
"my-model": {
|
|
127
62
|
"provider": "openai",
|
|
128
|
-
"name": "My
|
|
129
|
-
"baseURL": "https://
|
|
130
|
-
"
|
|
131
|
-
"
|
|
132
|
-
"envBaseURL": "MY_API_BASE",
|
|
133
|
-
"model": "my-model",
|
|
134
|
-
"max_tokens": 8000,
|
|
135
|
-
"LLMMAX_TOKENS": 128000,
|
|
136
|
-
"features": ["streaming", "function-calling"]
|
|
137
|
-
},
|
|
138
|
-
"gpt-5.4": {
|
|
139
|
-
"baseURL": "https://my-proxy.example.com/v1"
|
|
63
|
+
"name": "My Model",
|
|
64
|
+
"baseURL": "https://api.openai.com/v1",
|
|
65
|
+
"envApiKey": "OPENAI_API_KEY",
|
|
66
|
+
"model": "gpt-5.4"
|
|
140
67
|
}
|
|
141
68
|
}
|
|
142
69
|
}
|
|
143
70
|
```
|
|
144
71
|
|
|
145
|
-
This supports both:
|
|
146
|
-
|
|
147
|
-
- adding a completely new model
|
|
148
|
-
- overriding part of a built-in model, such as `baseURL`
|
|
149
|
-
|
|
150
|
-
## Environment Variables
|
|
151
|
-
|
|
152
|
-
Runtime:
|
|
153
|
-
|
|
154
|
-
- `RENX_HOME`
|
|
155
|
-
- `AGENT_MODEL`
|
|
156
|
-
- `AGENT_MAX_STEPS`
|
|
157
|
-
- `AGENT_MAX_RETRY_COUNT`
|
|
158
|
-
- `AGENT_TOOL_CONFIRMATION_MODE`
|
|
159
|
-
- `AGENT_CONVERSATION_ID`
|
|
160
|
-
- `AGENT_SESSION_ID`
|
|
161
|
-
|
|
162
|
-
Logging:
|
|
163
|
-
|
|
164
|
-
- `AGENT_LOG_LEVEL`
|
|
165
|
-
- `AGENT_LOG_FORMAT`
|
|
166
|
-
- `AGENT_LOG_CONSOLE`
|
|
167
|
-
- `AGENT_LOG_FILE_ENABLED`
|
|
168
|
-
|
|
169
|
-
File history:
|
|
170
|
-
|
|
171
|
-
- `AGENT_FILE_HISTORY_ENABLED`
|
|
172
|
-
- `AGENT_FILE_HISTORY_MAX_PER_FILE`
|
|
173
|
-
- `AGENT_FILE_HISTORY_MAX_AGE_DAYS`
|
|
174
|
-
- `AGENT_FILE_HISTORY_MAX_TOTAL_MB`
|
|
175
|
-
|
|
176
|
-
Custom models:
|
|
177
|
-
|
|
178
|
-
- `RENX_CUSTOM_MODELS_JSON`
|
|
179
|
-
|
|
180
|
-
Provider API keys are passed through their own environment variables, for example:
|
|
181
|
-
|
|
182
|
-
- `OPENAI_API_KEY`
|
|
183
|
-
- `GLM_API_KEY`
|
|
184
|
-
- `QWEN_API_KEY`
|
|
185
|
-
|
|
186
72
|
## Publish
|
|
187
73
|
|
|
188
74
|
Useful local release commands:
|
|
@@ -200,15 +86,3 @@ Version rules:
|
|
|
200
86
|
- `publish:patch`: small fix, `0.0.1`
|
|
201
87
|
- `publish:minor`: new feature, `0.1.0`
|
|
202
88
|
- `publish:major`: breaking change or refactor, `1.0.0`
|
|
203
|
-
|
|
204
|
-
## Maintainers
|
|
205
|
-
|
|
206
|
-
Maintainers need Bun to build and publish the precompiled binary package.
|
|
207
|
-
|
|
208
|
-
Install Bun:
|
|
209
|
-
|
|
210
|
-
```bash
|
|
211
|
-
powershell -c "irm bun.sh/install.ps1 | iex"
|
|
212
|
-
```
|
|
213
|
-
|
|
214
|
-
Current release builds the executable for the platform used during publishing. For example, publishing on Windows x64 produces a Windows x64 npm package.
|
package/bin/renx.exe
CHANGED
|
Binary file
|
package/package.json
CHANGED