tryharness 0.7.78 → 0.7.82

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.
Files changed (63) hide show
  1. package/README.md +4 -3
  2. package/assets/install.sh +104 -0
  3. package/cli.mjs +203 -321
  4. package/lib/adapters.mjs +7 -6
  5. package/lib/agentRuntimes.mjs +2 -1
  6. package/lib/backupSetup.mjs +0 -52
  7. package/lib/boardProtocol.json +21 -1
  8. package/lib/browserPage.mjs +30 -0
  9. package/lib/coordinator.mjs +0 -2
  10. package/lib/daemon.mjs +117 -7
  11. package/lib/desktop.mjs +7 -1
  12. package/lib/dispatcher.mjs +12 -2
  13. package/lib/environments.mjs +4 -11
  14. package/lib/goalCommands.mjs +18 -8
  15. package/lib/hookDialects.mjs +2 -1
  16. package/lib/jobAnswers.mjs +2 -1
  17. package/lib/kanban.mjs +217 -48
  18. package/lib/localStack.mjs +24 -9
  19. package/lib/machineRoutes.mjs +9 -0
  20. package/lib/machineRuns.mjs +9 -1
  21. package/lib/manager.mjs +60 -2
  22. package/lib/mcp-stdio.mjs +9 -3
  23. package/lib/museSession.mjs +2 -1
  24. package/lib/nativeHost.mjs +11 -2
  25. package/lib/network.mjs +20 -0
  26. package/lib/notify.mjs +48 -16
  27. package/lib/onboard.mjs +71 -366
  28. package/lib/ownMachines.mjs +95 -44
  29. package/lib/pairing.mjs +0 -84
  30. package/lib/paths.mjs +17 -0
  31. package/lib/peopleBoard.mjs +131 -0
  32. package/lib/personNotices.mjs +9 -25
  33. package/lib/phones.mjs +1 -0
  34. package/lib/profile.mjs +0 -109
  35. package/lib/projectBoard.mjs +219 -0
  36. package/lib/projectPieces.mjs +26 -0
  37. package/lib/projects.mjs +37 -4
  38. package/lib/removeHarness.mjs +91 -0
  39. package/lib/roomChannels.mjs +2 -0
  40. package/lib/runAuthority.mjs +23 -9
  41. package/lib/runBrief.mjs +20 -14
  42. package/lib/runner.mjs +3 -3
  43. package/lib/runtime-install.mjs +22 -2
  44. package/lib/screen.mjs +133 -0
  45. package/lib/selfUpdate.mjs +6 -6
  46. package/lib/service.mjs +120 -7
  47. package/lib/sessionControl.mjs +10 -0
  48. package/lib/setupChoices.mjs +400 -0
  49. package/lib/setupMode.mjs +137 -0
  50. package/lib/store.mjs +6 -3
  51. package/lib/swarm.mjs +181 -61
  52. package/lib/t3.mjs +23 -14
  53. package/lib/taskCommands.mjs +25 -15
  54. package/lib/taskRooms.mjs +2 -4
  55. package/lib/threadActions.mjs +16 -4
  56. package/lib/threadAuthority.mjs +28 -10
  57. package/lib/threadRuns.mjs +162 -74
  58. package/lib/toolCheck.mjs +136 -0
  59. package/lib/ui.mjs +15 -1
  60. package/lib/wakes.mjs +3 -3
  61. package/npm-shrinkwrap.json +14 -14
  62. package/package.json +4 -4
  63. package/release.json +64 -55
package/README.md CHANGED
@@ -392,9 +392,10 @@ the user set in Harness and Quotient answers it with one search over its tracked
392
392
  daemon must be connected to post it, and `get_task` (or `tryharness board show <id>`) with its
393
393
  id reads it back. A task for a coding agent or Grok Bot waits here. A task for several agents
394
394
  at once is for agents in one place.
395
- Grok Bot keeps its MCP servers in its own account settings, so setup prints
396
- `npx tryharness mcp grok-bot`, a one-server snippet to paste into Grok Bot's MCP settings; it
397
- then appears on the board as `grok-bot`.
395
+ Grok Bot and Muse run in their own clouds. `tryharness agents setup grok-bot` (or `muse`)
396
+ shows the one message Harness writes for each and puts it on the clipboard; the agent adds
397
+ Harness as an OAuth connector, the person approves it on Harness's approval page under the
398
+ agent's name, and it appears on the board as `grok-bot` or `muse`.
398
399
 
399
400
  The daemon dials out to Harness over one authenticated WebSocket. Its local control
400
401
  socket is permissioned to the current user. When OpenCode is installed, the daemon also
@@ -0,0 +1,104 @@
1
+ #!/bin/sh
2
+ # Installs Harness: curl -fsSL https://tryharness.ai/install | sh
3
+ # (arguments for setup go after `sh -s --`, for example: ... | sh -s -- --no-desktop)
4
+ #
5
+ # What it does, in order:
6
+ # 1. Downloads Node.js $NODE_VERSION for this computer from nodejs.org, checks it
7
+ # against the SHA-256 sums nodejs.org publishes, and unpacks it into
8
+ # ~/.harness/node. Harness runs on this Node; any Node you have is left as it
9
+ # is. Nothing is installed outside ~/.harness and nothing needs sudo.
10
+ # 2. Runs Harness's setup (npx tryharness) on that Node.
11
+ #
12
+ # `tryharness upgrade` runs this with --node-only (step 1 alone) when a release
13
+ # moves to a newer Node. The Node already here stays until the new one is checked
14
+ # and in place.
15
+
16
+ set -eu
17
+
18
+ NODE_VERSION=22.23.4
19
+ NODE_DIST="${HARNESS_NODE_DIST:-https://nodejs.org/dist}/v$NODE_VERSION"
20
+ HARNESS_HOME="${HARNESS_HOME:-$HOME/.harness}"
21
+ NODE_DIR="$HARNESS_HOME/node"
22
+
23
+ fail() {
24
+ echo "Harness install: $*" >&2
25
+ exit 1
26
+ }
27
+
28
+ platform() {
29
+ case "$(uname -s)" in
30
+ Darwin) os=darwin ;;
31
+ Linux) os=linux ;;
32
+ *) fail "this installer is for macOS and Linux; elsewhere run: npx tryharness" ;;
33
+ esac
34
+ case "$(uname -m)" in
35
+ arm64 | aarch64) arch=arm64 ;;
36
+ x86_64 | amd64) arch=x64 ;;
37
+ *) fail "Node.js $NODE_VERSION has no build for $(uname -m)" ;;
38
+ esac
39
+ echo "$os-$arch"
40
+ }
41
+
42
+ sha256_of() {
43
+ if command -v sha256sum >/dev/null 2>&1; then
44
+ sha256sum "$1" | cut -d ' ' -f 1
45
+ else
46
+ shasum -a 256 "$1" | cut -d ' ' -f 1
47
+ fi
48
+ }
49
+
50
+ installed_version() {
51
+ "$NODE_DIR/bin/node" --version 2>/dev/null || true
52
+ }
53
+
54
+ install_node() {
55
+ if [ "$(installed_version)" = "v$NODE_VERSION" ]; then
56
+ return
57
+ fi
58
+ tarball="node-v$NODE_VERSION-$(platform).tar.gz"
59
+ mkdir -p "$HARNESS_HOME"
60
+ # Downloaded and unpacked inside ~/.harness, so putting it in place is a rename.
61
+ work="$(mktemp -d "$HARNESS_HOME/node-download.XXXXXX")"
62
+ trap 'rm -rf "$work"' EXIT
63
+
64
+ echo "Downloading Node.js $NODE_VERSION for Harness ($tarball)"
65
+ curl -fsSL "$NODE_DIST/SHASUMS256.txt" -o "$work/SHASUMS256.txt"
66
+ curl -fsSL "$NODE_DIST/$tarball" -o "$work/$tarball"
67
+
68
+ expected="$(awk -v name="$tarball" '$2 == name { print $1 }' "$work/SHASUMS256.txt")"
69
+ [ -n "$expected" ] || fail "nodejs.org lists no checksum for $tarball; nothing was installed"
70
+ actual="$(sha256_of "$work/$tarball")"
71
+ [ "$actual" = "$expected" ] ||
72
+ fail "$tarball does not match the checksum nodejs.org publishes; nothing was installed"
73
+
74
+ mkdir "$work/node"
75
+ tar -xzf "$work/$tarball" -C "$work/node" --strip-components 1
76
+ [ "$("$work/node/bin/node" --version)" = "v$NODE_VERSION" ] ||
77
+ fail "the Node.js in $tarball does not run here; nothing was installed"
78
+
79
+ if [ -d "$NODE_DIR" ]; then
80
+ mv "$NODE_DIR" "$work/previous"
81
+ fi
82
+ mv "$work/node" "$NODE_DIR"
83
+ rm -rf "$work"
84
+ trap - EXIT
85
+ echo "Node.js $NODE_VERSION is in $NODE_DIR"
86
+ }
87
+
88
+ # Harness's Node first on PATH, so npx and everything npm starts run on it.
89
+ run_setup() {
90
+ PATH="$NODE_DIR/bin:$PATH"
91
+ export PATH
92
+ exec npx --yes tryharness@latest "$@"
93
+ }
94
+
95
+ main() {
96
+ install_node
97
+ if [ "${1:-}" = "--node-only" ]; then
98
+ exit 0
99
+ fi
100
+ run_setup "$@"
101
+ }
102
+
103
+ # Everything above only defines; this last line runs it, so a download cut short runs nothing.
104
+ main "$@"