Skip to content

Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors

Rust

docs(windows): use the WinSW 2.12 service-account schema

AkitaOnRails403e9c9d4a8e
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 0ea4c3a1..ec2f6f80 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -12,6 +12,13 @@ version in [`docs/changelog/`](docs/changelog/):
## [Unreleased]
### Fixed
+- Fixed the WinSW v2.12.0 service-account example using the v3
+ `<username>` element. WinSW v2.12.0 expects separate `<domain>` and `<user>`
+ elements; it ignored `<username>` and installed the service as
+ `LocalSystem`, which cannot safely own a wiki under another user's profile.
+ The Windows guide now uses the version-correct XML, grants service logon,
+ explains reinstalling an existing service, and verifies its recorded
+ `StartName`. (#1321)
- Fixed `/web/health` warning that hook events wait in the local spool during
every active session. Hooks spool each event first and deliver it at the turn,
compaction or session boundary, so a few fresh events in the spool are normal,
diff --git a/docs/windows.md b/docs/windows.md
index 2b878458..da44917f 100644
--- a/docs/windows.md
+++ b/docs/windows.md
@@ -461,17 +461,34 @@ as that user** rather than as `LocalSystem`. In the WinSW XML add a
```xml
<serviceaccount>
- <username>.\you</username>
+ <domain>.</domain>
+ <user>you</user>
<password>your-account-password</password>
+ <allowservicelogon>true</allowservicelogon>
</serviceaccount>
```
(or set it from the service's **Log On** tab in `services.msc` after
-install, then `restart`). Use `.\you` for a local account or
-`DOMAIN\you` for a domain account. `LocalSystem` is only appropriate when
-the data directory is in a location that account owns outright (e.g. a
-dedicated `C:\ProgramData\ai-memory` created and owned by the service
-account).
+install, then `restart`). This is the WinSW v2.12.0 XML shape used by this
+guide. For a local account, keep `<domain>.</domain>`; for a domain account,
+put the domain in `<domain>` and the account name in `<user>`. WinSW v3 uses
+the combined `<username>DOMAIN\you</username>` form instead, so follow the
+schema for the release you pinned.
+
+Add the block before the first `install`. If the service is already installed,
+stop and uninstall it, update the XML, then install and start it again. Verify
+the account recorded by the Service Control Manager rather than relying only
+on the wrapper's running state:
+
+```powershell
+Get-CimInstance Win32_Service -Filter "Name='ai-memory'" |
+ Select-Object Name, StartName, State
+```
+
+`StartName` must name the intended account, not `LocalSystem`. `LocalSystem`
+is only appropriate when the data directory is in a location that account
+owns outright (e.g. a dedicated `C:\ProgramData\ai-memory` created and owned
+by the service account).
> **WinSW error 1069 / stale password.** If `start` fails with *"The
> service did not start due to a logon failure"* (error 1069), the