sequentialthinking: the thought box's header row is 2 columns narrower than its border
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- devtools
Research direction
Start in the sequential-thinking server's code that draws the stderr thought box, where the header row and the border rows are built; the issue does not name the file. Compare how the header is padded with how the border width is computed, and reuse the colour-code stripping that #5000 added. Done when the header, the top border and the bottom border of a thought box with an emoji have the same display width, and the change is checked by logging a sample thought and comparing the rows.
Written by the indexing model from the issue text.
Description
Problem
The sequential-thinking server's thought log (stderr) draws each thought in a box whose header row is 2 columns narrower than its border rows, so the right edge of the header does not line up:
┌──────────────────┐
│ 💭 Thought 1/3 │
├──────────────────┤
#5000 fixed the box's width depending on colour codes and the undefined labels; the header row was already unpadded before that fix (2026.8.31 shows the same misalignment) and was out of its scope.
Found while verifying the v1.0.0 release ledger (#5080). Cosmetic: the log is diagnostic output on stderr, not part of any tool result.
Expected
The header row is padded to the border's width, measured on the text without colour codes (and accounting for the emoji's display width), so all three rows align.
- Dominant language
- JavaScript
- Stars
- 91.2k
- Forks
- 11.8k
- Avg merge
- 6h 20m
- Merged PRs (30d)
- 117
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from modelcontextprotocol/servers
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
modelcontextprotocol/servers#5134 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
modelcontextprotocol/servers#5071 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
modelcontextprotocol/servers#5059 · 2 comments ·
Maintainers usually reply within 1 day
-
mcp-server-fetch: `fetch` prompt returns JSON-RPC error code 0 with the raw exception text for an invalid URLMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
modelcontextprotocol/servers#4914 · 1 comment ·
Maintainers usually reply within 1 day
-
CLAUDE.md: tool-naming rule (kebab-case) disagrees with filesystem and memory serversPossibly taken @liang0417 claimed this 15 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
modelcontextprotocol/servers#4892 · 1 comment ·
Maintainers usually reply within 1 day
All issues in modelcontextprotocol/servers
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
nodejs/node#66743 · 1 reaction ·
Maintainers usually reply within 1 day
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OWASP/cve-lite-cli#1335 ·
Maintainers usually reply within 1 day
-
Channels status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
mastra-ai/mastra#27093 · 1 comment ·
Maintainers usually reply within 1 day
-
category/development priority/P1 scope/ci-cd scope/testing status/ready-for-agent type/bug
Difficulty 1/5 Under an hour Newbie friendliness 72/100
QwenLM/qwen-code#14225 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100