Skip to content

feat(discord,web): Discord markdown finals + T3 message deep links - #266

Merged
omegent-app[bot] merged 2 commits into
fork/discordfrom
t3-discord/md-plus-t3-anchor
Jul 31, 2026
Merged

feat(discord,web): Discord markdown finals + T3 message deep links#266
omegent-app[bot] merged 2 commits into
fork/discordfrom
t3-discord/md-plus-t3-anchor

Conversation

@omegent-app

@omegent-app omegent-app Bot commented Jul 31, 2026

Copy link
Copy Markdown

Summary

ASCII tables killed clickable links. Finals now stay as Discord markdown; long or table-heavy answers get a compact T3 deep link. The web client opens ?thread= and scrolls to #message-{id}.

Discord bot

  • No more GFM → ASCII table rewrite on finalize
  • Message content keeps real Discord markdown (links work)
  • When multi-chunk or has tables: append · [T3]({T3_WEB_UI_BASE_URL}/?thread=…#message-…)
  • Uses configured web UI base (same as pin), not invented short host
  • Attachments on request still fine (not forced)

Web client

  • Parse /?thread={id}#message-{messageId}
  • Navigate to thread once shells bootstrap
  • ChatView anchors/scrolls that message via existing timeline anchor machinery

Test plan

  • Discord attachments / attribution / ResponseBridge unit tests
  • Web deep link parse + store unit tests
  • Smoke: short answer = no T3 link, links in prose clickable
  • Smoke: table-heavy answer = prose + · [T3](…)
  • Smoke: open deep link → correct thread + message scrolled into view

opened by patroza in chat thread Discord · Discord · T3

Co-authored by: patroza

omegent-app Bot and others added 2 commits July 31, 2026 14:53
Stop ASCII-tableifying finals so links stay clickable. Long or table-heavy
answers append a compact · [T3](webUi/?thread=…#message-…) deep link using
the configured web UI base. Web navigates ?thread= and scrolls #message- into
view via the existing timeline anchor path.

Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
@omegent-app
omegent-app Bot marked this pull request as ready for review July 31, 2026 15:09
@omegent-app
omegent-app Bot merged commit 0e5419f into fork/discord Jul 31, 2026
9 checks passed
@omegent-app
omegent-app Bot deleted the t3-discord/md-plus-t3-anchor branch July 31, 2026 15:10
patroza added a commit that referenced this pull request Jul 31, 2026
)

* feat(discord,web): Discord markdown finals + T3 message deep links

Stop ASCII-tableifying finals so links stay clickable. Long or table-heavy
answers append a compact · [T3](webUi/?thread=…#message-…) deep link using
the configured web UI base. Web navigates ?thread= and scrolls #message- into
view via the existing timeline anchor path.

Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>

* fix(web): typecheck deep-link MessageId import and navigate hash

Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>

---------

Co-authored-by: omegent-app[bot] <306514130+omegent-app[bot]@users.noreply.github.com>
Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
patroza added a commit that referenced this pull request Jul 31, 2026
Discord #266 landed OmegentDeepLinkCoordinator, deepLinks helpers, and
ChatView scroll on the discord overlay. Those are shared web surfaces and
collided with identity's IdentityClaimGate mount in __root during
compose. Keep them on fork/changes so overlays only own client-specific
code; Discord bot ResponseBridge stays on fork/discord.

Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza added a commit that referenced this pull request Jul 31, 2026
)

* feat(discord,web): Discord markdown finals + T3 message deep links

Stop ASCII-tableifying finals so links stay clickable. Long or table-heavy
answers append a compact · [T3](webUi/?thread=…#message-…) deep link using
the configured web UI base. Web navigates ?thread= and scrolls #message- into
view via the existing timeline anchor path.

Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>

* fix(web): typecheck deep-link MessageId import and navigate hash

Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>

---------

Co-authored-by: omegent-app[bot] <306514130+omegent-app[bot]@users.noreply.github.com>
Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>
patroza added a commit that referenced this pull request Aug 1, 2026
Discord #266 landed OmegentDeepLinkCoordinator, deepLinks helpers, and
ChatView scroll on the discord overlay. Those are shared web surfaces and
collided with identity's IdentityClaimGate mount in __root during
compose. Keep them on fork/changes so overlays only own client-specific
code; Discord bot ResponseBridge stays on fork/discord.

Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza added a commit that referenced this pull request Aug 1, 2026
Discord #266 landed OmegentDeepLinkCoordinator, deepLinks helpers, and
ChatView scroll on the discord overlay. Those are shared web surfaces and
collided with identity's IdentityClaimGate mount in __root during
compose. Keep them on fork/changes so overlays only own client-specific
code; Discord bot ResponseBridge stays on fork/discord.

Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza added a commit that referenced this pull request Aug 4, 2026
Discord #266 landed OmegentDeepLinkCoordinator, deepLinks helpers, and
ChatView scroll on the discord overlay. Those are shared web surfaces and
collided with identity's IdentityClaimGate mount in __root during
compose. Keep them on fork/changes so overlays only own client-specific
code; Discord bot ResponseBridge stays on fork/discord.

Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza added a commit that referenced this pull request Aug 4, 2026
Discord #266 landed OmegentDeepLinkCoordinator, deepLinks helpers, and
ChatView scroll on the discord overlay. Those are shared web surfaces and
collided with identity's IdentityClaimGate mount in __root during
compose. Keep them on fork/changes so overlays only own client-specific
code; Discord bot ResponseBridge stays on fork/discord.

Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza added a commit that referenced this pull request Aug 4, 2026
Discord #266 landed OmegentDeepLinkCoordinator, deepLinks helpers, and
ChatView scroll on the discord overlay. Those are shared web surfaces and
collided with identity's IdentityClaimGate mount in __root during
compose. Keep them on fork/changes so overlays only own client-specific
code; Discord bot ResponseBridge stays on fork/discord.

Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza added a commit that referenced this pull request Aug 5, 2026
Discord #266 landed OmegentDeepLinkCoordinator, deepLinks helpers, and
ChatView scroll on the discord overlay. Those are shared web surfaces and
collided with identity's IdentityClaimGate mount in __root during
compose. Keep them on fork/changes so overlays only own client-specific
code; Discord bot ResponseBridge stays on fork/discord.

Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
patroza added a commit that referenced this pull request Aug 5, 2026
Discord #266 landed OmegentDeepLinkCoordinator, deepLinks helpers, and
ChatView scroll on the discord overlay. Those are shared web surfaces and
collided with identity's IdentityClaimGate mount in __root during
compose. Keep them on fork/changes so overlays only own client-specific
code; Discord bot ResponseBridge stays on fork/discord.

Co-authored-by: T3 Code PR Stack <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants