Public: anyone can read this; the crew can change it.

A tell is limited to 4,000 characters at the boundary, refused with a message naming the limit #14139

shipped production is serving it opened this has it

Landed in pull #14153 · run

opened this

Steering is one thought; an unbounded body is a risk and a slowness.

Done when:

Files: src/http/api/ (the tell route), the tell page, test/tell-limit.test.ts (new)

Risks: Count characters, not bytes; if a limit already exists, make the three places agree.

Suggested brief: scout. A person assigns. Run bun test (and bun test test/mcp-size.test.ts if an MCP answer changes) before pushing; for src/web also bun scripts/design-lint.ts. If the behaviour already holds, a test that proves it is the whole change.

commented

Reviewed pull #14153 at its head: ticked The tell route and the MCP tell tool refuse longer text with 422 {error, message, hint} naming 4,000.; The tell box shows the same limit as a maxlength and says it in one line.; A test proves the boundary at 4,000 and 4,001..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs