How to show message if usage limit is reached?

[pixlmint]

I use claude code through my claude pro subscription, and there's a fairly low usage limit which I'll reach regularly during more serious work.

When I use claude code in the CLI directly, it shows a message "usage limit reached, resets at 12pm".

In CodeCompanion, the chat just stops, making it look like claude was just done with whatever I told it to do.

I'd really appreciate it if the plugin could somehow notify me that this isn't a regular interruption. If it can tell me when usage limit resets, that'd be great, but really not a requirement. I'd just appreciate if it didn't fail silently.

[olimorris]

You'd need to see if this is in the ACP protocol. I'd be happy to support this.

[pixlmint]

It doesn't look like it's in the scope of ACP Protocol. All it returns is an empty response.

I intentionally used up my quota, then manually sent a prompt to the ACP, and this is the response:

{
  "jsonrpc": "2.0",
  "id": 3,
  "result": {
    "stopReason": "end_turn"
  }
}

So it seems like this can't really be done right now. But maybe one improvement could be that CodeCompanion gives some message when the user tried sending a message, and the adapter returned an empty response?

[olimorris]

I'm reluctant to introduce customizations that are outside of the spec and end_turn is very generic. Checking for an empty response doesn't feel very robust. This might trigger persistent warnings for other agents.

I recall that Claude Code did notify me via CodeCompanion over the xmas period when I reached my usage limit. Checking my logs it output:

[ACP::Handler] Internal error: Limit reached · resets 12pm (Europe/London)

[pixlmint]

Yeah that's fair, and if I wanted this I could probably achieve the same by adding an on_exit callback.

I recall that Claude Code did notify me via CodeCompanion over the xmas period when I reached my usage limit. Checking my logs it output:

I checked ~/.local/state/nvim/codecompanion.log, and I can't find anything of the sort in there, even with the log level set to INFO. So maybe it's a change on Anthropic's side?