@akshar5/cohall 0.6.0 → 0.6.2

package/deploy/windows/install-device.ps1

@@ -1,7 +1,25 @@
+param(
+  [Parameter(Mandatory = $true)][string]$NodeExecutable,
+  [Parameter(Mandatory = $true)][string]$Entrypoint,
+  [Parameter(Mandatory = $true)][string]$ConfigurationPath
+)
+
 $ErrorActionPreference = "Stop"
 
-$cohall = (Get-Command cohall -ErrorAction Stop).Source
-$action = New-ScheduledTaskAction -Execute $cohall -Argument "device"
+function Quote-Literal([string]$Value) {
+  return "'" + $Value.Replace("'", "''") + "'"
+}
+
+$bootstrap = @"
+`$ErrorActionPreference = 'Stop'
+`$env:COHALL_CONFIG = $(Quote-Literal $ConfigurationPath)
+`$env:PATH = $(Quote-Literal (Split-Path -Parent $NodeExecutable)) + ';' + `$env:PATH
+& $(Quote-Literal $NodeExecutable) $(Quote-Literal $Entrypoint) device
+exit `$LASTEXITCODE
+"@
+$encoded = [Convert]::ToBase64String([Text.Encoding]::Unicode.GetBytes($bootstrap))
+$powerShell = [Diagnostics.Process]::GetCurrentProcess().MainModule.FileName
+$action = New-ScheduledTaskAction -Execute $powerShell -Argument "-NoLogo -NoProfile -NonInteractive -EncodedCommand $encoded"
 $trigger = New-ScheduledTaskTrigger -AtLogOn -User $env:USERNAME
 $settings = New-ScheduledTaskSettingsSet `
   -ExecutionTimeLimit (New-TimeSpan -Days 3650) `
@@ -17,5 +35,6 @@ Register-ScheduledTask `
   -Settings $settings `
   -Force | Out-Null
 
+Stop-ScheduledTask -TaskName "Cohall Device" -ErrorAction SilentlyContinue
 Start-ScheduledTask -TaskName "Cohall Device"
 Write-Output "Cohall Device scheduled task installed."

package/docs/install.md

@@ -92,7 +92,7 @@ values are prompted with useful defaults. Re-running `cohall init` repairs the
 skill installation and reuses credentials when the selected relay has not
 changed. `cohall join` remains the non-guided configuration primitive.
 
-Workspace roots must already exist. Cohall resolves them to canonical paths and
+Workspace roots must be existing directories. Cohall resolves them to canonical paths and
 rejects delegated work outside them.
 
 For a client that submits work but never runs a device worker:
@@ -215,6 +215,17 @@ plan, or `--no-restart` to leave services pending a manual restart. Back up a
 production relay's data directory before an upgrade because SQLite migrations
 run in place.
 
+An exact version already installed on disk skips package installation and still
+restarts active services. Dry runs and failed installations preserve restart
+recovery state. A new explicit version takes precedence over an older recovery
+record.
+
+Upgrade tools use the first PATH candidate that passes ownership and permission
+checks. Unsafe candidates are skipped; an explicit executable path must pass
+those checks itself. Linux user namespaces may hide root ownership of fixed OS
+directories, but user-installed executables still require trusted ownership and
+permissions.
+
 The relay owner can queue the same built-in upgrade across every registered
 device:
 

package/docs/services.md

@@ -33,8 +33,16 @@ cohall service install
 journalctl --user -u cohall-device -f
 ```
 
-The generated service uses the exact executable that ran the installer. Linger
-is optional. Without it, the user service starts after login and stops with the
+The generated service uses the exact Cohall executable and puts the current
+Node.js directory first on `PATH`. It records the resolved configuration file,
+including `COHALL_CONFIG` or `XDG_CONFIG_HOME` overrides. Reinstall the service
+after moving that file or replacing a Node.js installation at a different path.
+Reinstalling restarts an existing worker to apply the changes.
+
+Other environment overrides are not copied from your shell. Save device settings
+with `cohall configure`, or set them explicitly in the service environment.
+
+Linger is optional. Without it, the user service starts after login and stops with the
 user's service manager. With it, the service starts at boot and remains after
 logout:
 
@@ -172,7 +180,9 @@ cohall service install
 
 The generated LaunchAgent uses `RunAtLoad` and `KeepAlive`: it starts at login,
 restarts after failure, and reconnects when the network returns. It cannot run
-before that user logs in. Check it with:
+before that user logs in. As on Linux, it records the current Node.js directory
+and configuration file, so custom Node installations and `COHALL_CONFIG` work
+after login. Reinstall it when either path changes. Check it with:
 
 ```bash
 launchctl print gui/"$(id -u)"/com.cohall.device
@@ -191,7 +201,10 @@ cohall service install
 ```
 
 The script registers a per-user scheduled task that starts `cohall device` at
-logon and restarts it after failures. It does not run before that user logs on.
+logon and restarts it after failures. The task uses PowerShell to set the selected
+configuration file and start the exact Node.js and Cohall executables, without
+depending on a `cohall.cmd` or `cohall.ps1` shim. Reinstall the task if these paths
+change. It does not run before that user logs on.
 
 ## Upgrade running services
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@akshar5/cohall",
-  "version": "0.6.0",
+  "version": "0.6.2",
   "description": "Let coding agents delegate work across your own devices.",
   "keywords": [
     "agents",
@@ -60,6 +60,7 @@
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.30.0",
     "effect": "4.0.0-beta.102",
+    "execa": "^10.0.1",
     "ws": "^8.21.3",
     "zod": "^4.4.3"
   },
@@ -72,8 +73,9 @@
     "vitest": "^4.1.10"
   },
   "overrides": {
-    "fast-uri": "^3.1.5",
-    "hono": "^4.12.34"
+    "fast-uri": "^3.1.6",
+    "hono": "^4.13.9",
+    "qs": "^6.16.0"
   },
   "engines": {
     "node": ">=24"