@sealant/mend 0.36.0-next.773 → 0.36.0-next.783
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/main.js +662 -94
- package/man/mend-accounts.1 +1 -1
- package/man/mend-adopt.1 +1 -1
- package/man/mend-attach.1 +1 -1
- package/man/mend-codex.1 +1 -1
- package/man/mend-completions.1 +1 -1
- package/man/mend-connect-pi.1 +1 -1
- package/man/mend-connect.1 +1 -1
- package/man/mend-continue.1 +1 -1
- package/man/mend-doctor.1 +2 -2
- 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-help.1 +1 -1
- package/man/mend-invite.1 +1 -1
- package/man/mend-keys-init.1 +1 -1
- package/man/mend-keys-mode.1 +1 -1
- package/man/mend-keys-share.1 +1 -1
- package/man/mend-keys-show.1 +1 -1
- package/man/mend-land.1 +1 -1
- package/man/mend-login.1 +1 -1
- package/man/mend-logout.1 +1 -1
- package/man/mend-logs.1 +1 -1
- package/man/mend-man.1 +1 -1
- package/man/mend-members.1 +1 -1
- 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-models.1 +2 -2
- package/man/mend-operator-exposure.1 +1 -1
- package/man/mend-operator-gate.1 +1 -1
- package/man/mend-operator-grant-owner.1 +1 -1
- package/man/mend-operator-org-create.1 +1 -1
- package/man/mend-operator-org-invite-owner.1 +1 -1
- package/man/mend-operator-org-list.1 +1 -1
- package/man/mend-operator-org-rename.1 +1 -1
- package/man/mend-operator-reset-link.1 +1 -1
- package/man/mend-pair.1 +3 -1
- package/man/mend-projects.1 +1 -1
- package/man/mend-pull.1 +1 -1
- package/man/mend-refresh.1 +1 -1
- package/man/mend-rejoin.1 +1 -1
- package/man/mend-resume.1 +1 -1
- package/man/mend-run.1 +1 -1
- 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 +19 -9
- package/man/mend-server-start.1 +1 -1
- package/man/mend-server-status.1 +1 -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 +1 -1
- package/man/mend-service-list.1 +1 -1
- package/man/mend-service-logs.1 +1 -1
- package/man/mend-service-restart.1 +1 -1
- package/man/mend-service-run.1 +1 -1
- package/man/mend-service-stop.1 +1 -1
- package/man/mend-session-share.1 +1 -1
- package/man/mend-sessions.1 +1 -1
- 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 +1 -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 +1 -1
- package/man/mend-workspace-replace.1 +1 -1
- package/man/mend-worktrees-rm.1 +1 -1
- package/man/mend-worktrees.1 +1 -1
- package/man/mend.1 +1 -1
- package/package.json +2 -2
package/man/mend-accounts.1
CHANGED
package/man/mend-adopt.1
CHANGED
package/man/mend-attach.1
CHANGED
package/man/mend-codex.1
CHANGED
package/man/mend-completions.1
CHANGED
package/man/mend-connect-pi.1
CHANGED
package/man/mend-connect.1
CHANGED
package/man/mend-continue.1
CHANGED
package/man/mend-doctor.1
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
.TH MEND-DOCTOR 1 "" "mend 0.36.0\-next.
|
|
1
|
+
.TH MEND-DOCTOR 1 "" "mend 0.36.0\-next.783" "mend manual"
|
|
2
2
|
.SH NAME
|
|
3
3
|
mend\-doctor \- check this machine's setup, or bundle it for a bug report
|
|
4
4
|
.SH SYNOPSIS
|
|
@@ -8,7 +8,7 @@ mend\-doctor \- check this machine's setup, or bundle it for a bug report
|
|
|
8
8
|
.br
|
|
9
9
|
.SH DESCRIPTION
|
|
10
10
|
.PP
|
|
11
|
-
Read\-only. One line per fact: the server, the sign\-in, the platform connection, the provider accounts, the
|
|
11
|
+
Read\-only. One line per fact: the server, the sign\-in, the platform connection, the provider accounts, the adopted projects, the claude, codex and gh CLIs on this machine, the exposure, the server's clock against this machine's, a Mac that sleeps on its own or when its lid closes, and where docker is on PATH what a stop of its daemon waits for against what systemd allows docker.service. Each unfinished line ends with the command that fixes it.
|
|
12
12
|
.PP
|
|
13
13
|
\-\-bundle collects what a maintainer asks for one output at a time into one tar.gz: this CLI and its environment, the doctor lines, the server's health, the local server's configuration (its compose file and the names of its .env keys, never their values), docker version, info, contexts, the Mend and workspace containers with their inspect facts, the local server's container logs, the running workspace containers' logs, every session with its processes, exit codes and argv, the recorded terminal output of each, the connected accounts, and the versions and paths of claude, codex, gh, git and docker on this machine.
|
|
14
14
|
.PP
|
package/man/mend-dotfiles-repo.1
CHANGED
package/man/mend-dotfiles-sync.1
CHANGED
package/man/mend-dotfiles.1
CHANGED
package/man/mend-env-cluster.1
CHANGED
package/man/mend-env-load.1
CHANGED
package/man/mend-env-show.1
CHANGED
package/man/mend-folder-create.1
CHANGED
package/man/mend-folder-list.1
CHANGED
package/man/mend-folder-push.1
CHANGED
package/man/mend-folder-rm.1
CHANGED
package/man/mend-git-author.1
CHANGED
package/man/mend-help.1
CHANGED
package/man/mend-invite.1
CHANGED
package/man/mend-keys-init.1
CHANGED
package/man/mend-keys-mode.1
CHANGED
package/man/mend-keys-share.1
CHANGED
package/man/mend-keys-show.1
CHANGED
package/man/mend-land.1
CHANGED
package/man/mend-login.1
CHANGED
package/man/mend-logout.1
CHANGED
package/man/mend-logs.1
CHANGED
package/man/mend-man.1
CHANGED
package/man/mend-members.1
CHANGED
package/man/mend-memory-import.1
CHANGED
package/man/mend-memory-rm.1
CHANGED
package/man/mend-memory-show.1
CHANGED
package/man/mend-memory.1
CHANGED
package/man/mend-models.1
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
.TH MEND-MODELS 1 "" "mend 0.36.0\-next.
|
|
1
|
+
.TH MEND-MODELS 1 "" "mend 0.36.0\-next.783" "mend manual"
|
|
2
2
|
.SH NAME
|
|
3
3
|
mend\-models \- the models each harness offers, as the server lists them
|
|
4
4
|
.SH SYNOPSIS
|
|
@@ -6,7 +6,7 @@ mend\-models \- the models each harness offers, as the server lists them
|
|
|
6
6
|
.br
|
|
7
7
|
.SH DESCRIPTION
|
|
8
8
|
.PP
|
|
9
|
-
One block per harness: each model's id, the one a launch runs when \-\-model is not given, and the efforts a model takes where they are fewer than the harness's. The list is the server's; the phone, the web app
|
|
9
|
+
One block per harness: each model's id, the one a launch runs when \-\-model is not given, and the efforts a model takes where they are fewer than the harness's. The list is the server's; the phone, the web app and VS Code offer the same one, and a session records which model it was started with.
|
|
10
10
|
.PP
|
|
11
11
|
Pass an id to mend claude or mend codex with \-\-model. An id the list does not know is passed through as given; the harness decides whether it exists.
|
|
12
12
|
.SH OPTIONS
|
package/man/mend-operator-gate.1
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
.TH MEND-OPERATOR-ORG-INVITE-OWNER 1 "" "mend 0.36.0\-next.
|
|
1
|
+
.TH MEND-OPERATOR-ORG-INVITE-OWNER 1 "" "mend 0.36.0\-next.783" "mend manual"
|
|
2
2
|
.SH NAME
|
|
3
3
|
mend\-operator\-org\-invite\-owner \- print a one\-time owner invitation for an organization
|
|
4
4
|
.SH SYNOPSIS
|
package/man/mend-pair.1
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
.TH MEND-PAIR 1 "" "mend 0.36.0\-next.
|
|
1
|
+
.TH MEND-PAIR 1 "" "mend 0.36.0\-next.783" "mend manual"
|
|
2
2
|
.SH NAME
|
|
3
3
|
mend\-pair \- pair a phone or a second machine
|
|
4
4
|
.SH SYNOPSIS
|
|
@@ -7,6 +7,8 @@ mend\-pair \- pair a phone or a second machine
|
|
|
7
7
|
.SH DESCRIPTION
|
|
8
8
|
.PP
|
|
9
9
|
Prints a QR code, the code itself, and the URL this server is reached at. The pairing is for one device, once, and expires after 10 minutes.
|
|
10
|
+
.PP
|
|
11
|
+
With the server's T3 Code gateway on, it also prints the gateway's address: in T3 Code, add a Remote link with that address and the code, or paste the link it prints, which carries both. The same code pairs T3 Code or the Mend app, once. T3 Code's SSH mode is not for Mend: it starts T3 Code's own server on the other machine.
|
|
10
12
|
.SH OPTIONS
|
|
11
13
|
.TP
|
|
12
14
|
.B \-\-url <base url>
|
package/man/mend-projects.1
CHANGED
package/man/mend-pull.1
CHANGED
package/man/mend-refresh.1
CHANGED
package/man/mend-rejoin.1
CHANGED
package/man/mend-resume.1
CHANGED
package/man/mend-run.1
CHANGED
package/man/mend-secrets-add.1
CHANGED
package/man/mend-secrets-rm.1
CHANGED
package/man/mend-secrets.1
CHANGED
package/man/mend-server-logs.1
CHANGED
package/man/mend-server-setup.1
CHANGED
|
@@ -1,16 +1,16 @@
|
|
|
1
|
-
.TH MEND-SERVER-SETUP 1 "" "mend 0.36.0\-next.
|
|
1
|
+
.TH MEND-SERVER-SETUP 1 "" "mend 0.36.0\-next.783" "mend manual"
|
|
2
2
|
.SH NAME
|
|
3
3
|
mend\-server\-setup \- install or change the local Mend server, guided
|
|
4
4
|
.SH SYNOPSIS
|
|
5
5
|
.B mend server setup
|
|
6
6
|
.br
|
|
7
|
-
.B mend server setup [\-\-yes] [\-\-context <name>] [\-\-version <version|latest>] [\-\-bind <ip>] [\-\-ssh\-bind <ip>] [\-\-url <origin>] [\-\-origin <origin>...] [\-\-port <n>] [\-\-ssh\-port <n>] [\-\-edge <host> | \-\-no\-edge] [\-\-exposure <loopback|private|public>] [\-\-tenancy <single|multi>] [\-\-declare <item>...] [\-\-undeclare <item>...] [\-\-t3\-gateway [\-\-t3\-gateway\-port <n>] | \-\-no\-t3\-gateway] [\-\-npm\-mirror | \-\-no\-npm\-mirror] [\-\-npm\-mirror\-max\-size <size>] [\-\-docker\-mirror | \-\-no\-docker\-mirror] [\-\-docker\-mirror\-max\-size <size>] [\-\-docker\-hub\-username <name> \-\-docker\-hub\-token\-stdin \-\-docker\-hub\-public\-only | \-\-no\-docker\-hub\-login] [\-\-docker\-socket <path>] [\-\-assets\-dir <dir>] [\-\-offline] [\-\-allow\-userns | \-\-no\-allow\-userns]
|
|
7
|
+
.B mend server setup [\-\-yes] [\-\-context <name>] [\-\-version <version|latest>] [\-\-bind <ip>] [\-\-ssh\-bind <ip>] [\-\-url <origin>] [\-\-origin <origin>...] [\-\-port <n>] [\-\-ssh\-port <n>] [\-\-edge <host> | \-\-no\-edge] [\-\-exposure <loopback|private|public>] [\-\-tenancy <single|multi>] [\-\-declare <item>...] [\-\-undeclare <item>...] [\-\-t3\-gateway [\-\-t3\-gateway\-port <n>] [\-\-t3\-gateway\-origin <host> | \-\-no\-t3\-gateway\-origin] | \-\-no\-t3\-gateway] [\-\-npm\-mirror | \-\-no\-npm\-mirror] [\-\-npm\-mirror\-max\-size <size>] [\-\-docker\-mirror | \-\-no\-docker\-mirror] [\-\-docker\-mirror\-max\-size <size>] [\-\-docker\-hub\-username <name> \-\-docker\-hub\-token\-stdin \-\-docker\-hub\-public\-only | \-\-no\-docker\-hub\-login] [\-\-docker\-socket <path>] [\-\-assets\-dir <dir>] [\-\-offline] [\-\-allow\-userns | \-\-no\-allow\-userns]
|
|
8
8
|
.br
|
|
9
9
|
.SH DESCRIPTION
|
|
10
10
|
.PP
|
|
11
|
-
On a terminal with no flags, setup asks its questions in plain words, one at a time: how people reach this Mend (just this machine, your private network or Tailscale, or the public internet with HTTPS), whether VS Code Remote\-SSH reaches it from other machines, the T3 Code gateway, the mirrors, and one organization or several. It looks before it asks and says what it observed: Tailscale's name and address and what Tailscale Serve forwards, where your domain resolves, and whether ports 80 and 443 are taken. It never asks for an address to bind: that follows from the answers. On an existing install it shows what is saved and lets you keep it, change one thing, or go through every question. It ends with what changes, in words, and the same command with flags; nothing applies until you say yes.
|
|
11
|
+
On a terminal with no flags, setup asks its questions in plain words, one at a time: on a fresh install with more than one Docker engine answering here (Docker Desktop beside OrbStack, colima, Rancher Desktop, a rootless Docker), which one Mend runs in, the current context in brackets; then how people reach this Mend (just this machine, your private network or Tailscale, or the public internet with HTTPS), whether VS Code Remote\-SSH reaches it from other machines, the T3 Code gateway, the mirrors, and one organization or several. It looks before it asks and says what it observed: Tailscale's name and address and what Tailscale Serve forwards, where your domain resolves, and whether ports 80 and 443 are taken. It never asks for an address to bind: that follows from the answers. On an existing install it shows what is saved and lets you keep it, change one thing, or go through every question. It ends with what changes, in words, and the same command with flags; nothing applies until you say yes.
|
|
12
12
|
.PP
|
|
13
|
-
Flags are for scripts and CI, and teach what the questions do. Each changes only what it names; everything else is kept from the saved install, so mend server setup \-\-t3\-gateway turns the gateway on and nothing more. When there is an install, a run with flags says what it changes. With no terminal and no flags, a fresh install is refused rather than guessed: \-\-yes takes the defaults. \-\-context and \-\-docker\-socket choose the Docker engine and answer
|
|
13
|
+
Flags are for scripts and CI, and teach what the questions do. Each changes only what it names; everything else is kept from the saved install, so mend server setup \-\-t3\-gateway turns the gateway on and nothing more. When there is an install, a run with flags says what it changes. With no terminal and no flags, a fresh install is refused rather than guessed: \-\-yes takes the defaults. \-\-context and \-\-docker\-socket choose the Docker engine and answer only that question, so with only those (on a Mac with Docker Desktop and OrbStack, \-\-context orbstack) setup still asks the rest. A fresh install without \-\-context takes DOCKER_CONTEXT, as docker does, and with \-\-yes or no terminal the current context, naming the others; an existing one stays on the context its data is on, and running Mend in another engine is a new install (mend uninstall \-\-server, then mend server setup there).
|
|
14
14
|
.PP
|
|
15
15
|
Before anything is pulled, setup checks that Mend's web and SSH ports are free where they are to be published, and says what holds one that is not: another Mend, with its version, or something else. On a terminal it offers the next free port; with flags it refuses and names \-\-port or \-\-ssh\-port. After starting, it reads health until this install answers: its version, and the instance id the server reports, so another Mend on the same port is said as one, never taken for this one.
|
|
16
16
|
.PP
|
|
@@ -20,7 +20,7 @@ The default listens only on localhost at http://localhost:3105. Non\-local acces
|
|
|
20
20
|
.PP
|
|
21
21
|
\-\-edge <host> runs a TLS edge in front of Mend: Caddy on ports 80 and 443 of every interface, which obtains and renews a certificate for the host and proxies to Mend's web tier. Mend's own port stays on loopback and the browser origin is https://<host>. The edge's compose overlay and Caddyfile are written into the generation beside compose.yaml, so start, restart and upgrade run them every time. \-\-no\-edge takes it away again, and the edge's container with it. A fresh install cannot start with the edge: until the first account exists, registration is open to whoever reaches the origin first, so set up on localhost, create the account, then add the edge.
|
|
22
22
|
.PP
|
|
23
|
-
\-\-t3\-gateway turns on the t3code gateway (docs/adr/0012): t3code's desktop, mobile and web clients add it as an environment, pair with a code from mend pair, and see this Mend's projects and sessions. It runs in the Mend container, confined to a root and a uid of its own, on a listener of its own published on 127.0.0.1
|
|
23
|
+
\-\-t3\-gateway turns on the t3code gateway (docs/adr/0012): t3code's desktop, mobile and web clients add it as an environment, pair with a code from mend pair, and see this Mend's projects and sessions. It runs in the Mend container, confined to a root and a uid of its own, on a listener of its own (port 3120, or \-\-t3\-gateway\-port) published where Mend's web port is: on 127.0.0.1 for just this machine, on the tailnet or LAN address for a private network, so T3 Code reaches it as it reaches Mend, with no tunnel. Every device pairs through Mend wherever it is published. Behind the edge its port stays on 127.0.0.1, and \-\-t3\-gateway\-origin <host> has the edge serve it on a host of its own, over HTTPS: a t3code client always uses a server's root path, so it cannot sit under Mend's origin. That host's DNS points where the edge's does; setup says where it resolves. Setup refuses it on a Mend image that has no gateway, and says whether it answered. It is kept across reruns and upgrades; \-\-no\-t3\-gateway turns it off, and its state stays in its own volume, mend\-t3\-gateway. Off, nothing of it runs.
|
|
24
24
|
.PP
|
|
25
25
|
\-\-exposure declares how the instance is reached, and \-\-tenancy whether one organization or many use it. Both are written into the generation and kept across reruns and upgrades. public needs the edge and an existing first account. With multi, or with public, the multi mode gate's settings follow: MEND_SOURCE_POLICY=tenant and MEND_CAPTURE_REQUIRE_SIZES=true, and public sets MEND_URL_BEARERS=refuse. The server still decides whether it starts, and mend server status shows what it reports.
|
|
26
26
|
.PP
|
|
@@ -39,7 +39,7 @@ Setup holds an exclusive process lock through startup and health checks. A busy
|
|
|
39
39
|
no questions: a fresh install takes the defaults (this machine only, http://localhost:3105), an existing one keeps what is saved
|
|
40
40
|
.TP
|
|
41
41
|
.B \-\-context <name>
|
|
42
|
-
local Docker context to persist; the global context is unchanged. Answers
|
|
42
|
+
local Docker context to persist; the global context is unchanged. Answers the engine question. Default: DOCKER_CONTEXT on a fresh install, else the saved one
|
|
43
43
|
.TP
|
|
44
44
|
.B \-\-version <v>
|
|
45
45
|
exact Mend server version, or latest; omitted keeps the current pin
|
|
@@ -69,14 +69,20 @@ run the Caddy TLS edge for this DNS name on 80 and 443; the origin becomes https
|
|
|
69
69
|
take a saved edge away; the origin returns to http://localhost
|
|
70
70
|
.TP
|
|
71
71
|
.B \-\-t3\-gateway
|
|
72
|
-
run the t3code gateway, published
|
|
72
|
+
run the t3code gateway on port 3120, published where Mend's web port is; kept across reruns and upgrades
|
|
73
73
|
.TP
|
|
74
74
|
.B \-\-t3\-gateway\-port <n>
|
|
75
|
-
the gateway's port
|
|
75
|
+
the gateway's port; implies \-\-t3\-gateway
|
|
76
76
|
.TP
|
|
77
77
|
.B \-\-no\-t3\-gateway
|
|
78
78
|
turn the t3code gateway off; its state stays
|
|
79
79
|
.TP
|
|
80
|
+
.B \-\-t3\-gateway\-origin <host>
|
|
81
|
+
with the edge: serve the gateway over HTTPS on this host of its own; its DNS points where the edge's does. Implies \-\-t3\-gateway
|
|
82
|
+
.TP
|
|
83
|
+
.B \-\-no\-t3\-gateway\-origin
|
|
84
|
+
the edge stops serving the gateway; it stays on, on 127.0.0.1
|
|
85
|
+
.TP
|
|
80
86
|
.B \-\-exposure <v>
|
|
81
87
|
declare loopback, private or public; kept across reruns and upgrades. public needs \-\-edge and an existing first account
|
|
82
88
|
.TP
|
|
@@ -135,7 +141,11 @@ on a terminal: the questions, then what changes and the same command with flags
|
|
|
135
141
|
.PP
|
|
136
142
|
.B mend server setup \-\-t3\-gateway
|
|
137
143
|
.br
|
|
138
|
-
on an existing install: turn the T3 Code gateway on, and keep everything else
|
|
144
|
+
on an existing install: turn the T3 Code gateway on where Mend's web port is published, and keep everything else
|
|
145
|
+
.PP
|
|
146
|
+
.B mend server setup \-\-t3\-gateway\-origin t3.mend.example.com
|
|
147
|
+
.br
|
|
148
|
+
behind the edge: serve the T3 Code gateway at https://t3.mend.example.com
|
|
139
149
|
.PP
|
|
140
150
|
.B mend server setup \-\-yes
|
|
141
151
|
.br
|
package/man/mend-server-start.1
CHANGED
package/man/mend-server-status.1
CHANGED
package/man/mend-server-stop.1
CHANGED
package/man/mend-server.1
CHANGED
package/man/mend-service-add.1
CHANGED
package/man/mend-service-init.1
CHANGED
package/man/mend-service-list.1
CHANGED
package/man/mend-service-logs.1
CHANGED