@whalent/agent 0.3.424 → 0.3.426
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 +47 -0
- package/dist/core.cjs +7 -7
- package/dist/index.cjs +1 -1
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -114,6 +114,53 @@ To specify a custom gateway:
|
|
|
114
114
|
whalent --token <YOUR_TOKEN> --gateway wss://your-server/gw/sdk/ws
|
|
115
115
|
```
|
|
116
116
|
|
|
117
|
+
## Android trial (0.3.426+)
|
|
118
|
+
|
|
119
|
+
Whalent Android 0.1.50 adds a native **Local agent** trial page: install the
|
|
120
|
+
Whalent APK, then download the selected ARM64 clients from that page. No second
|
|
121
|
+
APK or terminal is required. The APK owns the runtime and its foreground service;
|
|
122
|
+
connections report **Android**, independently of the Linux guest runtime.
|
|
123
|
+
|
|
124
|
+
For developer diagnostics, these commands also work inside DSHA's Ubuntu
|
|
125
|
+
terminal or a Termux PRoot Ubuntu environment with Node.js 24+:
|
|
126
|
+
|
|
127
|
+
```bash
|
|
128
|
+
npm install -g @whalent/agent@0.3.426 @openai/codex@0.154.0
|
|
129
|
+
whalent android doctor
|
|
130
|
+
whalent android start
|
|
131
|
+
```
|
|
132
|
+
|
|
133
|
+
`start` uses the normal Whalent login flow; `--token`, `--gateway` and `--machine`
|
|
134
|
+
remain available. Keep this command running in the device terminal. In Whalent's
|
|
135
|
+
machine management page choose this Android machine, configure credentials, and
|
|
136
|
+
create **Codex** and **DeepSeek Harness** agents with workspaces inside the
|
|
137
|
+
Ubuntu environment. Provider credentials and sessions continue to use the
|
|
138
|
+
existing per-agent isolation. This does not attach to or copy a DSHA Web UI
|
|
139
|
+
conversation.
|
|
140
|
+
|
|
141
|
+
DSHA's existing Harness plugin tree is reused (including its Android patches).
|
|
142
|
+
If auto-discovery fails, locate the **directory containing `node_modules` and
|
|
143
|
+
the `@deepseek-ai/dsh-app-boot` dependency**, then set
|
|
144
|
+
`WHALENT_DSH_RUNTIME_DIR` to that directory before running both commands.
|
|
145
|
+
For a fresh Ubuntu environment without Harness, install `@deepseek-ai/dsh`
|
|
146
|
+
there first; native Termux/Bionic may need additional upstream patches and is
|
|
147
|
+
not covered by the Ubuntu trial.
|
|
148
|
+
|
|
149
|
+
`doctor` sends a real `initialize` request to Codex `app-server` and to the
|
|
150
|
+
Whalent Harness bridge, using temporary provider homes. It does not call a
|
|
151
|
+
model or log in to Whalent. Use `doctor codex` or `doctor deepseek` to probe just one client.
|
|
152
|
+
Both `ready` fields must be true for the combined probe; exit code 1 means
|
|
153
|
+
one or both probes failed. Successful initialization is not a full task,
|
|
154
|
+
sandbox, PTY, history-import, or Android background-survival test.
|
|
155
|
+
|
|
156
|
+
The device's stable random identity is stored in
|
|
157
|
+
`~/.whalent-agent/android-device-id` (or the `WHALENT_HOME` base). Preserve it
|
|
158
|
+
across upgrades, and do not copy it into another phone's base image. It avoids
|
|
159
|
+
identical Ubuntu hostnames replacing each other's daemon connections.
|
|
160
|
+
`WHALENT_HOST_PLATFORM=android` is the equivalent device hint for an embedded
|
|
161
|
+
APK launcher; it is inherited by workers. Helper downloads still use the
|
|
162
|
+
actual runtime OS/ABI, so a phone running Ubuntu selects Linux ARM64 helpers.
|
|
163
|
+
|
|
117
164
|
## MCP Gateway Routing
|
|
118
165
|
|
|
119
166
|
When starting the legacy `whalent mcp` subcommand directly, pass the gateway
|