@sealant/mend 0.35.1 → 0.36.0-next.1033
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/README.md +39 -7
- package/dist/chunk-QHWF3YTC.js +24234 -0
- package/dist/{dashboard-MGR4YUFD.js → dashboard-OITCD5JU.js} +1351 -352
- package/dist/main.js +11319 -2034
- package/man/mend-accounts.1 +1 -1
- package/man/mend-adopt.1 +4 -4
- package/man/mend-agent-logins.1 +20 -0
- package/man/mend-attach.1 +1 -1
- package/man/mend-codex.1 +9 -7
- package/man/mend-completions.1 +1 -1
- package/man/mend-connect-pi.1 +28 -0
- package/man/mend-connect.1 +6 -2
- 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 +4 -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 +10 -2
- package/man/mend-logout.1 +1 -1
- package/man/mend-logs.1 +37 -0
- package/man/mend-man.1 +1 -1
- package/man/mend-members.1 +1 -1
- package/man/mend-memory-import.1 +23 -0
- package/man/mend-memory-rm.1 +15 -0
- package/man/mend-memory-show.1 +15 -0
- package/man/mend-memory.1 +32 -0
- package/man/mend-models.1 +22 -0
- package/man/mend-operator-exposure.1 +2 -2
- 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 +10 -2
- package/man/mend-pull.1 +6 -3
- package/man/mend-refresh.1 +6 -2
- package/man/mend-rejoin.1 +1 -1
- package/man/mend-resume.1 +1 -1
- package/man/mend-run.1 +37 -4
- package/man/mend-secrets-add.1 +24 -0
- package/man/mend-secrets-rm.1 +14 -0
- package/man/mend-secrets.1 +18 -0
- package/man/mend-server-logs.1 +1 -1
- package/man/mend-server-restart.1 +1 -1
- package/man/mend-server-setup.1 +125 -8
- package/man/mend-server-start.1 +1 -1
- package/man/mend-server-status.1 +7 -3
- package/man/mend-server-stop.1 +3 -3
- package/man/mend-server-upgrade.1 +14 -2
- 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 +10 -4
- package/man/mend-service-logs.1 +3 -1
- package/man/mend-service-restart.1 +1 -1
- package/man/mend-service-run.1 +16 -4
- package/man/mend-service-stop.1 +1 -1
- package/man/mend-session-share.1 +13 -3
- package/man/mend-sessions.1 +3 -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 +7 -3
- package/man/mend-ssh-keys-remove.1 +18 -0
- package/man/mend-ssh-keys.1 +15 -0
- package/man/mend-ssh-setup.1 +2 -2
- package/man/mend-ssh.1 +17 -4
- package/man/mend-stop.1 +1 -1
- package/man/mend-ui.1 +4 -2
- package/man/mend-uninstall.1 +10 -4
- package/man/mend-version.1 +1 -1
- package/man/mend-wait.1 +28 -0
- package/man/mend-workspace-replace.1 +24 -0
- package/man/mend-worktrees-rm.1 +29 -0
- package/man/mend-worktrees.1 +2 -2
- package/man/mend.1 +61 -7
- package/package.json +22 -41
- package/dist/chunk-SMH65F6Z.js +0 -29007
package/man/mend-accounts.1
CHANGED
package/man/mend-adopt.1
CHANGED
|
@@ -1,21 +1,21 @@
|
|
|
1
|
-
.TH MEND-ADOPT 1 "" "mend 0.
|
|
1
|
+
.TH MEND-ADOPT 1 "" "mend 0.36.0\-next.1033" "mend manual"
|
|
2
2
|
.SH NAME
|
|
3
3
|
mend\-adopt \- adopt a repository into the store
|
|
4
4
|
.SH SYNOPSIS
|
|
5
|
-
.B mend adopt [git\-url] [\-\-name <name>] [\-\-auth
|
|
5
|
+
.B mend adopt [git\-url] [\-\-name <name>] [\-\-auth mend\-key|bridge] [\-\-private|\-\-shared]
|
|
6
6
|
.br
|
|
7
7
|
.SH DESCRIPTION
|
|
8
8
|
.PP
|
|
9
9
|
Clones a network Git repository into Mend's store. Every session then gets its own worktree of it. With no argument, Mend uses the current checkout's origin URL. HTTP(S), SSH, git://, and SCP\-style URLs work; local paths and file:// URLs do not.
|
|
10
10
|
.PP
|
|
11
|
-
\-\-auth says how the store fetches from the remote. Default: your mode from mend keys mode. mend\-key signs with your Mend key on the server (see mend keys). bridge relays this machine's ssh\-agent while a mend command runs here, so hardware keys stay on your desk.
|
|
11
|
+
\-\-auth says how the store fetches from the remote. Default: your mode from mend keys mode. mend\-key signs with your Mend key on the server (see mend keys). bridge relays this machine's ssh\-agent while a mend command runs here, so hardware keys stay on your desk. Both sign ssh remotes: for a private repository, adopt its SSH URL (git@host:owner/repo.git), not its https one.
|
|
12
12
|
.SH OPTIONS
|
|
13
13
|
.TP
|
|
14
14
|
.B \-\-name <name>
|
|
15
15
|
the project's name in Mend. Default: the repository's
|
|
16
16
|
.TP
|
|
17
17
|
.B \-\-auth <mode>
|
|
18
|
-
mend\-key
|
|
18
|
+
mend\-key or bridge. Default: mend keys mode
|
|
19
19
|
.TP
|
|
20
20
|
.B \-\-private
|
|
21
21
|
only you see the project. Default
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
.TH MEND-AGENT-LOGINS 1 "" "mend 0.36.0\-next.1033" "mend manual"
|
|
2
|
+
.SH NAME
|
|
3
|
+
mend\-agent\-logins \- which of your own logins your Claude and Codex sessions get
|
|
4
|
+
.SH SYNOPSIS
|
|
5
|
+
.B mend agent\-logins [all|selected]
|
|
6
|
+
.br
|
|
7
|
+
.SH DESCRIPTION
|
|
8
|
+
.PP
|
|
9
|
+
With all, the default, a Claude session also gets your Codex login and a Codex session your Claude login, when you have connected it, so the agent can run codex or claude on your own login: a Codex review from a Claude session, for example. With selected, a session gets its own agent's login only. Without arguments, prints the setting.
|
|
10
|
+
.PP
|
|
11
|
+
Only ever your own logins in a per\-person workspace: no session gets anyone else's. In a workspace that shares one home, whoever joins or steers there runs on the logins of the person who started it, these included. GitHub is given either way, and shells, pi and opencode get every login you connected either way; so does a shell you open on a session (mend shell), into the home its agent shares. A change applies the next time your logins are written into a workspace: one that already holds them keeps them while it runs, for new sessions of yours there too.
|
|
12
|
+
.SH EXAMPLES
|
|
13
|
+
.PP
|
|
14
|
+
.B mend agent\-logins
|
|
15
|
+
.PP
|
|
16
|
+
.B mend agent\-logins selected
|
|
17
|
+
.br
|
|
18
|
+
the session's own agent's login only
|
|
19
|
+
.SH SEE ALSO
|
|
20
|
+
mend(1), mend\-connect(1), mend\-accounts(1)
|
package/man/mend-attach.1
CHANGED
package/man/mend-codex.1
CHANGED
|
@@ -1,16 +1,18 @@
|
|
|
1
|
-
.TH MEND-CODEX 1 "" "mend 0.
|
|
1
|
+
.TH MEND-CODEX 1 "" "mend 0.36.0\-next.1033" "mend manual"
|
|
2
2
|
.SH NAME
|
|
3
|
-
mend\-codex \- launch codex, claude, or
|
|
3
|
+
mend\-codex \- launch codex, claude, opencode or pi in a recorded worktree
|
|
4
4
|
.SH SYNOPSIS
|
|
5
5
|
.B mend codex ["prompt"] [\-\-name <worktree>] [\-\-worktree <existing>] [\-\-model <id>] [\-\-effort <level>] [\-\-base <ref>] [\-\-ask] [\-\-fast] [\-\-detach|\-d] [\-\-foreground] [\-\-no\-tunnel] [\-\-land|\-\-no\-land] [\-\-project <p>]
|
|
6
6
|
.br
|
|
7
|
-
also mend claude, mend opencode, with the same options
|
|
7
|
+
also mend claude, mend opencode, mend pi, with the same options
|
|
8
8
|
.SH DESCRIPTION
|
|
9
9
|
.PP
|
|
10
|
-
mend codex, mend claude, and mend
|
|
10
|
+
mend codex, mend claude, mend opencode and mend pi are the same command with a different harness. The session runs in a workspace on the platform, in its own git worktree, and everything it does is recorded. This terminal attaches to it.
|
|
11
11
|
.PP
|
|
12
12
|
The worktree's name is asked first. \-\-name skips the ask; an existing name joins that worktree as a new session. \-\-worktree joins only and fails if the name is unknown. A quoted prompt becomes the first message.
|
|
13
13
|
.PP
|
|
14
|
+
When another person's session is running in the worktree you join, the launch says so before the session starts: you share its workspace, everything you run runs as you, on your own logins, and either of you can read the other's files, logins included.
|
|
15
|
+
.PP
|
|
14
16
|
Detach with Ctrl+] and the session keeps running. Reattach from any terminal with mend attach, or from the phone.
|
|
15
17
|
.PP
|
|
16
18
|
On a server that is not this machine, the session's live Services declared \-\-http or \-\-https are tunneled to this machine's loopback while this terminal is attached, on the Service's own port when it is free and on a free one when it is not. One line per tunnel says where it opens, for example web → http://localhost:5173. A Service that stops closes its tunnel, and detaching closes them all. The Services keep running.
|
|
@@ -27,10 +29,10 @@ name the worktree; an existing name joins it
|
|
|
27
29
|
join an existing worktree only
|
|
28
30
|
.TP
|
|
29
31
|
.B \-\-model <id>
|
|
30
|
-
the harness's model id
|
|
32
|
+
the harness's model id, one mend models lists. Default: the server's default for the harness
|
|
31
33
|
.TP
|
|
32
34
|
.B \-\-effort <level>
|
|
33
|
-
low, medium, high, xhigh, or
|
|
35
|
+
low, medium, high, xhigh, max, or ultra where the model takes it. Default: the harness's own
|
|
34
36
|
.TP
|
|
35
37
|
.B \-\-base <ref>
|
|
36
38
|
the branch or sha the worktree starts from
|
|
@@ -69,4 +71,4 @@ start in the background
|
|
|
69
71
|
.br
|
|
70
72
|
a second session in the same worktree
|
|
71
73
|
.SH SEE ALSO
|
|
72
|
-
mend(1), mend\-attach(1), mend\-stop(1), mend\-run(1), mend\-sessions(1), mend\-land(1)
|
|
74
|
+
mend(1), mend\-attach(1), mend\-stop(1), mend\-run(1), mend\-sessions(1), mend\-land(1), mend\-models(1)
|
package/man/mend-completions.1
CHANGED
|
@@ -0,0 +1,28 @@
|
|
|
1
|
+
.TH MEND-CONNECT-PI 1 "" "mend 0.36.0\-next.1033" "mend manual"
|
|
2
|
+
.SH NAME
|
|
3
|
+
mend\-connect\-pi \- send your pi setup to every pi session of yours
|
|
4
|
+
.SH SYNOPSIS
|
|
5
|
+
.B mend connect pi [\-\-dir <path>] [\-\-dry\-run] [\-\-remove]
|
|
6
|
+
.br
|
|
7
|
+
.SH DESCRIPTION
|
|
8
|
+
.PP
|
|
9
|
+
Reads pi's agent directory on this machine (~/.pi/agent, or $PI_CODING_AGENT_DIR) and saves it as your pi profile: extensions, themes, prompt templates, settings, mcp.json and keybindings. Every pi session you start receives it, and before pi starts the session installs the packages settings.json declares and what your extensions import. A package that fails to install is left out of that session, and the terminal says why.
|
|
10
|
+
.PP
|
|
11
|
+
Links are followed, so a setup a tool such as Home Manager links in is read as the files it points at. A package settings.json names by local path is copied into the profile. Your login stays here: pi runs on the ChatGPT login mend connect codex makes. Skills go with mend skills push. Run it again after you change your setup; sessions already running keep the profile they started with.
|
|
12
|
+
.SH OPTIONS
|
|
13
|
+
.TP
|
|
14
|
+
.B \-\-dir <path>
|
|
15
|
+
read another agent directory
|
|
16
|
+
.TP
|
|
17
|
+
.B \-\-dry\-run
|
|
18
|
+
say what would be sent, and send nothing
|
|
19
|
+
.TP
|
|
20
|
+
.B \-\-remove
|
|
21
|
+
delete the saved profile
|
|
22
|
+
.SH EXAMPLES
|
|
23
|
+
.PP
|
|
24
|
+
.B mend connect pi \-\-dry\-run
|
|
25
|
+
.br
|
|
26
|
+
what your pi profile would hold
|
|
27
|
+
.SH SEE ALSO
|
|
28
|
+
mend(1), mend\-connect(1), mend\-skills\-push(1)
|
package/man/mend-connect.1
CHANGED
|
@@ -1,14 +1,18 @@
|
|
|
1
|
-
.TH MEND-CONNECT 1 "" "mend 0.
|
|
1
|
+
.TH MEND-CONNECT 1 "" "mend 0.36.0\-next.1033" "mend manual"
|
|
2
2
|
.SH NAME
|
|
3
3
|
mend\-connect \- send this machine's provider credential to the platform
|
|
4
4
|
.SH SYNOPSIS
|
|
5
5
|
.B mend connect <claude|codex|github> [\-\-use\-my\-login] [\-\-from\-stdin] [\-\-remove]
|
|
6
6
|
.br
|
|
7
|
+
.B mend connect pi [\-\-dir <path>] [\-\-dry\-run] [\-\-remove]
|
|
8
|
+
.br
|
|
7
9
|
.SH DESCRIPTION
|
|
8
10
|
.PP
|
|
9
11
|
Sessions run on the platform, so the platform needs your provider login. It is stored under your own user and used only for your work. Nothing is shared with other users.
|
|
10
12
|
.PP
|
|
11
13
|
Claude and Codex get a login of Mend's own. Both rotate their refresh token, so two copies of one login fight and the one that refreshes second is signed out, and Mend's server refreshes on a schedule. So this logs in through the provider's own flow and your own login stays as it is: Claude in the browser, Codex with a device code, both sent and not kept here. Run it again whenever Mend says a login needs reconnecting. GitHub sends gh's token.
|
|
14
|
+
.PP
|
|
15
|
+
In a per\-person workspace each person's processes use their own GitHub login, in their own home: git over HTTPS to GitHub reads it through Mend's credential helper, and no GITHUB_TOKEN is set in the environment. A command that needs the token takes it for itself: GITHUB_TOKEN=$(/run/mend/bin/mend\-git\-credential token) <command>.
|
|
12
16
|
.SH OPTIONS
|
|
13
17
|
.TP
|
|
14
18
|
.B \-\-use\-my\-login
|
|
@@ -31,4 +35,4 @@ a Codex login of Mend's own, with a device code
|
|
|
31
35
|
.PP
|
|
32
36
|
.B mend connect github \-\-remove
|
|
33
37
|
.SH SEE ALSO
|
|
34
|
-
mend(1), mend\-accounts(1)
|
|
38
|
+
mend(1), mend\-accounts(1), mend\-connect\-pi(1)
|
package/man/mend-continue.1
CHANGED
package/man/mend-doctor.1
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
.TH MEND-DOCTOR 1 "" "mend 0.
|
|
1
|
+
.TH MEND-DOCTOR 1 "" "mend 0.36.0\-next.1033" "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
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
.TH MEND-ENV-CLUSTER 1 "" "mend 0.
|
|
1
|
+
.TH MEND-ENV-CLUSTER 1 "" "mend 0.36.0\-next.1033" "mend manual"
|
|
2
2
|
.SH NAME
|
|
3
3
|
mend\-env\-cluster \- bind Kubernetes secrets and configmaps to the workspaces
|
|
4
4
|
.SH SYNOPSIS
|
|
@@ -17,6 +17,9 @@ For a Mend server running in Kubernetes. The platform mounts the named objects i
|
|
|
17
17
|
.TP
|
|
18
18
|
.B \-\-project <p>
|
|
19
19
|
the project by name, when the current directory is not inside it
|
|
20
|
+
.TP
|
|
21
|
+
.B \-\-clear
|
|
22
|
+
with sa: run the workspaces as the platform's default service account
|
|
20
23
|
.SH EXAMPLES
|
|
21
24
|
.PP
|
|
22
25
|
.B mend env cluster add secret app\-env
|
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
|
@@ -1,16 +1,24 @@
|
|
|
1
|
-
.TH MEND-LOGIN 1 "" "mend 0.
|
|
1
|
+
.TH MEND-LOGIN 1 "" "mend 0.36.0\-next.1033" "mend manual"
|
|
2
2
|
.SH NAME
|
|
3
3
|
mend\-login \- sign this terminal in through the browser
|
|
4
4
|
.SH SYNOPSIS
|
|
5
|
-
.B mend login [\-\-url <server>]
|
|
5
|
+
.B mend login [\-\-url <server>] [\-\-open | \-\-no\-open]
|
|
6
6
|
.br
|
|
7
7
|
.SH DESCRIPTION
|
|
8
8
|
.PP
|
|
9
9
|
Opens <server>/authorize in your browser. You press Authorize there. The CLI saves a device token to ~/.config/mend/cli.json with mode 0600. No password is typed in the terminal, and the token can be revoked from the server at any time.
|
|
10
|
+
.PP
|
|
11
|
+
Over SSH, or on Linux with no display, no browser opens: the CLI prints the link and the code, and you open the link on your own machine.
|
|
10
12
|
.SH OPTIONS
|
|
11
13
|
.TP
|
|
12
14
|
.B \-\-url <server>
|
|
13
15
|
the Mend server. Default: MEND_URL, then http://localhost:3105
|
|
16
|
+
.TP
|
|
17
|
+
.B \-\-open
|
|
18
|
+
open the browser here, even over SSH
|
|
19
|
+
.TP
|
|
20
|
+
.B \-\-no\-open
|
|
21
|
+
only print the link and the code
|
|
14
22
|
.SH EXAMPLES
|
|
15
23
|
.PP
|
|
16
24
|
.B mend login \-\-url http://10.0.0.216:3105
|
package/man/mend-logout.1
CHANGED
package/man/mend-logs.1
ADDED
|
@@ -0,0 +1,37 @@
|
|
|
1
|
+
.TH MEND-LOGS 1 "" "mend 0.36.0\-next.1033" "mend manual"
|
|
2
|
+
.SH NAME
|
|
3
|
+
mend\-logs \- print a session's recorded terminal output
|
|
4
|
+
.SH SYNOPSIS
|
|
5
|
+
.B mend logs [session] [\-\-follow] [\-\-from <sequence>] [\-\-process <id>]
|
|
6
|
+
.br
|
|
7
|
+
.B mend logs [session] \-\-service <name\-or\-id> [\-\-follow] [\-\-from <sequence>]
|
|
8
|
+
.br
|
|
9
|
+
.SH DESCRIPTION
|
|
10
|
+
.PP
|
|
11
|
+
Prints what the session's command (or agent) wrote to its terminal, as the record holds it, on stdout. Settled sessions count: the record outlives the process and the workspace. \-\-follow keeps printing until the process ends. The record is printed as it is, nothing taken out: anyone who can read the project can read it, so what a command printed, a password included, reaches them too. A signal stops it and puts the terminal back, exiting 128 + its number: 130 for SIGINT (Ctrl+C), 129 for SIGHUP, 143 for SIGTERM.
|
|
12
|
+
.PP
|
|
13
|
+
<session> is the session id, a prefix of it, or the worktree's name. With none, the one live session is taken. \-\-process reads another process of the session, a shell or a Service attempt, by a prefix of its id; a Service's id or name there reads the Service's current attempt.
|
|
14
|
+
.PP
|
|
15
|
+
\-\-service reads a Service's current attempt, by the Service's id, its name or a prefix of its id, the ids mend service list prints. A full id names its Service before any name does. A name two Services carry is refused, with both ids listed; name one by its id, or name the session. A Service with no attempt (an adopted port, which Mend runs no process for) has nothing recorded, and mend logs says so and exits 1.
|
|
16
|
+
.SH OPTIONS
|
|
17
|
+
.TP
|
|
18
|
+
.B \-\-follow, \-f
|
|
19
|
+
keep printing until the process ends
|
|
20
|
+
.TP
|
|
21
|
+
.B \-\-from <sequence>
|
|
22
|
+
start at a record sequence. Default: 0
|
|
23
|
+
.TP
|
|
24
|
+
.B \-\-process <id>
|
|
25
|
+
another process of the session, by a prefix of its id
|
|
26
|
+
.TP
|
|
27
|
+
.B \-\-service <name\-or\-id>
|
|
28
|
+
a Service's current attempt
|
|
29
|
+
.SH EXAMPLES
|
|
30
|
+
.PP
|
|
31
|
+
.B mend logs 3f2a \-\-follow
|
|
32
|
+
.PP
|
|
33
|
+
.B mend logs \-\-service web \-\-follow
|
|
34
|
+
.br
|
|
35
|
+
the Service web's output, live
|
|
36
|
+
.SH SEE ALSO
|
|
37
|
+
mend(1), mend\-run(1), mend\-wait(1), mend\-service\-logs(1)
|
package/man/mend-man.1
CHANGED
package/man/mend-members.1
CHANGED
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
.TH MEND-MEMORY-IMPORT 1 "" "mend 0.36.0\-next.1033" "mend manual"
|
|
2
|
+
.SH NAME
|
|
3
|
+
mend\-memory\-import \- bring this machine's claude and codex memory for the repository
|
|
4
|
+
.SH SYNOPSIS
|
|
5
|
+
.B mend memory import [\-\-project <p>] [\-\-dry\-run]
|
|
6
|
+
.br
|
|
7
|
+
.SH DESCRIPTION
|
|
8
|
+
.PP
|
|
9
|
+
Run inside the repository's checkout. Reads the memory Claude Code keeps on this machine for that directory, and the summaries Codex made of conversations held in it. Codex keeps one memory for everything, so only its summaries of this repository's conversations are read, never its consolidated memory. Transcripts, logins and settings are not read.
|
|
10
|
+
.PP
|
|
11
|
+
A file Mend does not have is added. A file both sides have with other contents is merged, keeping both sides' lines (a line both wrote at different places stays twice), and a note's frontmatter is merged key by key, with this machine's value kept as a comment where the two differ. Mend remembers what it imported from this checkout on this machine, so the next import from here takes whichever side changed since and merges only what both changed. A file Mend removed since then is not added again. A file it cannot merge stays as Mend has it, and this machine's is kept as a version, as it is when a merge does not hold every line this machine sent. Every version Mend replaces is kept.
|
|
12
|
+
.SH OPTIONS
|
|
13
|
+
.TP
|
|
14
|
+
.B \-\-project <p>
|
|
15
|
+
the project by name, when the current directory is not inside it
|
|
16
|
+
.TP
|
|
17
|
+
.B \-\-dry\-run
|
|
18
|
+
show what the import would do, and write nothing
|
|
19
|
+
.SH EXAMPLES
|
|
20
|
+
.PP
|
|
21
|
+
.B mend memory import \-\-dry\-run
|
|
22
|
+
.SH SEE ALSO
|
|
23
|
+
mend(1), mend\-memory(1), mend\-adopt(1)
|
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
.TH MEND-MEMORY-RM 1 "" "mend 0.36.0\-next.1033" "mend manual"
|
|
2
|
+
.SH NAME
|
|
3
|
+
mend\-memory\-rm \- remove one memory file
|
|
4
|
+
.SH SYNOPSIS
|
|
5
|
+
.B mend memory rm <file> [\-\-project <p>]
|
|
6
|
+
.br
|
|
7
|
+
.SH DESCRIPTION
|
|
8
|
+
.PP
|
|
9
|
+
Removes the file from your memory for the project. Sessions already running keep their copy; the next launch does not deliver it, and a session that still holds it unchanged moves it aside. The last version stays on the server.
|
|
10
|
+
.SH OPTIONS
|
|
11
|
+
.TP
|
|
12
|
+
.B \-\-project <p>
|
|
13
|
+
the project by name, when the current directory is not inside it
|
|
14
|
+
.SH SEE ALSO
|
|
15
|
+
mend(1), mend\-memory(1)
|
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
.TH MEND-MEMORY-SHOW 1 "" "mend 0.36.0\-next.1033" "mend manual"
|
|
2
|
+
.SH NAME
|
|
3
|
+
mend\-memory\-show \- print one memory file
|
|
4
|
+
.SH SYNOPSIS
|
|
5
|
+
.B mend memory show <file> [\-\-project <p>]
|
|
6
|
+
.br
|
|
7
|
+
.SH DESCRIPTION
|
|
8
|
+
.PP
|
|
9
|
+
Prints the file as Mend stores it, by the name mend memory lists. A name alone is Claude's; prefix another harness's with its name, as in codex:MEMORY.md.
|
|
10
|
+
.SH OPTIONS
|
|
11
|
+
.TP
|
|
12
|
+
.B \-\-project <p>
|
|
13
|
+
the project by name, when the current directory is not inside it
|
|
14
|
+
.SH SEE ALSO
|
|
15
|
+
mend(1), mend\-memory(1)
|
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
.TH MEND-MEMORY 1 "" "mend 0.36.0\-next.1033" "mend manual"
|
|
2
|
+
.SH NAME
|
|
3
|
+
mend\-memory \- what the agents remember about a project, for you
|
|
4
|
+
.SH SYNOPSIS
|
|
5
|
+
.B mend memory [list] [\-\-project <p>]
|
|
6
|
+
.br
|
|
7
|
+
.B mend memory show <file> [\-\-project <p>]
|
|
8
|
+
.br
|
|
9
|
+
.B mend memory rm <file> [\-\-project <p>]
|
|
10
|
+
.br
|
|
11
|
+
.SH DESCRIPTION
|
|
12
|
+
.PP
|
|
13
|
+
Claude Code and Codex write what they learn about a repository to their memory. Mend keeps that memory per person per project: every session you start on the project receives it, and what the agent learned is saved back when it ends. When two of your sessions change the same text file, both sides' lines are kept.
|
|
14
|
+
.PP
|
|
15
|
+
Codex builds its memory from your past conversations when a session starts, with model calls on your own login. Mend carries your earlier Codex conversations on the project into each new session so it has some to learn from.
|
|
16
|
+
.PP
|
|
17
|
+
This lists your memory for the project, prints one file, or removes one. Removing keeps the last version on the server. Other people's sessions never see it.
|
|
18
|
+
.SH OPTIONS
|
|
19
|
+
.TP
|
|
20
|
+
.B \-\-project <p>
|
|
21
|
+
the project by name, when the current directory is not inside it
|
|
22
|
+
.SH EXAMPLES
|
|
23
|
+
.PP
|
|
24
|
+
.B mend memory
|
|
25
|
+
.br
|
|
26
|
+
your memory for the project in this directory
|
|
27
|
+
.PP
|
|
28
|
+
.B mend memory show MEMORY.md
|
|
29
|
+
.br
|
|
30
|
+
Claude's index of what it remembers
|
|
31
|
+
.SH SEE ALSO
|
|
32
|
+
mend(1), mend\-memory\-import(1)
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
.TH MEND-MODELS 1 "" "mend 0.36.0\-next.1033" "mend manual"
|
|
2
|
+
.SH NAME
|
|
3
|
+
mend\-models \- the models each harness offers, as the server lists them
|
|
4
|
+
.SH SYNOPSIS
|
|
5
|
+
.B mend models [\-\-json]
|
|
6
|
+
.br
|
|
7
|
+
.SH DESCRIPTION
|
|
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 and VS Code offer the same one, and a session records which model it was started with.
|
|
10
|
+
.PP
|
|
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
|
+
.SH OPTIONS
|
|
13
|
+
.TP
|
|
14
|
+
.B \-\-json
|
|
15
|
+
the catalog as the server answers it
|
|
16
|
+
.SH EXAMPLES
|
|
17
|
+
.PP
|
|
18
|
+
.B mend models
|
|
19
|
+
.PP
|
|
20
|
+
.B mend codex "fix the flaky test" \-\-model gpt\-6\-astra \-\-effort ultra
|
|
21
|
+
.SH SEE ALSO
|
|
22
|
+
mend(1), mend\-codex(1), mend\-sessions(1)
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
.TH MEND-OPERATOR-EXPOSURE 1 "" "mend 0.
|
|
1
|
+
.TH MEND-OPERATOR-EXPOSURE 1 "" "mend 0.36.0\-next.1033" "mend manual"
|
|
2
2
|
.SH NAME
|
|
3
3
|
mend\-operator\-exposure \- how this instance is exposed, as declared and as observed
|
|
4
4
|
.SH SYNOPSIS
|
|
@@ -6,6 +6,6 @@ mend\-operator\-exposure \- how this instance is exposed, as declared and as obs
|
|
|
6
6
|
.br
|
|
7
7
|
.SH DESCRIPTION
|
|
8
8
|
.PP
|
|
9
|
-
Operator only. States MEND_EXPOSURE as declared (loopback, private or public) and one line per item of the public exposure gate, with how it was established: observed (this server read it), carried (this build contains it, and the server cannot see it in effect), declared (you stated it and the server cannot check it), or open. MEND_EXPOSURE=public refuses to start while an item the server can observe
|
|
9
|
+
Operator only. States MEND_EXPOSURE as declared (loopback, private or public) and one line per item of the public exposure gate, with how it was established: observed (this server read it), carried (this build contains it, and the server cannot see it in effect), declared (you stated it and the server cannot check it), or open. MEND_EXPOSURE=public refuses to start while an item that blocks a start is open: every item the server can observe, and workspace\-ssh until you declare it. Items it cannot observe say what would verify them; once you have verified core\-private, edge\-tls, workspace\-ssh (SSH published apart from the web port) or (while it is enabled) t3code\-gateway from outside, name it in MEND_EXPOSURE_DECLARED, or with mend server setup \-\-declare. The report is what was observed; it is not a statement that the instance is fit to expose.
|
|
10
10
|
.SH SEE ALSO
|
|
11
11
|
mend(1), mend\-operator\-gate(1), mend\-doctor(1)
|
package/man/mend-operator-gate.1
CHANGED
package/man/mend-pair.1
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
.TH MEND-PAIR 1 "" "mend 0.
|
|
1
|
+
.TH MEND-PAIR 1 "" "mend 0.36.0\-next.1033" "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>
|