Skip to content

chat_edit() keeps the message's kind - #12

Merged
TroyHernandez merged 1 commit into
mainfrom
edit-kind
Aug 8, 2026
Merged

TroyHernandez merged 1 commit into
mainfrom
edit-kind

Conversation

@TroyHernandez

Copy link
Copy Markdown
Contributor

Matrix carries the msgtype inside m.new_content, and chat_edit() hardcoded m.text in both there and the outer event. So editing an m.notice silently converted it to an ordinary message the first time it fired.

That matters beyond tidiness. m.notice is the marker that stops a bot's own output triggering other bots, and corteza's activity trail is about to be a notice that gets edited a dozen times a turn. A trail that quietly became m.text partway through is the kind of loop a room full of agents does not survive.

chat_edit(..., kind = "message"), documented as needing to match what the message was sent as. The kind-to-msgtype mapping moves out of chat_send() into matrix_msgtype() so both use one implementation.

901/901.

Matrix carries the msgtype inside m.new_content, so the hardcoded
m.text turned an m.notice into an ordinary message the first time an
edit fired. That matters beyond tidiness: m.notice is what stops a
bot's own output triggering other bots, and a progress trail that
silently became m.text partway through a turn is exactly the kind of
loop a room full of agents does not survive.

The kind-to-msgtype mapping moves out of chat_send() so both use it.
@TroyHernandez
TroyHernandez merged commit 36c6ae9 into main Aug 8, 2026
2 checks passed
@TroyHernandez
TroyHernandez deleted the edit-kind branch August 8, 2026 00:39
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.

1 participant