@@ -101,9 +101,16 @@ carries every feature forward unchanged. That commit includes the full
 - [Prompt start height, percentage sizes and home screen layout](./features/2026-10-12-home-screen-layout.md)
 - [Deliver and settle TUI worker requests without startup races](./features/2026-10-12-tui-worker-error-reply.md)
 - [tui.json decides over remembered runtime toggles](./features/2026-10-12-tui-config-toggle-precedence.md)
+- [Markdown in submitted user messages and plugin-defined message blocks](./features/2026-10-14-user-message-markdown.md)
 
 ## Session records
 
+- [2026-10-14 `ses_ec57be11affe3kxXJ4WyM3OwOY`](./sessions/2026-10-14-user-message-markdown.md)
+  - `syntax.user_messages` colors markdown in submitted messages; `syntax.blocks`
+    and `api.blocks.register` draw delimited blocks, `[vibeterm_*]` as YAML via
+    the route plugin; issues #55439/#55440, PRs #55441/#55442; vt-292 on both
+    hosts, enforced on both.
+
 - [2026-10-14 `ses_eebf9a83fffeIQQwW9gVFo5jaO`](./sessions/2026-10-14-instant-drag-copy.md)
   - A drag anywhere on opencode's instant home and "Loading session…" screens
     copies the drawn text (OSC 52 plus native clipboard), not only inside the
 
@@ -113,6 +113,11 @@ Reported by `ses_ed1e2b932ffe6tTqhsOiGuYXRE`; see its
   user question "support for systemd units coloring?": heredoc bodies written to
   unit files were a shell string; now ini. PRs #54705 and #54706 amended.
   Evidence: `246c6c10f2`; two-heredoc frames at 40/80/160; PTY at 80/160.
+- 2026-10-14 [`ses_ec57be11affe3kxXJ4WyM3OwOY`](../sessions/2026-10-14-user-message-markdown.md) -
+  `toolCodeTheme` gains the markdown slots for colored user messages, and the
+  tool input block's colors become `toolInputColors`, shared with YAML message
+  blocks. See [markdown in user messages](./2026-10-14-user-message-markdown.md).
+  Evidence: `5e5994b93a`, `748601cc2b`; `tool-code-theme.test.ts`.
 
 ## Future ideas
 
 
@@ -0,0 +1,100 @@
+# Markdown in submitted user messages and plugin-defined message blocks
+
+## Identity
+
+- Status: active
+- Integration branch: `dev-nowaker`
+- Development branch(es): `message-syntax` (worktree off `dev-nowaker`);
+  upstream branches `message-markdown` (`9de106cb26`, stacked on
+  `tool-output-syntax`) and `message-blocks` (`2c659ccfe6`, stacked on
+  `message-markdown`), off `github/v1` `dfb56f76c7`
+- First local commit: `5e5994b93a`
+- Current local commit(s): `5e5994b93a`, `748601cc2b`
+- Upstream base when introduced: `dfb56f76c7` (upstream `v1`, `v1.19.0`)
+- Last checked against upstream: `dfb56f76c7`
+- Upstream: issues [#55439](https://github.com/anomalyco/opencode/issues/55439),
+  [#55440](https://github.com/anomalyco/opencode/issues/55440); PRs
+  [#55441](https://github.com/anomalyco/opencode/pull/55441) (markdown, stacked
+  on #54968) and [#55442](https://github.com/anomalyco/opencode/pull/55442)
+  (blocks, stacked on #55441), both against `v1`. **Needs a v2 port later.**
+
+## Original request
+
+Relayed by coordinator `ses_ef8235798ffejGr4sa22eXmVNv` (item 37), the user
+verbatim:
+
+> i want syntax coloring of user already submitted messafges. it doesn't (and
+> can't) be as good as ai messages because we humans type botched syntax, but we
+> can probably fire opencode's md colorizer at it, to colorize: 1. ble 2. blah
+> (or - bullet points) wherever they show up. or colorize `content in ticks`. or
+> colorize #headers of various level. maybe even try tables?
+> and for vibeterm specicially needed real bad, and to be proposed as separate PR
+> with hopes they wil accept, we'd like to define custom formatters, or whatever
+> to call it (if not possible today, who knows?) - speciafaclly, i need us to
+> catch any
+> [vibterm_*]
+> ...
+> [/vibeterm_*]
+> and render it with our standard yaml colors/formatting.
+
+## Goals
+
+- `syntax.user_messages` (default `false`, as upstream) colors the markdown in a
+  submitted user message: headings, lists, inline and fenced code, emphasis,
+  links, quotes, tables.
+- Only colors change: text as typed, wraps as plain, nothing concealed, no red.
+- Accidental markdown stays plain: setext headings, indented code, lazy quote
+  continuation, intra-word emphasis.
+- A plugin (`api.blocks.register`) or `syntax.blocks` defines a delimited block
+  and its format; `yaml` uses the tool input block's colors.
+- Vibeterm's `[vibeterm_*]` blocks draw as YAML through the `vibeterm.route`
+  plugin, with no tui.json entry.
+
+## Non-goals
+
+- Assistant text: it goes through `<markdown>`, which has no per-range hook.
+- Rendering markdown (concealment, reflow) in user messages.
+
+## Rationale and constraints
+
+- The tree-sitter markdown grammar already in opentui gives highlights on the
+  raw text; setting them as chunks on one text renderable (`StyledOutput`, from
+  #54968) keeps layout identical, where `<markdown>` would reflow and conceal.
+- Upstream PR B does not depend on #54707: it keeps its own `YamlKind` and
+  `yamlColors`; the fork shares one `toolInputColors` between the tool input
+  block and YAML blocks.
+
+## Changes
+
+| Commit | Workday | Change | Stable seam |
+|---|---|---|---|
+| `5e5994b93a` | 2026-10-14 | `syntax.user_messages`; forgiving markdown highlights over user text; markdown slots in the non-red palette | `UserText` in `routes/session/index.tsx`; `util/user-markdown.ts` `forgivingMarkdown`; `ALTERNATIVES` in `theme/tool-code.ts`; `Syntax` in `config/index.tsx` |
+| `748601cc2b` | 2026-10-14 | `syntax.blocks`, `api.blocks.register`, yaml formatter; `toolInputColors` shared with `GenericTool` | `util/message-blocks.ts` `messageSegments`, `yamlSegments`; `messageChunks` in `routes/session/index.tsx`; `TuiMessageBlock` in `packages/plugin/src/tui.ts`; `registerBlock` in `plugin/runtime.tsx`; `blocks` in `opencode/src/plugin/tui/runtime.ts` |
+
+opencode-tools `0497c41`: `opencode-vibeterm-route-plugin/message-blocks.ts`
+registers `[vibeterm_*]` / `[/vibeterm_*]` / `yaml`.
+
+Docs: `user_messages` and `blocks` under `Syntax highlighting` in
+`packages/web/src/content/docs/tui.mdx`.
+
+## Verification
+
+Reported by `ses_ec57be11affe3kxXJ4WyM3OwOY`; see its
+[session record](../sessions/2026-10-14-user-message-markdown.md).
+
+## Timeline
+
+- 2026-10-14 [`ses_ec57be11affe3kxXJ4WyM3OwOY`](../sessions/2026-10-14-user-message-markdown.md) -
+  initial build of both parts, Vibeterm route plugin rule, upstream issues and
+  PRs, install on both hosts, `syntax.user_messages` enforced on both hosts.
+  Evidence: `5e5994b93a`, `748601cc2b`; PTY at 80/160.
+
+## Current maintenance notes
+
+- The upstream branches carry no AI trailers; the fork commits do.
+- Fork vs upstream B: `toolInputColors` + `ToolInputKind` (fork, from #54707)
+  vs `yamlColors` + `YamlKind` (upstream). Whichever of #54707 and #55442 lands
+  second merges them.
+- `syntax.blocks` is an array of objects, so the opencode-tools knob catalog
+  does not list it; `syntax.user_messages` is a global-only knob there
+  (opencode-tools `a42e4c6`).
@@ -0,0 +1,108 @@
+# Markdown in user messages and [vibeterm_*] blocks as YAML
+
+## Identity
+
+- Workday: 2026-10-14
+- Session: `ses_ec57be11affe3kxXJ4WyM3OwOY`
+- Agent/platform: Sisyphus (anthropic/claude-opus-5-5, high) / linux
+- Repository: `~/projekty/webapps/opencode`; opencode-tools
+- Integration branch: `dev-nowaker`
+- Development branch(es): `message-syntax`; upstream `message-markdown`,
+  `message-blocks`
+- Upstream base: `dfb56f76c7` (`v1.19.0`)
+- Source result commit(s): `5e5994b93a`, `748601cc2b`
+- Forklog commit: this file's introducing commit
+
+## User requests
+
+Relayed by coordinator `ses_ef8235798ffejGr4sa22eXmVNv` (item 37); the
+verbatim request is in the
+[feature record](../features/2026-10-14-user-message-markdown.md#original-request).
+The coordinator added: knob default off as upstream, the user's value only
+through Vibeterm settings, prefer extending the TUI plugin API over hardcoding
+Vibeterm, a real-terminal check, both-host install, upstream PRs against v1.
+
+## Goals
+
+- Color the markdown in submitted user messages without changing their text or
+  wrap.
+- Let a plugin or config format a delimited block; draw `[vibeterm_*]` as YAML.
+
+## Constraints and non-goals
+
+- Never red in the transcript; no change to assistant text.
+- No restart of `opencode-serve-tailscale`, `opencode-serve-lan` or any tab.
+
+## Branch and upstream movement
+
+| Repository | Branch | Before | After | Action |
+|---|---|---|---|---|
+| opencode | `dev-nowaker` | `b0ebca176f` | `748601cc2b` | fast-forward of `message-syntax`, pushed to `origin` and `nowaker-github` |
+| opencode | `message-markdown` | - | `9de106cb26` | new, on `tool-output-syntax` (#54968), PR #55441 |
+| opencode | `message-blocks` | - | `2c659ccfe6` | new, on `message-markdown`, PR #55442 |
+| opencode-tools | `master` | `7e47b93` | `0497c41` | route plugin registers the `[vibeterm_*]` rule |
+
+`ses_ec549ca11ffeaEknagLhxmfpFp` rebased its unpushed forklog commit
+`340c1ca1d8` onto `748601cc2b` as `181722b19d` after a queued note from this
+session; nothing of theirs was touched here.
+
+## Features touched
+
+| Feature | Outcome | Evidence |
+|---|---|---|
+| [Markdown in user messages and message blocks](../features/2026-10-14-user-message-markdown.md) | new | below |
+| [Syntax coloring in tool calls](../features/2026-10-11-tool-syntax-coloring.md) | changed | `toolCodeTheme` gains markdown slots; `GenericTool` reads `toolInputColors`; `tool-code-theme.test.ts` covers the new slots |
+
+## Other delivered work
+
+- opencode-tools `0497c41`: `registerMessageBlocks` in
+  `opencode-vibeterm-route-plugin`, test, FEATURES.md.
+- `opencodeTui.syntax.user_messages` enforced `true` through `writeSetting` on
+  desktop and m4max, after opencode-tools `a42e4c6`
+  (`ses_ed1e2b932ffe6tTqhsOiGuYXRE`) gave the knob a Focus decision; the first
+  attempt wrote tui.json but failed on `opencodeTui.enforced`.
+
+## Verification
+
+- packages/tui on `message-syntax` rebased on `b0ebca176f`: typecheck clean;
+  full suite 681 pass, 0 fail. packages/plugin and packages/opencode typecheck
+  clean; push hook 30/30 typecheck tasks.
+- Upstream `message-blocks`: tui, plugin and opencode typecheck clean; tui
+  suite 247 pass, 0 fail.
+- Real PTY, scratch build `1.19.0-vt-289`, isolated XDG home, fake provider,
+  throwaway `ocrig-*` tmux sockets, 80 and 160 columns, three variants (off;
+  `syntax.blocks` in tui.json; the rule from the route plugin): the message's
+  screen text is identical in all three; headings, list markers, inline code
+  and table headers colored; YAML keys peach, strings green, numbers orange,
+  booleans purple, delimiter lines grey; `done`/`---` plain; no red cell.
+- A first PTY attempt deadlocked: `Bun.spawnSync` of `opencode run` blocked the
+  in-process fake provider. A second seeded the message with `opencode run`'s
+  argument quoting (`"[vibeterm_metadata]`, `run.ts:289`), correctly unmatched;
+  the final run seeds through stdin.
+
+## Build and install
+
+- Build command: `VIBETERM_V2_GUARD=<opencode-tools>/vibeterm-opencode-client/bin/vibeterm-v2-guard .vibeterm/build.sh`
+  in each host's primary checkout at `181722b19d`
+- Installed artifact: `1.19.0-vt-292-dfb56f76c7`; desktop inode `49964691`,
+  m4max inode `34213364`; v2 guard gate PASSED on both; retry marker present on
+  both.
+- Running services: desktop `opencode-serve-tailscale` PID `914944` (started
+  04:38:28 CDT) and `opencode-serve-lan` PID `910216` unchanged; no tab
+  restarted, so running tabs pick this up on their next start.
+
+## Commit provenance
+
+- `5e5994b93a`, `748601cc2b` - source.
+- Required trailer: `AI-Session-ID: ses_ec57be11affe3kxXJ4WyM3OwOY`
+
+```sh
+git log --format='%H %(trailers:key=AI-Session-ID,valueonly)' -- \
+  .vibeterm/forklog/sessions/2026-10-14-user-message-markdown.md
+```
+
+## Unknowns and blocked verification
+
+- No v1/v2 patch-rig scenario added; not in the matrix.
+- The instant-editor test timed out once at load average ~80 on both this
+  branch and the untouched base; it passed in the later full run.