local-commander-agent 0.3.47 → 0.3.49
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/CHANGELOG.md +218 -207
- package/README.md +216 -216
- package/bin/command-path.mjs +223 -223
- package/bin/localcommander.mjs +872 -872
- package/bin/monitor-agents.mjs +162 -162
- package/bin/monitor-context.d.mts +7 -7
- package/bin/monitor-context.mjs +65 -65
- package/bin/monitor-mcp.mjs +136 -136
- package/bin/monitor-savings.d.mts +20 -20
- package/bin/monitor-savings.mjs +71 -71
- package/bin/monitor.mjs +530 -530
- package/bin/network-package.mjs +38 -38
- package/bin/posix.mjs +84 -84
- package/package.json +57 -57
- package/runtime/JobHost.exe +0 -0
- package/runtime/LocalCommanderAgent.exe +0 -0
- package/runtime/OwnerBridge.exe +0 -0
- package/runtime/agent.mjs +35 -6
package/CHANGELOG.md
CHANGED
|
@@ -1,207 +1,218 @@
|
|
|
1
|
-
# Change history
|
|
2
|
-
|
|
3
|
-
## 0.3.
|
|
4
|
-
|
|
5
|
-
-
|
|
6
|
-
-
|
|
7
|
-
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
-
|
|
19
|
-
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
-
|
|
31
|
-
-
|
|
32
|
-
- Includes everything in 0.3.
|
|
33
|
-
|
|
34
|
-
## 0.3.
|
|
35
|
-
|
|
36
|
-
-
|
|
37
|
-
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
-
|
|
42
|
-
- Internal changes that do not change how the agent works on Windows.
|
|
43
|
-
- Includes everything in 0.3.
|
|
44
|
-
|
|
45
|
-
## 0.3.
|
|
46
|
-
|
|
47
|
-
- Fix:
|
|
48
|
-
- Fix:
|
|
49
|
-
-
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
-
|
|
54
|
-
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
-
|
|
60
|
-
- Includes everything in 0.3.
|
|
61
|
-
|
|
62
|
-
## 0.3.
|
|
63
|
-
|
|
64
|
-
-
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
|
|
70
|
-
-
|
|
71
|
-
|
|
72
|
-
|
|
73
|
-
|
|
74
|
-
|
|
75
|
-
-
|
|
76
|
-
|
|
77
|
-
|
|
78
|
-
|
|
79
|
-
-
|
|
80
|
-
-
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
|
|
84
|
-
|
|
85
|
-
-
|
|
86
|
-
|
|
87
|
-
|
|
88
|
-
|
|
89
|
-
|
|
90
|
-
-
|
|
91
|
-
|
|
92
|
-
|
|
93
|
-
|
|
94
|
-
|
|
95
|
-
- Fix: when the agent
|
|
96
|
-
- Includes everything in 0.3.
|
|
97
|
-
|
|
98
|
-
## 0.3.
|
|
99
|
-
|
|
100
|
-
-
|
|
101
|
-
-
|
|
102
|
-
|
|
103
|
-
|
|
104
|
-
|
|
105
|
-
|
|
106
|
-
|
|
107
|
-
-
|
|
108
|
-
|
|
109
|
-
|
|
110
|
-
|
|
111
|
-
|
|
112
|
-
|
|
113
|
-
-
|
|
114
|
-
-
|
|
115
|
-
|
|
116
|
-
|
|
117
|
-
|
|
118
|
-
|
|
119
|
-
-
|
|
120
|
-
-
|
|
121
|
-
|
|
122
|
-
## 0.3.
|
|
123
|
-
|
|
124
|
-
-
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
|
|
128
|
-
-
|
|
129
|
-
|
|
130
|
-
|
|
131
|
-
|
|
132
|
-
|
|
133
|
-
|
|
134
|
-
|
|
135
|
-
|
|
136
|
-
|
|
137
|
-
|
|
138
|
-
|
|
139
|
-
|
|
140
|
-
|
|
141
|
-
-
|
|
142
|
-
|
|
143
|
-
|
|
144
|
-
|
|
145
|
-
|
|
146
|
-
|
|
147
|
-
|
|
148
|
-
|
|
149
|
-
|
|
150
|
-
|
|
151
|
-
|
|
152
|
-
|
|
153
|
-
|
|
154
|
-
|
|
155
|
-
|
|
156
|
-
|
|
157
|
-
|
|
158
|
-
|
|
159
|
-
|
|
160
|
-
|
|
161
|
-
|
|
162
|
-
|
|
163
|
-
|
|
164
|
-
|
|
165
|
-
|
|
166
|
-
|
|
167
|
-
|
|
168
|
-
-
|
|
169
|
-
|
|
170
|
-
|
|
171
|
-
|
|
172
|
-
|
|
173
|
-
-
|
|
174
|
-
-
|
|
175
|
-
|
|
176
|
-
|
|
177
|
-
|
|
178
|
-
|
|
179
|
-
-
|
|
180
|
-
-
|
|
181
|
-
|
|
182
|
-
|
|
183
|
-
|
|
184
|
-
|
|
185
|
-
|
|
186
|
-
|
|
187
|
-
|
|
188
|
-
-
|
|
189
|
-
|
|
190
|
-
-
|
|
191
|
-
-
|
|
192
|
-
|
|
193
|
-
|
|
194
|
-
|
|
195
|
-
|
|
196
|
-
|
|
197
|
-
|
|
198
|
-
-
|
|
199
|
-
-
|
|
200
|
-
-
|
|
201
|
-
|
|
202
|
-
|
|
203
|
-
|
|
204
|
-
|
|
205
|
-
|
|
206
|
-
|
|
207
|
-
|
|
1
|
+
# Change history
|
|
2
|
+
|
|
3
|
+
## 0.3.49 - 2026-10-23
|
|
4
|
+
|
|
5
|
+
- Commands without an explicit working folder no longer block file work across the approved drive. Specify cwd when folder serialization is needed.
|
|
6
|
+
- Work held by another task in the same folder now returns RESOURCE_LOCKED after 20 seconds instead of disappearing behind a relay timeout. Nothing ran; retry after the other task finishes.
|
|
7
|
+
- Includes everything in 0.3.48.
|
|
8
|
+
|
|
9
|
+
## 0.3.48 - 2026-10-22
|
|
10
|
+
|
|
11
|
+
- Fixed: after the screenshot setting was switched (or screenshots were enabled for testing), the agent could not restart or update and stopped with STORE_DIRECTORY_UNKNOWN. Restarts and updates work again with either setting.
|
|
12
|
+
- Includes everything in 0.3.47.
|
|
13
|
+
|
|
14
|
+
## 0.3.47 - 2026-10-22
|
|
15
|
+
|
|
16
|
+
- New: screenshots on Linux. Where the screenshot tool is available to your account and the computer has Full Access, it now also works on a Linux desktop (Wayland through the desktop portal or grim, X11 through xwd, import or maim). When capture is not possible the client gets a clear reason, such as no desktop session or no capture tool.
|
|
17
|
+
- New: you can turn screenshots off for this computer. Run `localcommander screenshot off` on Windows, or `npx local-commander-agent screenshot off` on macOS and Linux; `screenshot on` turns them back on and `screenshot status` shows the current setting. No restart is needed.
|
|
18
|
+
- The cabinet now shows whether each computer has Full Access or selected folders only.
|
|
19
|
+
- Includes everything in 0.3.46.
|
|
20
|
+
|
|
21
|
+
## 0.3.46 - 2026-10-22
|
|
22
|
+
|
|
23
|
+
- Simpler setup on macOS and Linux: the approval page opens in your browser by itself, and on a Mac access is one click in a window (Full Access, or Choose Folder). Linux asks one question in the terminal: press Enter for Full Access or type a folder.
|
|
24
|
+
- Fixed: on macOS, updates keep access to the agent's key in the Keychain.
|
|
25
|
+
- Includes everything in 0.3.45.
|
|
26
|
+
|
|
27
|
+
## 0.3.45 - 2026-10-22
|
|
28
|
+
|
|
29
|
+
- New: macOS 14 or later on Apple Silicon, and Linux x64 or arm64 with a systemd user session. Run the same `npx local-commander-agent@latest` in Terminal; npm downloads only the runtime for your computer. Setup pairs the computer, asks what may be used in the terminal, and runs the agent as a background service that starts when you sign in.
|
|
30
|
+
- Fixed: a computer that lost its connection without noticing (after sleep, a network change or a server restart) now reconnects within about three minutes instead of staying offline.
|
|
31
|
+
- Fixed: a request that never reached a sleeping computer no longer keeps one of its execution slots busy; the computer frees it when it reconnects.
|
|
32
|
+
- Includes everything in 0.3.44.
|
|
33
|
+
|
|
34
|
+
## 0.3.44 - 2026-10-22
|
|
35
|
+
|
|
36
|
+
- New: when you set up a computer, the window that asks what may be used now shows the Local Commander account the computer joined. Someone helping you can approve your computer from their own phone with the code you read to them. Continue only if you know that account; Cancel shares nothing.
|
|
37
|
+
- Includes everything in 0.3.43.
|
|
38
|
+
|
|
39
|
+
## 0.3.43 - 2026-10-21
|
|
40
|
+
|
|
41
|
+
- Faster: file search on Windows reads files in batches through one helper process instead of starting one per file. A search over 300 files now takes well under a second. Results are unchanged.
|
|
42
|
+
- Internal changes that do not change how the agent works on Windows.
|
|
43
|
+
- Includes everything in 0.3.42.
|
|
44
|
+
|
|
45
|
+
## 0.3.42 - 2026-10-21
|
|
46
|
+
|
|
47
|
+
- Fix: editing several lines of a file with Windows line breaks (CRLF) now works when the AI sends plain line breaks. The new text keeps the file's Windows line breaks.
|
|
48
|
+
- Fix: files saved as UTF-16 (for example by Windows PowerShell) or with a byte order mark can be read, searched and edited. The encoding and the mark are kept.
|
|
49
|
+
- New: text files up to 16 MiB can be read page by page, for example the end of a large log. Files over 1 MiB used to be refused.
|
|
50
|
+
- Fix: reading a file with very long lines returns the whole lines that fit and where to continue, instead of failing.
|
|
51
|
+
- Fix: searches and folder listings return what fits and say when the result is incomplete, instead of silently skipping files or failing on one unreadable folder.
|
|
52
|
+
- Fix: clear errors for files that are locked by another program, read-only, binary or too large.
|
|
53
|
+
- Internal changes that do not change how the agent works on Windows.
|
|
54
|
+
- Includes everything in 0.3.41.
|
|
55
|
+
|
|
56
|
+
## 0.3.41 - 2026-10-17
|
|
57
|
+
|
|
58
|
+
- Fix: the agent no longer exits when the Local Commander service stops answering, for example during a server restart. A connection attempt that gets no answer now gives up after 10 seconds and the agent tries again 2 seconds later, so the computer comes back online by itself.
|
|
59
|
+
- Fix: `update` no longer reports a failure when Windows takes longer than 15 seconds to announce the PATH change. The update had already finished.
|
|
60
|
+
- Includes everything in 0.3.40.
|
|
61
|
+
|
|
62
|
+
## 0.3.40 - 2026-10-16
|
|
63
|
+
|
|
64
|
+
- Docs: the README covers only what this package installs. Developer-only notes are removed, and the release-history link no longer points to a private repository.
|
|
65
|
+
- No change to the agent, its commands or its permissions.
|
|
66
|
+
- Includes everything in 0.3.39-pairlink.1.
|
|
67
|
+
|
|
68
|
+
## 0.3.39-pairlink.1 - 2026-10-15
|
|
69
|
+
|
|
70
|
+
- Change: the pairing link printed in the terminal now carries the confirmation code, so the website opens the Connect dialog with the code already filled in. Check that it matches the code in your terminal, then click Approve (#218).
|
|
71
|
+
- Includes everything in 0.3.38-local.1.
|
|
72
|
+
|
|
73
|
+
## 0.3.38-local.1 - 2026-10-15
|
|
74
|
+
|
|
75
|
+
- New: direct local MCP for AI clients on this computer, such as Claude Code, Codex or Cursor (#104).
|
|
76
|
+
- Turn it on once with `localcommander mcp on`, then add `cmd /c localcommander mcp` to the client's MCP settings.
|
|
77
|
+
- Calls go straight to the running agent with no cloud round trip, so they take milliseconds and keep working without internet.
|
|
78
|
+
- The same approved workspaces, Full Access or scoped mode and your denials apply.
|
|
79
|
+
- The agent listens only on 127.0.0.1, only while this is on, and accepts only processes of your Windows user. `localcommander mcp off` revokes it immediately.
|
|
80
|
+
- Fix: `localcommander network status` works again, and uninstall can remove the network service on a PC that set it up earlier (#204).
|
|
81
|
+
- Includes everything in 0.3.37-review.1.
|
|
82
|
+
|
|
83
|
+
## 0.3.37-review.1 - 2026-10-14
|
|
84
|
+
|
|
85
|
+
- Change: this version ships without the AI connection (the `localcommander network` and `network proxy` commands and the bundled network service). The package is about 82 MB smaller. The agent no longer requests an AI connection or starts proxy mode, even if an earlier version turned it on. `localcommander network off`, `localcommander network proxy off` and uninstall still work, so a PC that enabled it can switch it off (#204).
|
|
86
|
+
- Includes everything in 0.3.36-startup.1.
|
|
87
|
+
|
|
88
|
+
## 0.3.36-startup.1 - 2026-10-14
|
|
89
|
+
|
|
90
|
+
- Fix: when an AI opens a project that has no `AGENTS.md` file (most projects), the agent now returns the project overview without project instructions. Before, this first step ended with an "unknown" result and a critical alert in your account, and the AI could stall. Projects with an `AGENTS.md` work as before (#197).
|
|
91
|
+
- Includes everything in 0.3.35-restart.1.
|
|
92
|
+
|
|
93
|
+
## 0.3.35-restart.1 - 2026-10-14
|
|
94
|
+
|
|
95
|
+
- Fix: when the agent restarts while a command is running (an update, a crash or a reboot), that command no longer keeps one of your execution slots busy until support frees it. After the restart the agent checks that the command's process is really gone and tells localcmd.app, which frees the slot. The command's result stays "unknown" (code `AGENT_RESTARTED`): it may have done part of its work, so check before running it again. If the agent cannot confirm the process is gone, the slot stays held as before. Commands interrupted under an older agent are not covered.
|
|
96
|
+
- Includes everything in 0.3.34-monitor.1.
|
|
97
|
+
|
|
98
|
+
## 0.3.34-monitor.1 - 2026-10-14
|
|
99
|
+
|
|
100
|
+
- Fix: an idle agent no longer rewrites its whole monitor file (about 50 KB) every minute. That came to about 70 MB of disk writes a day while doing nothing. The once-a-minute connection check now updates a small separate file of about 110 bytes, and the monitor file is rewritten only when something actually changes. `localcommander monitor` shows the same connected, stale and stopped states as before.
|
|
101
|
+
- Includes everything in 0.3.33-codepage.1.
|
|
102
|
+
|
|
103
|
+
## 0.3.33-codepage.1 - 2026-10-14
|
|
104
|
+
|
|
105
|
+
- Fix: output from programs that print in the Windows ANSI code page is now readable. Examples are `chcp` and Python or Java with default settings; on a Russian PC they write windows-1251, not CP866. Each output stream is now checked against both the ANSI and the console (OEM) code page, and the one that reads as real text is used. `cmd.exe` and Windows PowerShell output in CP866 stays as it was, and UTF-8 output is unchanged.
|
|
106
|
+
- Fix: when the agent was started from a UTF-8 terminal, it took that terminal's code page (65001) as the console code page, so CP866 output came back as `�`. The agent now checks the code page its commands actually get.
|
|
107
|
+
- Includes everything in 0.3.32-identity.1.
|
|
108
|
+
|
|
109
|
+
## 0.3.32-identity.1 - 2026-10-14
|
|
110
|
+
|
|
111
|
+
- Protection against running work on the wrong computer: when localcmd.app asks for it, the agent now proves which Windows installation it is running on. It sends a fingerprint of this PC's Windows machine ID and computer name, salted for this pairing so it cannot be matched across pairings. The first connection after updating records it. If a later connection comes from a copied disk image, a cloned virtual machine or a renamed PC, localcmd.app pauses the computer ("quarantined") and runs nothing on it until you confirm it at localcmd.app or remove its access.
|
|
112
|
+
- If the machine ID cannot be read, the agent connects as before, without the proof.
|
|
113
|
+
- Fix: output from Windows console programs that print in the system code page (for example Russian `cmd.exe` messages in CP866) is now readable text instead of `�` characters. UTF-8 output is unchanged. `LCMCP_CONSOLE_ENCODING` overrides the detected code page.
|
|
114
|
+
- Includes everything in 0.3.31-leases.1, the optional encrypted content audit pilot (off by default) and the AI connection network bundle.
|
|
115
|
+
|
|
116
|
+
## 0.3.31-leases.1 - 2026-10-13
|
|
117
|
+
|
|
118
|
+
- Fix: commands that never started now always give their slot back. If the connection to Local Commander dropped, or the agent restarted, while a command was waiting to start, the cloud was never told it didn't run. That command kept one of your execution slots until a manual fix, and once enough slots were held, new commands timed out while the computer showed online. The agent now reports these commands as not started, the same way it already did for commands it refused, and earlier ones still in its journal are reported on the first reconnect after updating.
|
|
119
|
+
- Commands the agent turns away before starting, because they arrived on a stale connection or after their deadline, are now reported as not started instead of unknown.
|
|
120
|
+
- Includes the optional encrypted content audit pilot from 0.3.30-audit.1 (off by default) and the AI connection network bundle.
|
|
121
|
+
|
|
122
|
+
## 0.3.30-audit.1 - 2026-10-12
|
|
123
|
+
|
|
124
|
+
- Pilot: optional encrypted content audit for this computer, off by default. `localcommander audit on` starts it: each finished request and response is cleaned of credentials, compressed and encrypted with your own recovery key before it is saved under `%LOCALAPPDATA%\LocalCommander\Audit`. The key is copied to your clipboard, never shown. Files are kept 7 days, and capture pauses at 512 MB; your commands are never slowed or blocked by it.
|
|
125
|
+
- `localcommander audit status` shows the real stored sizes per day; `audit off` stops it; `audit copy-key` copies the key again; `audit restore <file> <output>` decrypts a file with your key from `LCMCP_AUDIT_RECOVERY_KEY`.
|
|
126
|
+
- Includes the AI connection network bundle, as in 0.3.28.
|
|
127
|
+
|
|
128
|
+
## 0.3.29-proxy.5 - 2026-10-11
|
|
129
|
+
|
|
130
|
+
- The AI proxy no longer asks for a password - the browser and CLIs connect with no sign-in (loopback only). network proxy on now adds a Start menu and Desktop shortcut, "AI Browser (Local Commander)", that opens ChatGPT/Claude already routed in one click.
|
|
131
|
+
- This build ships without the network driver, so there is no antivirus prompt during install; it provides the AI connection through the proxy only.
|
|
132
|
+
|
|
133
|
+
## 0.3.29-proxy.4 - 2026-10-11
|
|
134
|
+
|
|
135
|
+
- The AI proxy now keeps the same local port and password across restarts and reboots, so you set up the browser and CLIs once. network proxy on also writes a one-click browser launcher (open-ai-browser.cmd) that opens Chrome/Edge already routed, in a profile that remembers the sign-in.
|
|
136
|
+
|
|
137
|
+
## 0.3.29-proxy.3 - 2026-10-11
|
|
138
|
+
|
|
139
|
+
- Fix: the proxy now sends a Basic authentication challenge, so browsers (Chrome/Edge) can sign in to it instead of failing with ERR_PROXY_AUTH_UNSUPPORTED.
|
|
140
|
+
|
|
141
|
+
## 0.3.29-proxy.2 - 2026-10-11
|
|
142
|
+
|
|
143
|
+
- Fix: proxy-mode state now lives in its own folder instead of the agent state folder, which refused to start after proxy.1 wrote a file there.
|
|
144
|
+
|
|
145
|
+
## 0.3.29-proxy.1 - 2026-10-11
|
|
146
|
+
|
|
147
|
+
- New: driver-free AI connection proxy for machines where antivirus blocks the network driver. `localcommander network proxy on` runs a local proxy that routes ChatGPT/Claude/Cursor through the gateway over HTTPS and everything else directly, for the browser and for CLIs (Claude Code, Codex, and any tool that reads a proxy variable). No TUN driver or privileged service is used; the agent verifies the connection lease itself. `localcommander network proxy status` and `off` manage it.
|
|
148
|
+
|
|
149
|
+
## 0.3.28-systemca.2 - 2026-10-11
|
|
150
|
+
|
|
151
|
+
- Fix: if antivirus removes or blocks an AI connection file, `update` and install now skip the AI connection with a message and still start Local Commander. Before, the update stopped with `NETWORK_BUNDLE_ALLOWLIST_FAILED` and left the agent stopped. The AI connection files are still installed only when every file passes its checksum.
|
|
152
|
+
- Unexpected install errors now show the Windows error class, for example `LOCAL_COMMANDER_FAILED (EPERM copyfile)`, without file paths.
|
|
153
|
+
|
|
154
|
+
## 0.3.28-systemca.1 - 2026-10-11
|
|
155
|
+
|
|
156
|
+
- Fix: the agent now trusts the certificates Windows trusts, as well as its built-in list. Computers whose antivirus or company network inspects HTTPS (for example Kaspersky Endpoint Security) can pair and connect without extra setup; before this they stopped at `NETWORK_FAILED`. Certificate checking stays on.
|
|
157
|
+
|
|
158
|
+
## 0.3.27-aiconnect.5 - 2026-10-11
|
|
159
|
+
|
|
160
|
+
- Fix: the network service could deadlock when its routing core exited. The first protected-route start now waits for the Windows network driver, and setup can replace a service that stopped responding.
|
|
161
|
+
|
|
162
|
+
## 0.3.26-aiconnect.4 - 2026-10-11
|
|
163
|
+
|
|
164
|
+
- Fix: network setup files live in their own folder; 0.3.25 wrote its receipt into the agent's private state folder, which then refused to start.
|
|
165
|
+
|
|
166
|
+
## 0.3.25-aiconnect.3 - 2026-10-11
|
|
167
|
+
|
|
168
|
+
- Fix: the network service now identifies the local agent from its process token, so the agent can reach it (0.3.24 could not connect).
|
|
169
|
+
|
|
170
|
+
## 0.3.24-aiconnect.2 - 2026-10-11
|
|
171
|
+
|
|
172
|
+
- AI connection pilot now reaches the gateway through a published HTTPS (WebSocket) endpoint, which works on networks where direct UDP is blocked. Each AI connection is an authenticated tunnel; the AI service's own encryption stays end to end.
|
|
173
|
+
- The tunnel runs inside Local Commander itself: when the agent stops, the protected route stops too. No extra proxy program is installed on Windows.
|
|
174
|
+
- Still an unsigned pilot: nothing changes until you run `localcommander network setup`.
|
|
175
|
+
|
|
176
|
+
## 0.3.23-aiconnect.1 - 2026-10-11
|
|
177
|
+
|
|
178
|
+
- AI connection pilot (#112): an optional Windows network service routes only ChatGPT/OpenAI, Claude and Cursor traffic through Local Commander's gateway, in Automatic, On or Off mode. Other internet traffic keeps its usual route.
|
|
179
|
+
- Access is tied to this computer's live Local Commander connection: short signed leases (45 seconds) that the server stops renewing when the device is revoked, disconnected or turned Off.
|
|
180
|
+
- Pilot build: the network service is not code-signed yet, so Windows shows "Unknown publisher". Nothing changes until you run `localcommander network setup`; `localcommander network off` and `localcommander network status` work locally.
|
|
181
|
+
|
|
182
|
+
## 0.3.22-fullaccess.1 - 2026-10-10
|
|
183
|
+
|
|
184
|
+
- Owner-approved Full Access no longer requires per-executable registration for Windows shells or administration tools. The Windows account rights and explicit deny-command restrictions remain enforced.
|
|
185
|
+
- Scoped grants and native authentication, target binding, journal/recovery and concurrency safeguards are unchanged.
|
|
186
|
+
- Local direct MCP and remote startup improvements remain separate issue #104 tasks; this build still uses authenticated hosted relay for ChatGPT web.
|
|
187
|
+
|
|
188
|
+
## 0.3.17-journal.1 - 2026-10-08
|
|
189
|
+
|
|
190
|
+
- Apply existing retention maintenance when a new request reaches the journal entry limit on a long-lived connection.
|
|
191
|
+
- Remove only expired, acknowledged terminal records under the existing integrity and retention checks.
|
|
192
|
+
- Keep active, unknown, unacknowledged and recent records protected; admission still fails closed when no record is eligible.
|
|
193
|
+
|
|
194
|
+
Includes the aligned monitor and expanded names from 0.3.16. This does not release unknown cloud reservations or replay work.
|
|
195
|
+
|
|
196
|
+
## 0.3.16-monitor.1 — 2026-10-08
|
|
197
|
+
|
|
198
|
+
- Align monitor columns, including Unicode text, numeric values and states.
|
|
199
|
+
- Leave unused registrations and empty activity rows out of the named agent view.
|
|
200
|
+
- Add 48 playful names to the existing short-name pool, for 128 choices.
|
|
201
|
+
- Show measured call counts, average duration, output and response bytes, errors, and native status/output polls.
|
|
202
|
+
- Exclude stale native snapshots from current per-computer savings totals.
|
|
203
|
+
|
|
204
|
+
Names are display hints. IDs and permissions are unchanged. Token figures remain estimates from measured bytes; provider usage and prices are not inferred.
|
|
205
|
+
|
|
206
|
+
## 0.3.15-recovery.1 — 2026-10-07
|
|
207
|
+
|
|
208
|
+
- Deliver durable proof when the native agent rejects work before acceptance, including after reconnect.
|
|
209
|
+
- Release cloud reservations only after a rejection receipt passes the existing execution and device checks.
|
|
210
|
+
- Retain fencing for unknown executions without rejection proof.
|
|
211
|
+
- Prune acknowledged terminal journal records using the existing retention rules.
|
|
212
|
+
# 0.3.19-admission.1
|
|
213
|
+
|
|
214
|
+
New execution admission pauses when protected journal capacity is exhausted; authenticated relay status carries the pause while status, output and cancellation remain available. Retains the verified native18 default of 2,000 entries, the existing byte/retention limits and unknown-execution fencing.
|
|
215
|
+
|
|
216
|
+
# 0.3.21-project-targets.3
|
|
217
|
+
|
|
218
|
+
Explicit project targets use on-demand repository identity and constrain session paths to the selected repository. Retains installed target20 behavior and adds accepted journal admission guards and authenticated readiness reporting; existing journal retention, permission checks and unknown-execution fencing remain.
|