After PASS on the IRC listener, the NOTICE that confirms it told the user to reconnect with PASS and their nick. The IRC listener cannot add a connection to an existing session, so that step does not work. The notice now reads:
Password set. Another client can log in to this session over the HTTP API: POST /api/v1/login with your nick and this password.
This is what README.md says in Multi-Client Model and in the PASS section: POST /api/v1/login is the only way to add a client to an existing session.
TestHandlePassPostRegistration in internal/ircserver now checks the whole notice text, not just its first two words.
What a reader might trip over: a PASS sent before registration gets no confirming notice at all, so that path is unchanged.
Disclosures:
Judgement call: the notice does not say that closing the IRC connection ends the session, along with any client logged in to it over the HTTP API. The issue asked for only the two facts above.
Model: opus-5-5
After `PASS` on the IRC listener, the `NOTICE` that confirms it told the user to reconnect with `PASS` and their nick. The IRC listener cannot add a connection to an existing session, so that step does not work. The notice now reads:
`Password set. Another client can log in to this session over the HTTP API: POST /api/v1/login with your nick and this password.`
This is what `README.md` says in Multi-Client Model and in the `PASS` section: `POST /api/v1/login` is the only way to add a client to an existing session.
`TestHandlePassPostRegistration` in `internal/ircserver` now checks the whole notice text, not just its first two words.
What a reader might trip over: a `PASS` sent before registration gets no confirming notice at all, so that path is unchanged.
Disclosures:
- Judgement call: the notice does not say that closing the IRC connection ends the session, along with any client logged in to it over the HTTP API. The issue asked for only the two facts above.
Model: opus-5-5
After PASS on the IRC listener, the confirming NOTICE told the user to
reconnect with PASS and their nick. The IRC listener cannot add a
connection to an existing session, so that step does not work. The
notice now says the password is set and that another client can log in
to the session over the HTTP API with POST /api/v1/login, as the README
describes. The test now checks the whole notice text.
Model: opus-5-5
PASS: after PASS on the IRC listener, the confirming NOTICE now points to POST /api/v1/login with the nick and this password, which works, instead of a reconnect over IRC, which does not.
Judgement call: the notice does not say that closing the IRC connection ends the session for every client logged in to it; I do not count that as misleading, because the notice claims nothing about how long the session lasts and README.md says so.
Model: opus-5-5
PASS: after `PASS` on the IRC listener, the confirming `NOTICE` now points to `POST /api/v1/login` with the nick and this password, which works, instead of a reconnect over IRC, which does not.
Judgement call: the notice does not say that closing the IRC connection ends the session for every client logged in to it; I do not count that as misleading, because the notice claims nothing about how long the session lasts and `README.md` says so.
Model: opus-5-5
clawbot
merged commit acb9527944 into next2026-11-02 05:27:28 +01:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
After
PASSon the IRC listener, theNOTICEthat confirms it told the user to reconnect withPASSand their nick. The IRC listener cannot add a connection to an existing session, so that step does not work. The notice now reads:Password set. Another client can log in to this session over the HTTP API: POST /api/v1/login with your nick and this password.This is what
README.mdsays in Multi-Client Model and in thePASSsection:POST /api/v1/loginis the only way to add a client to an existing session.TestHandlePassPostRegistrationininternal/ircservernow checks the whole notice text, not just its first two words.What a reader might trip over: a
PASSsent before registration gets no confirming notice at all, so that path is unchanged.Disclosures:
Model: opus-5-5
PASS: after
PASSon the IRC listener, the confirmingNOTICEnow points toPOST /api/v1/loginwith the nick and this password, which works, instead of a reconnect over IRC, which does not.Judgement call: the notice does not say that closing the IRC connection ends the session for every client logged in to it; I do not count that as misleading, because the notice claims nothing about how long the session lasts and
README.mdsays so.Model: opus-5-5