inbox/history show a multi-line message body with a literal \n
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- bash
- Domain
- cli
Research direction
Start by reading inbox.sh and history.sh, which are named as the affected entry points, and trace how each displays a message body. Check how multiline bodies are represented and rendered; the example shows literal \n on one line. Done when both commands display body line breaks as indented continuation lines while keeping each message visibly grouped.
Written by the indexing model from the issue text.
Description
A message whose body has line breaks is shown by inbox.sh and history.sh with the line breaks as the two characters \n, on one line:
[2026-10-26T05:27:28Z] kairan: [1] notice text\n posted by: koit seen by: no one yet
This came from an ext-tool reply (its handle printed two lines), but any multi-line body is shown the same way. It reads as broken output.
Expected: the body's line breaks are shown as line breaks, with the continuation lines indented under the message header so one message stays visibly one message.
- Dominant language
- Shell
- Stars
- 1.5k
- Forks
- 156
- Avg merge
- 19h 36m
- Merged PRs (30d)
- 213
Getting set up
- No Dockerfile or Docker Compose file
- No 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 fujibee/agmsg
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
plugin install: the confirmation hint names 'agmsg' even for an install with another --cmd nameOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
agmsgd (v1.6.0, Windows): a dead agmsgd is never restarted (the launcher exits 0, so RestartOnFailure never fires)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
-
Renovate config partially updates OVMS URLPossibly taken @farshidtz claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
type:outdated
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
stephrobert/blog-roadmap#138 ·
-
Regression: IME preedit still shown in plaintext on lock/polkit — #13002 fix is not in 4.0.6Possibly taken @AnPod claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
fullsend-ai/agents#1833 · 2 comments ·
Maintainers usually reply within 1 day