shapewall 0.3.3 → 0.6.0
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 +249 -0
- package/README.md +49 -3
- package/dist/agent/package-lock.json +2 -2
- package/dist/client/assets/BoardChat-DdwBcb2N.js +27 -0
- package/dist/client/assets/{BuzzDialog-Ix9qJvim.js → BuzzDialog-DpUcnU6S.js} +1 -1
- package/dist/client/assets/ChecksPanel-CngYV4yz.js +1 -0
- package/dist/client/assets/History-CD0saQA5.js +1 -0
- package/dist/client/assets/LocalSettings-MZy2baig.js +1 -0
- package/dist/client/assets/{Management-NVFDtSZB.js → Management-CSvZ-SHO.js} +1 -1
- package/dist/client/assets/QuickConnect-foLh2QUm.js +1 -0
- package/dist/client/assets/{ShareDialog-By0ETg6n.js → ShareDialog-DPWDftoL.js} +2 -2
- package/dist/client/assets/{app-update-dialog-RGIw24iZ.js → app-update-dialog-CtiXpTRD.js} +1 -1
- package/dist/client/assets/{circle-x-B6KfScOE.js → circle-x-CteRBtXC.js} +1 -1
- package/dist/client/assets/index-Cxz1UVcV.css +2 -0
- package/dist/client/assets/index-uUZVBYUS.js +37 -0
- package/dist/client/assets/play-BjRNIGSf.js +1 -0
- package/dist/client/assets/{refresh-cw-vkgvCCfR.js → refresh-cw-r_tZiFfB.js} +1 -1
- package/dist/client/assets/{runtime-Bft6x_6E.js → runtime-Bvq10IhH.js} +1 -1
- package/dist/client/assets/ui-zQpn-PdL.js +41 -0
- package/dist/client/build-info.json +1 -1
- package/dist/client/index.html +3 -3
- package/dist/client/sw.js +2 -2
- package/dist/console/assets/{LocalAccountsApp-VOCZg8dg.js → LocalAccountsApp-DIdy1KnN.js} +1 -1
- package/dist/console/assets/{LocalConsole-CMwAW-mF.js → LocalConsole-DfcQztF-.js} +1 -1
- package/dist/console/assets/{app-update-dialog-Cw6UDqNP.js → app-update-dialog-ttl9lF5A.js} +1 -1
- package/dist/console/assets/console-OqAjD0kV.js +55 -0
- package/dist/console/assets/console-kvjrAArQ.css +2 -0
- package/dist/console/build-info.json +1 -1
- package/dist/console/console.html +2 -2
- package/docs/agent-hardening.md +192 -0
- package/docs/agent-recipes.md +23 -0
- package/docs/agent-workflow.md +5 -0
- package/docs/agents.md +14 -6
- package/docs/hosted.md +804 -11
- package/docs/where-to-run.md +37 -2
- package/package.json +1 -1
- package/src/agent/backends/acp.js +528 -25
- package/src/agent/branch-mode.js +17 -3
- package/src/agent/card-hash.js +65 -0
- package/src/agent/context.js +41 -0
- package/src/agent/exec-paths.js +105 -0
- package/src/agent/routes.js +2 -2
- package/src/agent/run.js +11 -1
- package/src/agent/starter/cli.js +6 -1
- package/src/agent/turn-changes.js +70 -8
- package/src/cli/args.js +13 -0
- package/src/cli/commands.js +20 -5
- package/src/cli/help.js +36 -1
- package/src/hosted/admin.js +7 -0
- package/src/hosted/agent-approvals.js +28 -3
- package/src/hosted/agent-link.js +1032 -0
- package/src/hosted/agent-policy.js +10 -3
- package/src/hosted/agent-presence.js +63 -22
- package/src/hosted/agent-routes.js +135 -0
- package/src/hosted/agents.js +1199 -0
- package/src/hosted/app.js +89 -5
- package/src/hosted/board-routes.js +127 -3
- package/src/hosted/chat-frames.js +256 -0
- package/src/hosted/chat-job.js +204 -0
- package/src/hosted/chat-permissions.js +191 -0
- package/src/hosted/chat-routes.js +1009 -0
- package/src/hosted/chat-store.js +460 -0
- package/src/hosted/comment-files.js +8 -1
- package/src/hosted/comments.js +1 -1
- package/src/hosted/console-routes.js +11 -0
- package/src/hosted/db.js +165 -0
- package/src/hosted/device-routes.js +64 -8
- package/src/hosted/device.js +35 -4
- package/src/hosted/events.js +3 -3
- package/src/hosted/membership.js +9 -1
- package/src/hosted/pages.js +2 -0
- package/src/hosted/permissions.js +38 -0
- package/src/hosted/presence.js +17 -0
- package/src/hosted/projects.js +29 -2
- package/src/hosted/ratelimit.js +8 -0
- package/src/hosted/tenancy.js +18 -0
- package/src/hosted/token-api.js +118 -19
- package/src/hosted/token-events.js +5 -3
- package/src/hosted/tokens.js +21 -5
- package/src/hosted/turn-hub.js +152 -0
- package/src/remote/agent-connect.js +433 -0
- package/src/remote/agent-fix.js +611 -0
- package/src/remote/agent-job.js +216 -0
- package/src/remote/agent-link.js +904 -0
- package/src/remote/agent-policy-file.js +242 -0
- package/src/remote/credentials.js +35 -1
- package/src/remote/login.js +12 -2
- package/dist/client/assets/BoardChat-DxehB761.js +0 -27
- package/dist/client/assets/ChecksPanel-pA_ueIaJ.js +0 -1
- package/dist/client/assets/History-C9N32kCv.js +0 -1
- package/dist/client/assets/LocalSettings-DawtKnvi.js +0 -1
- package/dist/client/assets/QuickConnect-DO1TjS1t.js +0 -1
- package/dist/client/assets/index-CsqLdqGx.css +0 -2
- package/dist/client/assets/index-DnZarJ3U.js +0 -37
- package/dist/client/assets/shield-check-QzwGhz0t.js +0 -1
- package/dist/client/assets/ui-DI-FGWWK.js +0 -41
- package/dist/console/assets/console-DgfWmUEx.js +0 -55
- package/dist/console/assets/console-Lis0vvdL.css +0 -2
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,255 @@
|
|
|
3
3
|
All notable changes to this project are documented here. The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
|
|
4
4
|
and the project uses [Semantic Versioning](https://semver.org/).
|
|
5
5
|
|
|
6
|
+
## 0.6.0 - 2026-11-12
|
|
7
|
+
|
|
8
|
+
Connected agents, stage C: approvals and edits from a hosted board. A connected agent can make a fix for a comment, on a new
|
|
9
|
+
branch, with each edit allowed by a person on the board. It is off until the machine that has the code switches it on. Nothing
|
|
10
|
+
changes on a local board.
|
|
11
|
+
|
|
12
|
+
- **The default is unchanged.** A connected agent reads and answers only. Edits are switched on only on the machine that has the
|
|
13
|
+
code: `shapewall agent connect --approvals owner` (the person who connected it may allow each edit from the board) or
|
|
14
|
+
`--approvals admins` (whoever the server lets answer: the agent's answer role, admin by default, owner if set).
|
|
15
|
+
`--approvals none` switches it off again. The choice is saved per connection in the machine's own policy file
|
|
16
|
+
(`agent-policy.json` beside the saved token, 0600, outside every repository). It is the ceiling, and the server can only
|
|
17
|
+
narrow it.
|
|
18
|
+
- **More flags for `agent connect`,** each saved for the connection: `--auto none|edits` (what the server's "Allow without
|
|
19
|
+
asking" rule may apply to; default none), `--allow-path FILE` (a settings file the agent may ask to edit: dotfiles,
|
|
20
|
+
`package.json`, a `Makefile`, a `Dockerfile` and CI config are refused otherwise; adds one per run, `none` empties the list),
|
|
21
|
+
`--base BRANCH` (where a fix starts; default the commit the checkout is on, and then a checkout with uncommitted changes to
|
|
22
|
+
tracked files refuses the fix, because the fix would silently leave them out) and `--git-remote NAME|none` (where a finished
|
|
23
|
+
fix is pushed; default `origin`).
|
|
24
|
+
- **Fix with an agent on a hosted comment.** Offered when a connected agent's machine takes edits and you may use that agent. The
|
|
25
|
+
server takes the comment in the agent's name with the rules of sending a comment to an agent: a trusted member vouches for the
|
|
26
|
+
text they saw, a non-admin's run still needs an admin's "Approve agent run" where the policy says so, the agent's audience, the
|
|
27
|
+
daily and open-claims budgets. Chat messages never edit: only Fix does. An offline agent cannot be asked for a fix (Send to
|
|
28
|
+
agent still queues). For an agent that reads and answers only, the button is not offered and one line says why.
|
|
29
|
+
- **A fix is never made in the checked-out tree.** The agent works in a fresh copy of the base commit, with no `.git` in it, in
|
|
30
|
+
a folder outside the project (under `$XDG_STATE_HOME/shapewall/agent-fixes/`), made by the same code as "work on a branch" on a
|
|
31
|
+
local board. Shapewall itself commits the result on a new branch, `shapewall/comment-<n>-<slug>`, with the repository's own
|
|
32
|
+
author; no hook, filter or attribute runs. It pushes that one branch when the machine has the remote and the change touches
|
|
33
|
+
nothing that runs in CI (dependency manifests, CI config: then the thread says "Not pushed" and why), and opens a pull request
|
|
34
|
+
when GitHub connect is set up on that machine. Otherwise the thread says "Fix ready on branch" with the name to copy. The folder
|
|
35
|
+
is removed afterwards; the branch stays. A folder that is not a Git repository, a repository with no commit yet, a merge in
|
|
36
|
+
progress, or uncommitted changes without `--base`: refused, with a clear sentence in the thread and on the comment.
|
|
37
|
+
- **The commit is exactly what was allowed.** Every changed file must have had an allowed edit and must hold exactly the content
|
|
38
|
+
that was shown. A changed edit, an extra file, another file touched: the branch is taken back and the thread says nothing was
|
|
39
|
+
committed. If files in the person's own checkout changed during the fix, the thread says so.
|
|
40
|
+
- **Permission cards.** Each edit the agent asks for is checked on the machine first: inside the fix's folder after resolving
|
|
41
|
+
symlinks, not `.git`, not Shapewall's store, not a settings file unless named with `--allow-path`, and the whole resulting file
|
|
42
|
+
must be computable and small enough to show in full. What fails is refused there and never becomes a question. What passes is
|
|
43
|
+
a card in the comment's chat thread: the path, the full diff, Allow and Deny, in the machine's own words, never the agent's
|
|
44
|
+
title. A card carries a hash of the turn, the card, the path, the whole diff and its expiry, and an answer must send that hash
|
|
45
|
+
back. A card expires after 2 minutes and is answered once. Stop cancels the cards that wait. Everyone with the thread open sees
|
|
46
|
+
the state change live, and the strip above the board lists the cards that wait for you.
|
|
47
|
+
- **Who may answer.** The agent's answer role (admin by default), who is also in the agent's audience and trusted by the
|
|
48
|
+
project's agent policy; only the person who connected the agent when its machine says `--approvals owner`. Allow needs a
|
|
49
|
+
passkey check in the last 10 minutes (the browser asks); Deny does not.
|
|
50
|
+
- **The machine checks every answer again:** a card it asked and still waits on, the same hash, not expired, once, and from the
|
|
51
|
+
connecting person when it said "owner". A failed "allow" is a deny, and an answer for a card it never asked is ignored. The
|
|
52
|
+
server never takes "approved" from the machine.
|
|
53
|
+
- **"Allow without asking"** is an approval rule per agent, in the console's approvals dialog. It is available only when the
|
|
54
|
+
agent's own machine named a kind with `--auto`, is set only by the role in the agent's "who may change the rule" setting (admin
|
|
55
|
+
by default; owners can make it owner), applies only to the kinds the machine named, and never widens what may be edited. If the
|
|
56
|
+
machine connects again without it, the stored rule is reset to "ask", and that is audited.
|
|
57
|
+
- **The console and the board say which mode an agent is in:** "Reads and answers", "Edits on a branch, each allowed by ..." or
|
|
58
|
+
"Edits on a branch, allowed without asking".
|
|
59
|
+
- **Audit log.** New entries: `agent_edit_mode_changed` (what the machine allows changed), `agent_permission_asked`,
|
|
60
|
+
`agent_permission_approved` and `agent_permission_denied` (who, the path, the card's hash; never file content or a diff),
|
|
61
|
+
`agent_permission_expired`, `agent_permission_auto`, `agent_fix_branch_ready`, `agent_branch_pushed` and
|
|
62
|
+
`agent_pull_request_opened` (as reported by the agent's machine), plus `agent_turn_started` with kind "fix" and
|
|
63
|
+
`agent_approval_rule_changed`.
|
|
64
|
+
- **Usage records.** A fix is one record of kind "fix": its steps, how it ended (fix ready, answered, stopped, failed,
|
|
65
|
+
interrupted) and how many requests were asked, allowed and denied.
|
|
66
|
+
|
|
67
|
+
**No commands for Claude Code.** The link and the machine's policy know a third kind of request: exact commands from the
|
|
68
|
+
machine's own list, each allowed on the board (`--allow-command`). It is not available for Claude Code in 0.6.0, and Claude Code
|
|
69
|
+
is still the only agent `agent connect` offers. The reason was found with the real adapter: started with its shell tool, Claude
|
|
70
|
+
Code runs commands it takes to be read-only (`ls`, `cat`) without asking anyone, and those can read outside the project. So a
|
|
71
|
+
fix session of Claude Code gets no shell tool at all, `--allow-command` is refused for it with that explanation, and commands in
|
|
72
|
+
a hand-edited policy file are not in effect.
|
|
73
|
+
|
|
74
|
+
**What leaves the code machine in edit mode,** beyond 0.5.0: the diffs on edit cards (bounded), the file paths and line counts of
|
|
75
|
+
a fix, the branch name and the pull request link. Still not the agent's token, which is never in the agent's environment, and
|
|
76
|
+
not absolute paths.
|
|
77
|
+
|
|
78
|
+
**The limit.** Shapewall does not sandbox the agent's own tools. With approvals on, a compromised hosted server can forge an
|
|
79
|
+
"allow" for an edit the agent really asked, with the right hash. The worst case is then edits to project files, on a branch, in a
|
|
80
|
+
throwaway folder, pushed for review: not commands, not the checkout, and not files outside the project that the agent asks about.
|
|
81
|
+
Give a connected agent a restricted profile, prefer `--approvals owner` to `admins`, review the pull request like any other, and
|
|
82
|
+
do not add `--allow-path` for CI files. [agent-hardening.md](docs/agent-hardening.md#edits-from-a-hosted-board) has the trust
|
|
83
|
+
table and how this was checked with the real Claude Code adapter.
|
|
84
|
+
|
|
85
|
+
Not in this release: recapture and push of new captures after a fix; the model and effort menus; batch fixes; "Allow for this
|
|
86
|
+
chat"; images in chat; connecting one agent to all projects; commands for Claude Code; fixes from chat messages; queueing a fix
|
|
87
|
+
for an offline agent; the usage and audit dashboards.
|
|
88
|
+
|
|
89
|
+
**Compatibility.** `shapewall watch --remote --exec` and `shapewall mcp --remote` work as before, with the same tokens. A
|
|
90
|
+
connected agent that was approved under 0.5.0 keeps reading and answering only until its own machine is started with
|
|
91
|
+
`--approvals`.
|
|
92
|
+
|
|
93
|
+
**Upgrading a hosted server.** Back up first (`shapewall hosted backup`). Migration 14 adds one table (`chat_permissions`) and
|
|
94
|
+
three columns on `agent_runs` (`approvals_asked`, `approvals_allowed`, `approvals_denied`), and changes nothing that exists. To
|
|
95
|
+
go back, restore the backup with 0.5.0, or run 0.5.0 on the upgraded database: it ignores the new table and columns, and a fix
|
|
96
|
+
cannot be started from it. Details and the SQL to remove the schema are in
|
|
97
|
+
[Migration 14 and rollback](docs/hosted.md#migration-14-and-rollback).
|
|
98
|
+
|
|
99
|
+
### After the security review
|
|
100
|
+
|
|
101
|
+
- **Files that run something.** One list (dotfiles, manifests and lockfiles, build and tool configuration, package scripts,
|
|
102
|
+
container and CI files, makefiles, test files) decides both what a connected agent may be asked to edit and what is pushed. An
|
|
103
|
+
edit to one is refused unless the machine names it with `--allow-path`; a named one is always answered by a person; a fix that
|
|
104
|
+
changes one is never pushed from the machine.
|
|
105
|
+
- **Push this fix.** A fix with an edit that went without asking (`--auto edits`) is committed on its branch on the machine and
|
|
106
|
+
held there. It is pushed, and a pull request opened, only after someone who may answer cards allows one card that shows the
|
|
107
|
+
whole diff, with a fresh passkey. It can be asked again.
|
|
108
|
+
- **Only the connecting person switches "Allow without asking" on** when their machine says `--approvals owner`.
|
|
109
|
+
- **Stop stops the commit, the push and the pull request.** A push that had already finished is said in the thread.
|
|
110
|
+
- **The commit check compares bytes and file mode**, and fails when an allowed file is missing from the commit. Edits to files
|
|
111
|
+
Git ignores, to `node_modules` and to `.gitattributes` / `.gitmodules` are refused when they are asked.
|
|
112
|
+
- **The policy file fails narrow**: an unknown value reads as the narrowest setting, by name, and the file's owner and mode are
|
|
113
|
+
checked before it is read.
|
|
114
|
+
- **Cards wait a length of time**, counted on each side's own clock. An answer the machine did not take shows as expired.
|
|
115
|
+
- **Diffs on cards go to the agent's audience** (and whoever may answer or asked). Other members read which file and the outcome.
|
|
116
|
+
- **Fix on a comment whose run needs approval**: an admin's Fix approves and starts; a member's really sends it for approval.
|
|
117
|
+
- **Leftover fix copies are swept** at connect and around every fix; the fix folder is never inside the project.
|
|
118
|
+
- A fix's status is written with its own claim; a pull request link must be a pull request URL (a link only on github.com);
|
|
119
|
+
cards count against the storage quota; comment text in a commit subject or pull request title pings and closes nothing.
|
|
120
|
+
|
|
121
|
+
## 0.5.0 - 2026-11-12
|
|
122
|
+
|
|
123
|
+
Connected agents: your Claude Code on a hosted board, to chat with. It reads and answers only. Nothing changes on a local board.
|
|
124
|
+
|
|
125
|
+
- **`shapewall agent connect --remote <server>`**, run in a project's folder on the machine that has the code, makes that machine's
|
|
126
|
+
Claude Code an agent of a hosted project. The first run shows a code; an admin approves it on the server's `/device` page, where
|
|
127
|
+
they name the agent, pick its icon, its project and who may use it. The agent gets a token of its own, saved on the machine and
|
|
128
|
+
never printed. Flags: `--agent`, `--name`, `--as` (a second connection), `--audience owner|server`, `--takeover`,
|
|
129
|
+
`--concurrency`, `--token-file` (for a service).
|
|
130
|
+
- **Only Claude Code can be connected.** An agent is offered when its own controls were shown to keep a session read-only. Codex,
|
|
131
|
+
goose and Gemini CLI are refused with a message: Codex, started in its read-only sandbox, changed no file in our check but still
|
|
132
|
+
ran shell commands and read a file outside the project without asking; goose's chat-only mode could not be verified on the test
|
|
133
|
+
machine; Gemini CLI was not installed to verify. For them, `shapewall watch --remote` stays the way.
|
|
134
|
+
- **The agent is online while the command runs.** Its state on the board and in the console comes from its open link to the server.
|
|
135
|
+
The link reconnects by itself; Ctrl+C is a clean exit.
|
|
136
|
+
- **One link per agent.** A second `agent connect` on the same token is refused, with the machine already connected and since
|
|
137
|
+
when. `--takeover` closes the other link first; add it to a service's command so a restart after a crash is not refused.
|
|
138
|
+
- **Chat on hosted boards.** The Agents panel has a **Chat** button on each connected agent you may use. It opens the same chat
|
|
139
|
+
panel a local board has: the answer streams in with the agent's steps, Stop works, and the conversation is kept on the server.
|
|
140
|
+
A reload, or a second person with the same thread open, gets a running answer from its start, in order, and a dropped stream
|
|
141
|
+
resumes where it was. The board chat and each comment's chat are shared with the workspace's members; a chat you start is yours
|
|
142
|
+
alone (50 of your own per board). "@" mentions and text files work as they do locally.
|
|
143
|
+
- **Read and answer only, by the agent's own controls.** A connected agent does not change files and runs no commands. Its session
|
|
144
|
+
starts with none of your Claude Code settings files (their allow rules, hooks, default mode, plugins and MCP servers do not
|
|
145
|
+
apply) and with only its reading tools; Bash, Edit, Write, web tools and the rest are removed. Shapewall also offers it no way to
|
|
146
|
+
write or run, and refuses every permission request on the spot, a read outside the project included; the answer says what was
|
|
147
|
+
refused. It fails closed: a mode other than "default" or "plan" is switched or the agent is not started, an agent that reports
|
|
148
|
+
no mode is not started, and managed settings that allow acting tools or run hooks stop `agent connect`. It still reads every
|
|
149
|
+
file in the project folder, and its answers leave the machine. Edits, commands and approvals from the board are not in this
|
|
150
|
+
release; for fixes, keep using `shapewall watch --remote --exec`.
|
|
151
|
+
- **Who may use it** follows the agent's audience, as for comments, and the board shows what is in effect. `--audience owner` asks
|
|
152
|
+
the server to keep it to the person who connected it even if its audience there is widened later, and the machine refuses a job
|
|
153
|
+
the server labels as someone else's; the machine cannot check that label, so it does not protect against a compromised server.
|
|
154
|
+
A message by someone outside an agent's audience never reaches that agent, even in a shared thread, and a share link guest's
|
|
155
|
+
text never does. Viewers, guests and public visitors have no chat.
|
|
156
|
+
- **Comments.** A comment sent to a connected agent by name is read and answered by it, in the comment's chat thread and as a reply
|
|
157
|
+
on the comment. Comments sent to any agent stay with watchers, which can fix them. The board context that goes with a question
|
|
158
|
+
follows the audience too: a comment is in it only when the person asking wrote it, the agent holds it, or its author is in the
|
|
159
|
+
agent's audience and it was sent to an agent and not to another one.
|
|
160
|
+
- **Offline.** Chat to an agent that is offline is refused, with the reason in place of the message box. A thread stays with its
|
|
161
|
+
agent and never moves by itself: the panel offers "Ask <other agent> instead", and the switch is written into the thread.
|
|
162
|
+
Comments sent to an offline agent wait, as before.
|
|
163
|
+
- **Limits.** The daily turn budget is counted from the usage records, so deleting a thread gives nothing back. Turns cut off by a
|
|
164
|
+
server stop are ended as interrupted when it starts again.
|
|
165
|
+
- **The console.** A project's Agents page says what each connected agent is (what runs, on which machine, since when it is
|
|
166
|
+
connected, that it reads and answers only), and its Connect card leads with this server's `shapewall agent connect` command. The
|
|
167
|
+
workspace overview shows the same.
|
|
168
|
+
- **Usage records and the audit log.** Every chat turn writes a usage record: who asked which agent, where, when, how it ended, and
|
|
169
|
+
the model, effort and token counts only when the agent reports them (a cost only when the agent itself reports one; never message
|
|
170
|
+
text). The audit log gains an agent connected, its link opened and closed (at most once a minute per agent when a link flaps), a
|
|
171
|
+
chat thread created, deleted or switched to another agent, and a turn started or stopped.
|
|
172
|
+
|
|
173
|
+
Not in this release: edits, commands and approvals from the board; "Fix with <agent>" through chat; images in chat; editing or
|
|
174
|
+
regenerating a message; answer ratings; the model and effort menus; connecting one agent to every project at once (one connection
|
|
175
|
+
serves one project; connect again with `--as` for another).
|
|
176
|
+
|
|
177
|
+
**Compatibility.** `shapewall watch --remote` and `shapewall mcp --remote` work as before, with the same tokens. The token API now
|
|
178
|
+
tells a token that may take work which agent each comment was sent to (`agentId`: its own agent's id, or `null` for any agent).
|
|
179
|
+
There is a new token scope, `agent`: it opens the link of a connected agent and nothing else, and is granted only by approving
|
|
180
|
+
`shapewall agent connect`. The agent policy has a new number, `dailyTurns` (200 chat turns a day for a project by default).
|
|
181
|
+
|
|
182
|
+
**Upgrading a hosted server.** Back up first (`shapewall hosted backup`). Migration 13 adds three tables for chat (threads, messages,
|
|
183
|
+
turns) and one column, and changes nothing that exists: no token gains a scope and no agent changes its audience. To go back, restore
|
|
184
|
+
the backup with 0.4.0, or run 0.4.0 on the upgraded database: it ignores the new tables, so chat is gone from the board until you
|
|
185
|
+
upgrade again, and a connected agent shows as an ordinary agent whose token still works for comments. Details and the SQL to remove
|
|
186
|
+
the schema are in [Migration 13 and rollback](docs/hosted.md#migration-13-and-rollback).
|
|
187
|
+
|
|
188
|
+
## 0.4.0 - 2026-11-12
|
|
189
|
+
|
|
190
|
+
Agents on a hosted board are things you can see and choose. This is the first step towards connected agents and chat on hosted
|
|
191
|
+
boards; nothing changes on a local board.
|
|
192
|
+
|
|
193
|
+
- On a hosted server, every project token that may take work (the `claim` scope) is an **agent**: it has a name, an icon and a
|
|
194
|
+
colour, a state (online, working, offline with when it was last seen) and a line saying whose work it takes. The board's Agent
|
|
195
|
+
panel lists them with what each is working on and what waits for it, and the Agent button's tooltip names them ("Builder online,
|
|
196
|
+
Fixer offline"). `shapewall watch --remote` and `shapewall mcp --remote` are those agents: they need no new flag and no new token.
|
|
197
|
+
- **Send to agent** on a thread is a split button, like "Fix with <agent>" on a local board. The main part names the project's
|
|
198
|
+
default agent; the menu lists every agent with its state, and **Any agent** for whichever takes it first. A comment sent to one
|
|
199
|
+
agent can only be taken by that agent: the project's other tokens do not see it, by list, by id or through MCP.
|
|
200
|
+
- A comment sent to an agent that is offline waits for it and says so on its thread and in the panel ("Waiting for Builder
|
|
201
|
+
(offline, last seen 2 hours ago)"), with **Let any agent take it** and **Choose another**. Nothing is lost: when the agent is
|
|
202
|
+
back it takes what was sent to it.
|
|
203
|
+
- Each agent says **who may send it work**: only the person who connected it, named members, or everyone the project's agent policy
|
|
204
|
+
trusts. The server checks it when a comment is sent and again when the agent takes it. On the board, an agent you may not use is
|
|
205
|
+
listed, greyed, with the reason. A new agent takes work only from the person who connected it, until an admin shares it.
|
|
206
|
+
- A project has a **default agent**, picked by an admin or owner: the one Send to agent names, and where a trusted member's new
|
|
207
|
+
comment goes. Without one, comments go to any agent, as before.
|
|
208
|
+
- The console has an **Agents** page for each project: every agent with its state, last seen, audience, approval settings and the
|
|
209
|
+
default; rename it and give it an icon and a colour (the editor the local Agents page uses); set the default; change who may use
|
|
210
|
+
it; revoke it; and a **Connect an agent** card with this server's exact commands. **Agents** in the workspace menu lists every
|
|
211
|
+
agent of the workspace with the project it serves and who connected it.
|
|
212
|
+
- Each agent has an approval rule and two roles, who may answer its approvals and who may change the rule (admins and owners, or
|
|
213
|
+
owners only). The rule in effect is always "Always ask"; "Approve automatically" is listed as not available until an agent's own
|
|
214
|
+
machine can allow it.
|
|
215
|
+
- An agent's replies on a thread show its icon. Renaming an agent renames its token: new replies use the new name, old ones keep
|
|
216
|
+
theirs.
|
|
217
|
+
- Phones have the Agent panel now: **Agents** in the board's More menu opens it as a sheet, and a thread's sheet has the same Send
|
|
218
|
+
to agent control.
|
|
219
|
+
- Every change is in the audit log with what it was before and after: an agent created or first seen, renamed, its look, the
|
|
220
|
+
default, its audience, its approval settings, revoked, and a waiting comment released to any agent.
|
|
221
|
+
- The server now writes one usage record for each comment an agent takes (who asked, which agent, when, how it ended; never the
|
|
222
|
+
comment or the answer). There is no page for it yet.
|
|
223
|
+
|
|
224
|
+
**Upgrading a hosted server.** Back up first (`shapewall hosted backup`). Migration 12 adds two tables and three columns and turns
|
|
225
|
+
every token that already has the `claim` scope into an agent that behaves exactly as before: it takes work from everyone the agent
|
|
226
|
+
policy trusts, and no project gets a default agent, so nothing is routed differently until you choose. Tokens made from this
|
|
227
|
+
release on start narrower, with only the person who made them: share such an agent on the project's Agents page if teammates'
|
|
228
|
+
comments should reach it. To go back, restore the backup with 0.3.4, or run 0.3.4 on the upgraded database: it ignores the new data,
|
|
229
|
+
which means a comment sent to one agent can be taken by any watcher, audiences are not enforced, and default agents, icons and
|
|
230
|
+
usage records are not shown until you upgrade again. Details and the SQL to remove the schema are in
|
|
231
|
+
[Migration 12 and rollback](docs/hosted.md#migration-12-and-rollback).
|
|
232
|
+
|
|
233
|
+
## 0.3.4 - 2026-11-12
|
|
234
|
+
|
|
235
|
+
- The agent's "Changed N files" card lists only the agent's work. Files Git ignores (by `.gitignore` as it is on disk, committed or
|
|
236
|
+
not, `.git/info/exclude` and your global excludes) are never listed or counted, and Undo never touches them. Before, anything
|
|
237
|
+
another program wrote inside the project folder during the turn showed up in the card (a dev server's data, a log), and Undo could
|
|
238
|
+
have deleted those new files and rolled the changed ones back. Outside a Git repository the list works as before, and Shapewall's
|
|
239
|
+
own folders (`.shapewall*`) are always left out.
|
|
240
|
+
- Hosted boards have the Agent button in the top bar, next to Comments and Checks, for people who can send comments to an agent. It
|
|
241
|
+
opens a small panel: whether an agent is listening ("Agent online: <token name>", or "No agent is listening" with the command to
|
|
242
|
+
connect one), what is running and what waits for you, each opening its comment. There is still no chat on hosted boards. Share
|
|
243
|
+
link guests and public viewers do not get it.
|
|
244
|
+
- The sidebar has one search field on every board. On a board with no journeys the old "Filter pages" box was still shown under
|
|
245
|
+
"Search the board".
|
|
246
|
+
- Esc is never swallowed by a tooltip. With the keyboard on a button inside a thread or a dialog (its tooltip showing), one Esc now
|
|
247
|
+
closes the thread or dialog; before, the first Esc only closed the tooltip.
|
|
248
|
+
- Phone: in the drawing sheet every tool and ink is a full 44 px target; the tools are on one line and the inks, Undo and Clear on
|
|
249
|
+
the next. In the journey bar each step has a 44 px target around its dot, and a journey with many steps scrolls sideways inside
|
|
250
|
+
the bar.
|
|
251
|
+
- "Fix ready on branch" wears the attention colour everywhere, the same as on the toolbar: it waits for you to apply it.
|
|
252
|
+
- `shapewall settings` exits cleanly (code 0, after cleaning up) when it is stopped the moment it starts. Before, a Ctrl-C or a
|
|
253
|
+
script's signal that arrived right as it printed its address could kill it outright.
|
|
254
|
+
|
|
6
255
|
## 0.3.3 - 2026-11-11
|
|
7
256
|
|
|
8
257
|
- Commenting goes one step at a time, and the board always says which step you are at. Pick: in comment mode the element under the
|
package/README.md
CHANGED
|
@@ -51,7 +51,11 @@ feedback, fix the code, and you recapture to check.
|
|
|
51
51
|
- **Works on a phone.** 44 px touch targets, a bottom sheet for comments, and Back closes the topmost panel instead of leaving the board.
|
|
52
52
|
- **Small and local.** Node 22, Playwright, Express, React Flow. Data is plain JSON files in `.shapewall/`. No account, no cloud.
|
|
53
53
|
- **A team server when you want one.** `shapewall hosted` adds passkey accounts, workspaces with roles, share links and live presence
|
|
54
|
-
on a server you run.
|
|
54
|
+
on a server you run. `shapewall agent connect` puts your Claude Code on the hosted board: teammates chat with it there, and it
|
|
55
|
+
reads the project and answers. When its own machine says so (`--approvals`), it also makes a fix for a comment on a new branch,
|
|
56
|
+
each edit allowed on the board. Each machine that watches a hosted board is an agent too, with a name, an
|
|
57
|
+
icon and a state; people send a comment to one by name, and each agent says whose work it takes.
|
|
58
|
+
[Multiplayer (beta)](#multiplayer-on-your-own-server).
|
|
55
59
|
- **Switch local projects.** Serve each project on its own port; the site dropdown lists them together while keeping every project's
|
|
56
60
|
agent and files separate. [Several local projects](docs/deployment.md#several-local-projects).
|
|
57
61
|
|
|
@@ -124,8 +128,15 @@ shapewall hosted --data ./hosted-data --tailscale --tailscale-port 8443
|
|
|
124
128
|
|
|
125
129
|
Run that on one machine. Teammates open its HTTPS address over Tailscale, sign in with their own passkeys and join a workspace you
|
|
126
130
|
invite them to. Captures still run on your machine: `shapewall share --remote URL` moves an existing project to the server, or `login`
|
|
127
|
-
and `push` upload new captures. Comments, roles, scoped agents and live presence work on the shared server.
|
|
128
|
-
|
|
131
|
+
and `push` upload new captures. Comments, roles, scoped agents and live presence work on the shared server. A machine that runs
|
|
132
|
+
`shapewall watch --remote URL` is an agent on that board, listed by name with its state; people send a comment to one agent or to
|
|
133
|
+
any, and each agent takes work only from the people it is shared with. `shapewall agent connect --remote URL`, run in a project's
|
|
134
|
+
folder, connects that machine's Claude Code for chat on the board: an admin approves it in the browser, members ask it questions
|
|
135
|
+
from the Agents panel, and it reads the project and answers. By default it does not change files or run commands from the board.
|
|
136
|
+
Edits are switched on only on the machine that has the code (`--approvals owner` or `admins`): **Fix with** on a comment then
|
|
137
|
+
makes the fix on a new branch there, never in the checkout, and each edit is a card with the full diff that someone allows or
|
|
138
|
+
denies on the board. It runs no commands from the board. Codex, goose and Gemini CLI are not offered by `agent connect` in this
|
|
139
|
+
release; for them, `shapewall watch --remote` stays the way ([Connected agents](docs/hosted.md#connected-agents)). You need no public domain and no Shapewall account.
|
|
129
140
|
|
|
130
141
|
The command runs in the foreground and sets up Tailscale Serve; running it as a service and backing it up are covered in
|
|
131
142
|
[the hosted guide](docs/hosted.md), with a [checklist to walk through before you invite the team](docs/hosted.md#before-you-invite-the-team).
|
|
@@ -497,6 +508,40 @@ Commands
|
|
|
497
508
|
--no-claim hand out every open comment once without claiming it (no agent status, beside other watchers)
|
|
498
509
|
a command that exits 0 must reply or set a status itself, else the
|
|
499
510
|
comment becomes needs-human (docs/agent-workflow.md)
|
|
511
|
+
agent connect make this machine's coding agent an agent of a hosted project: members chat with it
|
|
512
|
+
on the board, and it reads this folder and answers. Read and answer only unless this
|
|
513
|
+
machine says more (--approvals). The first run is approved in the browser by an admin.
|
|
514
|
+
--remote URL
|
|
515
|
+
--agent NAME which agent: claude, or a saved agent's id that runs Claude Code (default: this
|
|
516
|
+
project's agent, else Claude Code when found). Codex, goose and Gemini CLI are not
|
|
517
|
+
offered in this release. Never a command from the server
|
|
518
|
+
--name "Builder" the name to suggest on the approval page (the approver has the last word)
|
|
519
|
+
--as NAME a second connection from this machine (its own token; default "default")
|
|
520
|
+
--audience owner|server "owner": the server keeps it to the person who connects it even if its audience
|
|
521
|
+
there is widened, and this machine refuses a job the server says is someone else's
|
|
522
|
+
(no protection from a server that lies); "server" (default): its audience on the server
|
|
523
|
+
--approvals none|owner|admins edits from the board. "none" (default): never. "owner": the person who
|
|
524
|
+
connected it may allow each edit on the board. "admins": whoever the server lets
|
|
525
|
+
answer (admins by default). A fix is made on a new branch in a folder of its own,
|
|
526
|
+
never in this checkout. Saved for this connection; the server cannot widen it
|
|
527
|
+
--allow-command "CMD" one exact command the agent may ask to run, each time allowed on the board (adds to
|
|
528
|
+
the list; "none" empties it). Default: no commands at all. Not for Claude Code in
|
|
529
|
+
this release: with its shell tool it runs read-only commands without asking
|
|
530
|
+
--auto none|edits|commands|edits,commands what the server's "allow without asking" rule may apply to
|
|
531
|
+
(default none). Never a file that runs something. Such a fix stays on this machine:
|
|
532
|
+
it is pushed only after a person allows "Push this fix" on its whole diff. With
|
|
533
|
+
--approvals owner, only the person who connected it can switch the rule on
|
|
534
|
+
--allow-path FILE a file that runs on install, build, test or CI (a dotfile, package.json, a Makefile,
|
|
535
|
+
a *.config.js, a script, a test, CI config) the agent may ask to edit; such edits are
|
|
536
|
+
refused otherwise, a named one is always asked, and a fix that changes one is never
|
|
537
|
+
pushed (adds to the list; "none" empties it)
|
|
538
|
+
--base BRANCH the branch a fix starts from (default "head": the commit this checkout is on, and
|
|
539
|
+
then only while it has no uncommitted changes)
|
|
540
|
+
--git-remote NAME where a finished fix is pushed (default origin; "none": never pushed). A pull request
|
|
541
|
+
is opened when GitHub connect is set up here (docs/github.md)
|
|
542
|
+
--takeover close the link another machine holds for this agent, and take its place
|
|
543
|
+
--concurrency N answers at once, 1 to 4 (default 2)
|
|
544
|
+
--token-file FILE for a service: the agent's own token, no browser (docs/hosted.md)
|
|
500
545
|
agent run --comment ID the sandboxed starter agent on one comment: a container with only a fresh
|
|
501
546
|
worktree, egress to the package registry only (the model is called from here), a branch
|
|
502
547
|
--pr also push the branch and open a pull request (GitHub connect); not when it
|
|
@@ -580,6 +625,7 @@ Hosted Shapewall (docs/hosted.md)
|
|
|
580
625
|
the same commands against a hosted board (--board ID picks one)
|
|
581
626
|
token: $SHAPEWALL_TOKEN or --token-file FILE (a project token, swp_...)
|
|
582
627
|
watch --exec commands get no token unless --pass-token
|
|
628
|
+
watch and mcp show on the board as an agent, by the token's name
|
|
583
629
|
--include-guests comments and watch: also share link guests' comments (untrusted)
|
|
584
630
|
hosted run the hosted server (accounts, workspaces, pushed boards)
|
|
585
631
|
--data DIR default ./shapewall-hosted-data (or $SHAPEWALL_HOSTED_DATA)
|
|
@@ -1,12 +1,12 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "shapewall",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.6.0",
|
|
4
4
|
"lockfileVersion": 3,
|
|
5
5
|
"requires": true,
|
|
6
6
|
"packages": {
|
|
7
7
|
"": {
|
|
8
8
|
"name": "shapewall",
|
|
9
|
-
"version": "0.
|
|
9
|
+
"version": "0.6.0",
|
|
10
10
|
"license": "Apache-2.0 AND FSL-1.1-ALv2",
|
|
11
11
|
"dependencies": {
|
|
12
12
|
"@agentclientprotocol/sdk": "2.4.0",
|