Response Delivery #234

New issue

Closed

opened 2026-07-15 11:34:20 +00:00 by Mark · 1 comment

Mark commented

2026-07-15 11:34:20 +00:00

Owner

Phase 4: Response Delivery

Goal: Format mesh results for Discord delivery — handle the 2000-char message limit, multi-message for long responses, rich embeds, typing indicators, and file attachments.

Approach candidates:

Split long responses at natural boundaries (paragraphs, code blocks) into Discord messages
Embeds for structured output: title, description, fields, color-coded by intent type
Typing indicator while mesh intent is processing (periodic progress updates)
File uploads for artifacts (code snippets, reports, generated content)
Model-generated summary + full artifact as follow-up

Outputs:

Response formatter in runtime/discord_ingress.py or separate runtime/discord_response.py
Embeds for structured output types (research findings, write artifacts, status reports)
Chunked message delivery for long content
Typing indicator integration during processing

Acceptance criteria:

Messages under 2000 chars delivered as single message
Messages over 2000 chars split across multiple messages with continuation markers
Research results formatted as Discord embed (title, summary, key findings as fields)
Write artifacts sent as embedded preview + optional file attachment
Bot shows typing indicator while mesh is processing
Error messages formatted distinctly (red embed, clear error prefix)
Code blocks preserve formatting in mono-spaced Discord blocks

Files touched: runtime/discord_ingress.py (amend), runtime/discord_response.py (create), runtime/__init__.py (amend), tests/unit/test_discord_response.py (create)

Decomposed from mesh-seed#134

## Phase 4: Response Delivery **Goal:** Format mesh results for Discord delivery — handle the 2000-char message limit, multi-message for long responses, rich embeds, typing indicators, and file attachments. **Approach candidates:** - Split long responses at natural boundaries (paragraphs, code blocks) into Discord messages - Embeds for structured output: title, description, fields, color-coded by intent type - Typing indicator while mesh intent is processing (periodic progress updates) - File uploads for artifacts (code snippets, reports, generated content) - Model-generated summary + full artifact as follow-up **Outputs:** - Response formatter in `runtime/discord_ingress.py` or separate `runtime/discord_response.py` - Embeds for structured output types (research findings, write artifacts, status reports) - Chunked message delivery for long content - Typing indicator integration during processing **Acceptance criteria:** - [ ] Messages under 2000 chars delivered as single message - [ ] Messages over 2000 chars split across multiple messages with continuation markers - [ ] Research results formatted as Discord embed (title, summary, key findings as fields) - [ ] Write artifacts sent as embedded preview + optional file attachment - [ ] Bot shows typing indicator while mesh is processing - [ ] Error messages formatted distinctly (red embed, clear error prefix) - [ ] Code blocks preserve formatting in mono-spaced Discord blocks **Files touched:** `runtime/discord_ingress.py` (amend), `runtime/discord_response.py` (create), `runtime/__init__.py` (amend), `tests/unit/test_discord_response.py` (create) --- --- _Decomposed from [mesh-seed#134](https://forgejo.tail018ac4.ts.net/Mark/mesh-seed/issues/134)_