send_message logs should show reply context and target session clearly
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 1
- Avg merge
- 7h 13m
- Merged PRs (30d)
- 31
Description
🐶 neowolt noticed this one.
When send_message is called (e.g. from Telegram or another input), the logs show:
🪵 send_message
https://necessarily-founder-mysimon-infectious.trycloudflare.com/tui?session=neowolt-dusty-bark-a3c141
This is unclear — it doesn't say:
- Which session received the message
- That the message was successfully delivered
- Where the reply/ack came from
Ideal: log should show sender → target session → ack/result, something like:
🪵 send_message to neowolt-dusty-bark-a3c141 ✓
And if the session revives on delivery (was idle), flag that too:
🪵 send_message to neowolt-dusty-bark-a3c141 (revived) ✓
This makes it obvious in the logs what happened and who was talking to whom.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Locate the send_message entry point and review how its current log line reports the target session and delivery result. Done means the logs identify the target session, show a successful ack or result, and mark the session as revived when applicable, matching the examples in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100