Mendby Sealant

Run your TUI agents anywhere you want

The coding agent you already use, in a recorded worktree on your own machine — reachable from every device you own.

$ curl -fsSL https://mend.sealant.dev/install.sh | sh

Open source · Self-hosted · Linux

01 / 05

Any TUI — terminal, browser, phone

mend claude, mend codex, or any command. One session, three ways in: terminal, browser, phone.

The session page is the same PTY your terminal holds — not a transcript of it. The web pane and the phone attach to the record stream, replay the scrollback, then ride the live bytes; a keystroke from any screen lands in the same harness. The rail keeps the machine facts beside the screen: checkpoints as you work, and every port the agent opens, forwarded under the session's address.

mend · localhost:3101/sessions/01J8QK4M

MendNowProjectsSettingsSign out

session

claude — fix invoice rounding

Running · recordingReview the changeMark checkpoint

mend/session/01J8QK4M · worktree store/billing-service/01J8QK4M · base 4f2c91ab90e2 · started 14:32:06

run r_01J8QK4M · live — the same session your terminal holds

attached: terminal · web · phone

$ mend claude

Checkpoints

41 · user-mark8e91c02 · seq 4021 · 14:41diff

40 · auto77120af · seq 3960 · 14:39diff

Forwards

:3000 vite dev/s/01j8qk4m/3000forwarded

02 / 05

One worktree per session

Each session runs in its own worktree on the server — parallel sessions, code in one place. And each gets its own link: a dev server started inside is one click away.

The project page is the fleet view. Adoption moved the repository into the central store, so each session row is its own worktree checked out from that store — parallel work that never collides, on a machine that keeps all of it. The addresses rail answers "where is it running": every forwarded port, one click from any device.

mend · localhost:3101/projects/billing-service

MendNowProjectsSettingsSign out

project

billing-service

start a session:claudecodexopencode

store ~/.config/mend/store/billing-service · main@4f2c91a · origin github.com/acme/billing-service

Sessions — one worktree each

claude — fix invoice roundingmend/session/01J8QK4M · base 4f2c91ab90e2Running · recording

codex — spike usage webhooksmend/session/01J8QKPT · base 4f2c91ab90e2Waiting for input

claude — refactor tax rulesmend/session/01J8QH2W · base 4f2c91ab90e2Completed · observed

Addresses

/s/01j8qk4m:3000 vite devforwarded

/s/01j8qkpt:6006 storybookforwarded

References

effect/workspace/ref/effect · a91c2ffread-only

03 / 05

Review beside the change

Mend reads the change and drafts a guided review — comments and suggestions with the evidence beside them. Replies land back in the live session.

The diff is the primary surface — read it file by file, or take the tour: the change replayed stop by stop, in the order the record wrote it. Comments anchor to a line and carry their evidence — a record sequence you can open, or a check you can run. Open comments assemble into one follow-up instruction that you edit before it is sent; nothing leaves the page on its own. Send it, and it lands in the live session for the agent to act on.

mend · localhost:3101/changes/01J8QK4M

MendNowProjectsSettingsSign out

review

session invoice-rounding

Exit tourSend review to session

worktree vs 4f2c91ab90e2 · 8 files · +214 −87 · 2 open comments · session

Stop 2 · the rounding boundarysrc/billing/total.ts · written at seq 3984

2 / 7← prevnext →

Files

src/billing/round.ts+20 −01src/billing/total.ts+12 −42src/billing/invoice.ts+41 −183migrations/012_cents.sql+26 −524src/api/billing.http.ts+9 −25test/rounding.test.ts+36 −06test/billing.test.ts+48 −87docs/billing.md+22 −3

src/billing/total.ts · +12 −4

const rate = plan.rateFor(usage)

- const total = amount * rate

+ const total = round(amount * rate)

return { total, rate }

Every amount leaves through total() — rounding here is what makes the cents migration in stop 4 safe. round() itself was stop 1.

the tour's note for this stop · from the record, seq 3960–4021

half-cents are dropped here — intended? The record shows no test touching rounding.

your comment, anchored total.ts:12 · evidence seq 3984 · open

04 / 05

Context packs from sessions

Scrub a session's record and promote what mattered into the project's context store as named packs. Inject it anytime.

The context page turns sessions into reusable knowledge, at whatever grain holds up. Scrub the record, select a span, and Mend offers what it contained: a single decision, one prompt-and- answer exchange, a check that passed, a file exactly as the agent saw it — or the whole span summarised as a handoff. You tick what becomes context; it joins a named, versioned pack. A session records the exact snapshot it received, so a review can always show what the agent knew. Inject a pack when a session starts, or into one already running.

mend · localhost:3101/projects/billing-service/context

MendNowProjectsSettingsSign out

context

authentication-service

pack · v3Inject into session

project billing-service · 4 items · snapshot 7 in use by 01J8QKPT

Record · 01J8QK4M — drag a span, promote what mattered

seq 0selected seq 3960 – 4021 · “legacy callback dig”seq 4021

From the selection — choose the grain

decision: db sessions stay authoritativeone answer · seq 3990

check: pnpm test auth/callbacks — passingcommand + result · seq 4014

handoff: legacy callback investigationthe whole span, summarised · seq 3960–4021

exchange: "why do callbacks retry twice?"prompt + answer · seq 3984

file read: docs/legacy-sso.mdas the agent saw it · seq 3971

Pack · authentication-service

AGENTS.mdfile · pinned to mainv3

docs/authentication.mdfile · pinned to mainv3

3 selections join on savedecision · check · handoffpromoting

05 / 05

Sessions outlive harnesses

A session belongs to the project, not the tool. Continue any session with a different harness than the one that started it.

When a session settles, the page offers the continuation directly: resume with any harness, not just the one that started it. The next harness lands in the same worktree with the same context snapshot, and the record continues as one history — so the review later reads one change, no matter how many tools touched it.

mend · localhost:3101/sessions/01J8QKPT

MendNowProjectsSettingsSign out

session

codex — spike usage webhooks

Completed · observedresume with:codexclaudeopencode

mend/session/01J8QKPT · worktree store/billing-service/01J8QKPT · base 4f2c91ab90e2

record r_01J8QKPT · settled — replay from any checkpoint

$ mend codex

mend claude, mend codex, or any command. One session, three ways in: terminal, browser, phone.