@sealant/mend 0.37.0-next.1197 → 0.37.0-next.1395
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/dist/agent-skill.md +287 -0
- package/dist/{chunk-EX5C6Y5A.js → chunk-ACIZ2XQQ.js} +10385 -7026
- package/dist/{dashboard-3WCED6AO.js → dashboard-7YGTCNL2.js} +109 -193
- package/dist/main.js +19506 -18860
- package/man/mend-access-keys-create.1 +27 -0
- package/man/mend-access-keys-list.1 +17 -0
- package/man/mend-access-keys-revoke.1 +15 -0
- package/man/mend-accounts.1 +1 -1
- package/man/mend-adopt.1 +6 -1
- package/man/mend-agent-install.1 +15 -0
- package/man/mend-agent-logins.1 +1 -1
- package/man/mend-attach.1 +1 -1
- package/man/mend-change.1 +18 -0
- package/man/mend-codex.1 +9 -1
- package/man/mend-comment-add.1 +24 -0
- package/man/mend-comment-send.1 +18 -0
- package/man/mend-completions.1 +1 -1
- package/man/mend-connect-executor.1 +24 -0
- package/man/mend-connect-pi.1 +4 -1
- package/man/mend-connect-status.1 +15 -0
- package/man/mend-connect.1 +36 -1
- package/man/mend-continue.1 +1 -1
- package/man/mend-diff.1 +24 -0
- package/man/mend-doctor.1 +12 -3
- package/man/mend-doppler-connect.1 +11 -0
- package/man/mend-doppler-disconnect.1 +11 -0
- package/man/mend-doppler-status.1 +11 -0
- package/man/mend-doppler-use.1 +15 -0
- package/man/mend-doppler.1 +15 -0
- package/man/mend-dotfiles-repo.1 +1 -1
- package/man/mend-dotfiles-sync.1 +1 -1
- package/man/mend-dotfiles.1 +1 -1
- package/man/mend-env-cluster.1 +1 -1
- package/man/mend-env-load.1 +1 -1
- package/man/mend-env-show.1 +1 -1
- package/man/mend-folder-create.1 +1 -1
- package/man/mend-folder-list.1 +1 -1
- package/man/mend-folder-push.1 +1 -1
- package/man/mend-folder-rm.1 +1 -1
- package/man/mend-git-author.1 +1 -1
- package/man/mend-git-check.1 +20 -0
- package/man/mend-handoff.1 +1 -1
- package/man/mend-help.1 +5 -1
- package/man/mend-history.1 +18 -0
- package/man/mend-interrupt.1 +15 -0
- package/man/mend-invite.1 +3 -3
- package/man/mend-keys-init.1 +1 -1
- package/man/mend-keys-mode.1 +2 -2
- package/man/mend-keys-share.1 +1 -1
- package/man/mend-keys-show.1 +1 -1
- package/man/mend-land.1 +6 -3
- package/man/mend-login.1 +8 -2
- package/man/mend-logout.1 +6 -2
- package/man/mend-logs.1 +1 -1
- package/man/mend-man.1 +1 -1
- package/man/mend-mcp-add.1 +45 -0
- package/man/mend-mcp-forget.1 +18 -0
- package/man/mend-mcp-off.1 +18 -0
- package/man/mend-mcp-on.1 +18 -0
- package/man/mend-mcp-remove.1 +18 -0
- package/man/mend-mcp.1 +24 -0
- package/man/mend-members.1 +3 -3
- package/man/mend-memory-import.1 +1 -1
- package/man/mend-memory-rm.1 +1 -1
- package/man/mend-memory-show.1 +1 -1
- package/man/mend-memory.1 +1 -1
- package/man/mend-message.1 +6 -3
- package/man/mend-models.1 +1 -1
- package/man/mend-operator-exposure.1 +1 -1
- package/man/mend-operator-gate.1 +1 -1
- package/man/mend-operator-grant-owner.1 +2 -2
- package/man/mend-operator-org-add-member.1 +20 -0
- package/man/mend-operator-org-create.1 +1 -1
- package/man/mend-operator-org-invite-owner.1 +2 -2
- package/man/mend-operator-org-list.1 +2 -2
- package/man/mend-operator-org-rename.1 +1 -1
- package/man/mend-operator-reset-link.1 +1 -1
- package/man/mend-org-leave.1 +17 -0
- package/man/mend-org-switch.1 +14 -0
- package/man/mend-org.1 +15 -0
- package/man/mend-pair.1 +1 -1
- package/man/mend-preview.1 +31 -0
- package/man/mend-projects-image.1 +20 -0
- package/man/mend-projects-purge.1 +18 -0
- package/man/mend-projects-removed.1 +15 -0
- package/man/mend-projects-restore.1 +18 -0
- package/man/mend-projects-rm.1 +15 -0
- package/man/mend-projects.1 +3 -3
- package/man/mend-proof-get.1 +21 -0
- package/man/mend-proof-list.1 +15 -0
- package/man/mend-pull.1 +1 -1
- package/man/mend-refresh.1 +1 -1
- package/man/mend-rejoin.1 +1 -1
- package/man/mend-resource-add.1 +17 -25
- package/man/mend-resource-env.1 +21 -0
- package/man/mend-resource-list.1 +10 -12
- package/man/mend-resource-load.1 +33 -0
- package/man/mend-resource-remove.1 +16 -16
- package/man/mend-resource-reset.1 +24 -0
- package/man/mend-resource-start.1 +28 -7
- package/man/mend-resource-stop.1 +27 -0
- package/man/mend-resource-use.1 +12 -9
- package/man/mend-respond.1 +21 -0
- package/man/mend-resume.1 +1 -1
- package/man/mend-run.1 +1 -1
- package/man/mend-screen-look.1 +21 -0
- package/man/mend-secrets-add.1 +1 -1
- package/man/mend-secrets-rm.1 +1 -1
- package/man/mend-secrets.1 +1 -1
- package/man/mend-server-logs.1 +1 -1
- package/man/mend-server-restart.1 +1 -1
- package/man/mend-server-setup.1 +46 -1
- package/man/mend-server-start.1 +1 -1
- package/man/mend-server-status.1 +8 -1
- package/man/mend-server-stop.1 +1 -1
- package/man/mend-server-upgrade.1 +1 -1
- package/man/mend-server.1 +1 -1
- package/man/mend-service-add.1 +1 -1
- package/man/mend-service-connect.1 +1 -1
- package/man/mend-service-init.1 +3 -3
- package/man/mend-service-list.1 +3 -3
- package/man/mend-service-logs.1 +1 -1
- package/man/mend-service-restart.1 +1 -1
- package/man/mend-service-run.1 +4 -4
- package/man/mend-service-stop.1 +1 -1
- package/man/mend-session-share.1 +2 -2
- package/man/mend-sessions.1 +2 -2
- package/man/mend-settings.1 +1 -1
- package/man/mend-setup-session.1 +25 -0
- package/man/mend-shell.1 +1 -1
- package/man/mend-skills-push.1 +1 -1
- package/man/mend-skills.1 +1 -1
- package/man/mend-snake.1 +1 -1
- package/man/mend-ssh-keys-remove.1 +1 -1
- package/man/mend-ssh-keys.1 +1 -1
- package/man/mend-ssh-setup.1 +1 -1
- package/man/mend-ssh.1 +1 -1
- package/man/mend-stop.1 +4 -1
- package/man/mend-ui.1 +1 -1
- package/man/mend-uninstall.1 +1 -1
- package/man/mend-version.1 +1 -1
- package/man/mend-wait.1 +4 -1
- package/man/mend-workspace-replace.1 +2 -2
- package/man/mend-worktrees-rm.1 +1 -1
- package/man/mend-worktrees.1 +1 -1
- package/man/mend.1 +139 -13
- package/package.json +4 -3
- package/man/mend-resource-approve.1 +0 -38
|
@@ -0,0 +1,287 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: mend
|
|
3
|
+
description:
|
|
4
|
+
Set up Mend and run coding work through its CLI. Use for first-time onboarding, conversation
|
|
5
|
+
sessions, steering, review, previews and proof, or handing a session back to the person.
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
<!-- mend-managed-skill:v1 -->
|
|
9
|
+
|
|
10
|
+
# Mend
|
|
11
|
+
|
|
12
|
+
Mend runs the person's coding agent in a recorded git worktree. The same session, record and change
|
|
13
|
+
are visible in the web app, T3 Code, VS Code and the person's terminal. Use the shell and `mend`
|
|
14
|
+
CLI. Mend does not ship an outside-agent MCP server.
|
|
15
|
+
|
|
16
|
+
Read this workflow before onboarding or running work. Run `mend help COMMAND --json` when you need
|
|
17
|
+
the installed version's flag details. Replace uppercase identifiers below with ids returned by Mend.
|
|
18
|
+
Keep the session id, web URL, worktree id and pinned review slice with the task.
|
|
19
|
+
|
|
20
|
+
## Command outcomes
|
|
21
|
+
|
|
22
|
+
Use `--json` for agent-run commands. Parse the v1 envelope, `{"v":1,"status":…,"data":…}`. Login
|
|
23
|
+
also streams authorize and signed-in events. Read every event until the command exits.
|
|
24
|
+
|
|
25
|
+
| Exit | Meaning | Next action |
|
|
26
|
+
| ---- | ---------------------- | ------------------------------------------------------------------------------ |
|
|
27
|
+
| 0 | Done or ready | Continue with the returned ids. |
|
|
28
|
+
| 1 | Failed | Read `error.code`, `message` and `fix`; inspect state before retrying a write. |
|
|
29
|
+
| 2 | Usage or `needs_input` | Supply the named argument or flag. No picker runs without a terminal. |
|
|
30
|
+
| 3 | Waiting on the person | Show the pending request or approval URL and wait for their answer. |
|
|
31
|
+
| 4 | Not ready | Resolve the named blocking items and recheck. |
|
|
32
|
+
| 124 | Timed out | Inspect state; accepted sessions and resources keep running. |
|
|
33
|
+
|
|
34
|
+
Set `--timeout` on waits. A timeout is not permission to repeat a write. Report observations,
|
|
35
|
+
including uncertainty, and link the session. Say "Turn completed, observed" and what changed. Mend's
|
|
36
|
+
findings and captures are evidence for the person to assess.
|
|
37
|
+
|
|
38
|
+
Keep credentials inside their owning CLI. Never read Mend's credential file, print or request a
|
|
39
|
+
token, type a password, or place a credential in an argument. The person opens authorization links,
|
|
40
|
+
signs in to each provider once, and decides whether to add a public deploy key. Forward permission
|
|
41
|
+
and question requests to them. Send only the answer they give; never approve on their behalf.
|
|
42
|
+
|
|
43
|
+
## 1. First contact
|
|
44
|
+
|
|
45
|
+
For "Set me up on Mend", fetch `https://mend.run/agent.md`, then install the CLI and skill.
|
|
46
|
+
|
|
47
|
+
```sh
|
|
48
|
+
npm i -g @sealant/mend
|
|
49
|
+
mend agent install --json
|
|
50
|
+
```
|
|
51
|
+
|
|
52
|
+
Read a returned `SKILL.md` path. Installation finds existing `~/.claude`, `~/.codex` and
|
|
53
|
+
`~/.pi/agent` homes and installs the same skill into each. If Node is too old, upgrade to the
|
|
54
|
+
version named by the error and retry. If a custom Mend skill occupies a destination, preserve it at
|
|
55
|
+
another path before retrying.
|
|
56
|
+
|
|
57
|
+
## 2. Pick a server
|
|
58
|
+
|
|
59
|
+
Ask one question, "Run Mend on this machine, or connect to a server you already have?" For this
|
|
60
|
+
machine, ask for the account email and display name and run the fresh-server setup below. For an
|
|
61
|
+
existing server, take its URL and proceed to sign-in. For a server the person can reach with SSH,
|
|
62
|
+
run the same install and setup on that host using their existing SSH access. Setup stays on that
|
|
63
|
+
host; afterward sign the local CLI in to its reachable URL. Use setup's reported fixes for Docker,
|
|
64
|
+
user namespaces, ports or exposure. Do not declare readiness while blocking items remain.
|
|
65
|
+
|
|
66
|
+
## 3. Sign in and create the first account
|
|
67
|
+
|
|
68
|
+
On a fresh server, create the first account without a password passing through the agent.
|
|
69
|
+
|
|
70
|
+
```sh
|
|
71
|
+
mend server setup --yes --account-email person@example.com --account-name "Person" --json
|
|
72
|
+
mend server status --json
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
Substitute the person's email and name. Same-machine setup signs the local CLI in directly. Give the
|
|
76
|
+
person the returned one-time web password link privately so they can set their own web password in
|
|
77
|
+
their browser. Treat this link as a one-time approval capability, never as a reusable credential. Do
|
|
78
|
+
not open or redeem it yourself. Setup over SSH creates the same account but does not sign the CLI on
|
|
79
|
+
your machine in.
|
|
80
|
+
|
|
81
|
+
For an existing server or a separate local CLI, run:
|
|
82
|
+
|
|
83
|
+
```sh
|
|
84
|
+
mend login --url https://mend.example.com --timeout 10m --json
|
|
85
|
+
```
|
|
86
|
+
|
|
87
|
+
Show the first `authorize` event's URL and device code to the person. They click Authorize. Keep
|
|
88
|
+
reading until `signed-in` and exit 0. On denial, expiry or timeout, follow the reported fix and run
|
|
89
|
+
login again when the person is ready. Do not invent an account or automate their sign-in.
|
|
90
|
+
|
|
91
|
+
## 4. Adopt the repository and check Git
|
|
92
|
+
|
|
93
|
+
Run inside the person's checkout, or give adopt its network Git URL.
|
|
94
|
+
|
|
95
|
+
```sh
|
|
96
|
+
mend adopt --json
|
|
97
|
+
mend git check --project PROJECT --json
|
|
98
|
+
```
|
|
99
|
+
|
|
100
|
+
Keep the returned project id. Report read and push as observed, with the transport's reason. For a
|
|
101
|
+
duplicate name, use the existing project or supply `--name` with a new name. For auth failures, show
|
|
102
|
+
the public deploy key and ask "Add Mend's deploy key to OWNER/REPO?" Only after their explicit yes,
|
|
103
|
+
write the returned public key to a file and use their already signed-in `gh`:
|
|
104
|
+
|
|
105
|
+
```sh
|
|
106
|
+
gh repo deploy-key add PUBLIC_KEY_FILE --repo OWNER/REPO --allow-write --title Mend
|
|
107
|
+
```
|
|
108
|
+
|
|
109
|
+
If `gh` is not signed in, give the person the repository's deploy-key settings link. Re-run Git
|
|
110
|
+
check afterward. DNS, network and timeout failures need their own reported fixes; adding a key does
|
|
111
|
+
not repair them.
|
|
112
|
+
|
|
113
|
+
## 5. Connect the person's agent logins
|
|
114
|
+
|
|
115
|
+
```sh
|
|
116
|
+
mend connect status --json
|
|
117
|
+
mend connect claude --timeout 10m --json
|
|
118
|
+
```
|
|
119
|
+
|
|
120
|
+
Choose the requested provider, for example `mend connect codex --timeout 10m --json`. Show its
|
|
121
|
+
authorize event and let the person sign in once. The provider CLI stores its credential privately
|
|
122
|
+
and Mend imports it without printing it. For pi, connect Codex and use `mend connect pi --json` to
|
|
123
|
+
save the local pi profile; follow the reported fix if no profile exists.
|
|
124
|
+
|
|
125
|
+
If the person explicitly chooses an API key and gives its file location, pipe it directly without
|
|
126
|
+
reading or printing it:
|
|
127
|
+
|
|
128
|
+
```sh
|
|
129
|
+
mend connect claude --api-key --json < KEY_FILE
|
|
130
|
+
```
|
|
131
|
+
|
|
132
|
+
## 6. Check readiness
|
|
133
|
+
|
|
134
|
+
```sh
|
|
135
|
+
mend doctor --harness codex --project PROJECT --json
|
|
136
|
+
```
|
|
137
|
+
|
|
138
|
+
Use the person's chosen harness. Readiness requires a reachable server, your Mend sign-in, that
|
|
139
|
+
harness's selected login on the server, and working Git for this project. A Codex-only person needs
|
|
140
|
+
Codex connected on the server. They need no Claude login or local agent CLI credentials. GitHub
|
|
141
|
+
login matters only when they want to land through GitHub.
|
|
142
|
+
|
|
143
|
+
Read every item's state and fix. `info` items are advisory, including unused providers and local CLI
|
|
144
|
+
credentials. Resolve blocking `todo` or `failed` items. Say "Mend is ready" on exit 0.
|
|
145
|
+
|
|
146
|
+
## 7. Start and observe a conversation
|
|
147
|
+
|
|
148
|
+
Use the person's chosen harness, Claude, Codex or pi, and their actual request.
|
|
149
|
+
|
|
150
|
+
```sh
|
|
151
|
+
mend claude --detach --conversation --project PROJECT --json "Fix the flaky login test"
|
|
152
|
+
mend wait SESSION --turn --timeout 10m --json
|
|
153
|
+
mend history SESSION --json
|
|
154
|
+
```
|
|
155
|
+
|
|
156
|
+
Find active or settled sessions with `mend sessions --all --project PROJECT --json`. Save the
|
|
157
|
+
returned session id, worktree, branch and web link. To read a turn and every later turn, use
|
|
158
|
+
`mend history SESSION --since TURN --json` with a full turn id from history. On exit 3, show the
|
|
159
|
+
person the pending question or permission, including its options and scope. Use their explicit
|
|
160
|
+
response only:
|
|
161
|
+
|
|
162
|
+
```sh
|
|
163
|
+
mend respond REQUEST --decision accept --json
|
|
164
|
+
mend respond REQUEST --answers '{"QUESTION_ID":["Their answer"]}' --json
|
|
165
|
+
```
|
|
166
|
+
|
|
167
|
+
Use the appropriate decision, `accept`, `accept-for-session`, `decline` or `cancel`, only as the
|
|
168
|
+
person directed. For questions use the returned question ids and their words. Then wait again.
|
|
169
|
+
Report the observed result and files touched with the session link.
|
|
170
|
+
|
|
171
|
+
## 8. Steer, resume, interrupt or stop
|
|
172
|
+
|
|
173
|
+
```sh
|
|
174
|
+
mend message SESSION "Also cover the Safari case" --json
|
|
175
|
+
mend message SESSION "Continue with the agreed fix" --resume --json
|
|
176
|
+
mend wait SESSION --turn --timeout 10m --json
|
|
177
|
+
mend interrupt SESSION --json
|
|
178
|
+
mend stop SESSION --json
|
|
179
|
+
mend stop SESSION --services --json
|
|
180
|
+
```
|
|
181
|
+
|
|
182
|
+
Use message for the person's follow-up; it queues while busy. Use `--resume` when the session
|
|
183
|
+
stopped. Interrupt stops the current turn; stop stops the session. Choose the action the person
|
|
184
|
+
asked for, then inspect history for what happened. Services keep running after an agent stop. Stop
|
|
185
|
+
them with `--services` only when the person asks.
|
|
186
|
+
|
|
187
|
+
## 9. Review and send the person's comments back
|
|
188
|
+
|
|
189
|
+
```sh
|
|
190
|
+
mend change SESSION --json
|
|
191
|
+
mend diff SESSION --slice SLICE --json
|
|
192
|
+
mend comment add SESSION src/auth.ts:42 "This swallows the error" --slice SLICE --json
|
|
193
|
+
mend comment send SESSION --slice SLICE --json
|
|
194
|
+
mend wait SESSION --turn --timeout 10m --json
|
|
195
|
+
```
|
|
196
|
+
|
|
197
|
+
Keep the slice returned by change so the patch and comment refer to what the person saw. Change
|
|
198
|
+
includes files, stats, checkpoints, draft findings, proposed checks and record evidence. Walk the
|
|
199
|
+
person through them; findings remain observations. Use `--side old` for removed lines, `--change`
|
|
200
|
+
for a whole-change remark, or `path:start-end` for a range. To compare checkpoints use
|
|
201
|
+
`mend diff SESSION --from CHECKPOINT_A --to CHECKPOINT_B --json` and inspect truncation fields.
|
|
202
|
+
Comment send bundles unsent open reviewer comments and returns without attaching. It does not
|
|
203
|
+
approve Mend's draft findings. On an uncertain delivery, retry the same command to reconcile the
|
|
204
|
+
saved bundle and request key before sending anything else.
|
|
205
|
+
|
|
206
|
+
## 10. Land when requested
|
|
207
|
+
|
|
208
|
+
```sh
|
|
209
|
+
mend land SESSION --json
|
|
210
|
+
```
|
|
211
|
+
|
|
212
|
+
Report what was pushed, its checkpoint and commit, the pull request URL and GitHub's last observed
|
|
213
|
+
state. A failed pull-request step can follow a successful push; preserve both facts. Mend never
|
|
214
|
+
merges. If the person asks for a merge, use their normal GitHub workflow with `gh` outside Mend.
|
|
215
|
+
|
|
216
|
+
## 11. Resources, Services, previews, screens and proof
|
|
217
|
+
|
|
218
|
+
When the work needs Postgres or another resource, have the session's agent write the named resource
|
|
219
|
+
such as `@db` into its `.mend/mend.toml` through an ordinary message. Wait for that turn and read
|
|
220
|
+
the change to obtain its project and worktree ids. Then explicitly start the intended level:
|
|
221
|
+
|
|
222
|
+
```sh
|
|
223
|
+
mend resource list --project-id PROJECT --worktree-id WORKTREE --json
|
|
224
|
+
mend resource add db --preset postgres --version 17 --project-id PROJECT --worktree-id WORKTREE --json
|
|
225
|
+
mend resource start db --project --project-id PROJECT --worktree-id WORKTREE --wait --timeout 10m --json
|
|
226
|
+
mend resource env --project-id PROJECT --worktree-id WORKTREE --json
|
|
227
|
+
mend service list SESSION --json
|
|
228
|
+
mend preview SESSION --json
|
|
229
|
+
mend screen look SESSION --out shot.png --timeout 30s --json
|
|
230
|
+
mend proof list SESSION --json
|
|
231
|
+
mend proof get PROOF --out proof.png --timeout 5m --json
|
|
232
|
+
```
|
|
233
|
+
|
|
234
|
+
Use `--worktree` for a separate worktree resource. If a changed definition needs a restart, show the
|
|
235
|
+
named affected worktrees and get the person's consent before passing `--restart`. Service listing
|
|
236
|
+
reports attempts, forwarding and target observations separately. If a preview is not ready, ask the
|
|
237
|
+
session's agent to start its declared Service and recheck. Give the person the Preview tab link for
|
|
238
|
+
their own browser sign-in. Do not request or pass preview tickets.
|
|
239
|
+
|
|
240
|
+
Resource add writes a declaration without starting anything. Resource env lists names without
|
|
241
|
+
revealing values. When the person asks to stop a resource or load a dump, use the explicit project,
|
|
242
|
+
worktree and level. A load saves the previous database first; inspect a timed-out load before
|
|
243
|
+
starting another.
|
|
244
|
+
|
|
245
|
+
```sh
|
|
246
|
+
mend resource stop db --project --project-id PROJECT --worktree-id WORKTREE --json
|
|
247
|
+
mend resource load db --from DUMP_FILE --target shared --project-id PROJECT --worktree-id WORKTREE --timeout 10m --json
|
|
248
|
+
mend projects image PROJECT --json
|
|
249
|
+
```
|
|
250
|
+
|
|
251
|
+
If screen look returns `ScreenObservationUnavailable`, read the effective image. If Screen is off,
|
|
252
|
+
enable it, then start a new session in a new worktree before observing again:
|
|
253
|
+
|
|
254
|
+
```sh
|
|
255
|
+
mend projects image PROJECT --screen on --json
|
|
256
|
+
```
|
|
257
|
+
|
|
258
|
+
The screen flag preserves the rest of the image. A custom image needs a family image selected in
|
|
259
|
+
project environment settings first. If Screen is already on, follow the reported screen-start
|
|
260
|
+
failure instead of repeating the setting.
|
|
261
|
+
|
|
262
|
+
Screen look only observes. The session's own agent drives the screen; the person takes over in Mend.
|
|
263
|
+
An outside agent never drives it or impersonates the session's agent. Proof list/get read
|
|
264
|
+
screenshots and videos already captured in the session, with checkpoint or unknown source and
|
|
265
|
+
observation times. Choose a new output path for each download. Show the saved media to the person
|
|
266
|
+
and describe what it captured, without treating the image as proof that the change works.
|
|
267
|
+
|
|
268
|
+
## 12. Hand the session to the person
|
|
269
|
+
|
|
270
|
+
At any point give the person the session's web link. For their own interactive terminal they can run
|
|
271
|
+
`mend attach SESSION`. They can also open that same session in T3 Code or VS Code. Keep the record
|
|
272
|
+
and change links with the handover so they can inspect everything done so far.
|
|
273
|
+
|
|
274
|
+
When the person asks to clean up, list projects and stop their work before removal. Removal keeps
|
|
275
|
+
files and history. Permanent deletion requires their request and the exact name, and can be refused
|
|
276
|
+
until uploads finish. Follow the structured error before retrying.
|
|
277
|
+
|
|
278
|
+
```sh
|
|
279
|
+
mend projects --json
|
|
280
|
+
mend projects rm PROJECT --json
|
|
281
|
+
mend projects removed --json
|
|
282
|
+
mend projects restore PROJECT --json
|
|
283
|
+
mend projects purge PROJECT --confirm PROJECT_NAME --json
|
|
284
|
+
```
|
|
285
|
+
|
|
286
|
+
When the person asks to sign this CLI out, run `mend logout --json`. Read local sign-out and server
|
|
287
|
+
revocation separately. If revocation is unconfirmed, give them the reported fix.
|