limits: raise message body cap 1k → 4k (catches ~95% of conversational overflow)
This commit is contained in:
parent
0adce04a04
commit
15f141801b
5 changed files with 22 additions and 21 deletions
|
|
@ -152,7 +152,7 @@ pub struct RecvArgs {
|
|||
#[derive(Debug, serde::Deserialize, schemars::JsonSchema)]
|
||||
pub struct RemindArgs {
|
||||
/// Body that lands in your inbox when the reminder fires (sender
|
||||
/// will appear as `reminder`). Soft cap at 1 KiB inline — anything
|
||||
/// will appear as `reminder`). Soft cap at 4 KiB inline — anything
|
||||
/// larger gets auto-persisted to a file under
|
||||
/// `/agents/<you>/state/reminders/auto-<ts>.md` and the inbox
|
||||
/// message becomes a short pointer. Pass `file_path` if you want
|
||||
|
|
@ -322,7 +322,7 @@ impl AgentServer {
|
|||
time (sender will appear as `reminder`). Use for self-paced follow-ups: 'check task \
|
||||
status in 60s', 'retry failed deploy at 14:00 UTC', 'nudge me when the operator's \
|
||||
deploy window opens'. Set EXACTLY ONE of `delay_seconds` (fire N seconds from now) \
|
||||
or `at_unix_timestamp` (fire at absolute epoch second). Body soft-caps at 1 KiB \
|
||||
or `at_unix_timestamp` (fire at absolute epoch second). Body soft-caps at 4 KiB \
|
||||
inline — anything larger gets auto-persisted to a file under your \
|
||||
`/agents/<you>/state/reminders/` dir and the inbox message becomes a short pointer; \
|
||||
pass `file_path` if you want to control the destination yourself. Returns \
|
||||
|
|
@ -455,7 +455,7 @@ pub struct AnswerArgs {
|
|||
/// Id of the question being answered — comes from the
|
||||
/// `question_asked` event in your inbox.
|
||||
pub id: i64,
|
||||
/// Free-text answer body. Soft-capped at 1 KiB by the same
|
||||
/// Free-text answer body. Soft-capped at 4 KiB by the same
|
||||
/// `MESSAGE_MAX_BYTES` limit as `send`; keep it short or write the
|
||||
/// detail to a file and pass a path.
|
||||
pub answer: String,
|
||||
|
|
@ -750,7 +750,7 @@ impl ManagerServer {
|
|||
time (sender will appear as `reminder`). Use for self-paced manager follow-ups: \
|
||||
'recheck pending approval in 10m', 'nudge alice if she hasn't replied by 14:00 \
|
||||
UTC'. Set EXACTLY ONE of `delay_seconds` (fire N seconds from now) or \
|
||||
`at_unix_timestamp` (fire at absolute epoch second). Body soft-caps at 1 KiB \
|
||||
`at_unix_timestamp` (fire at absolute epoch second). Body soft-caps at 4 KiB \
|
||||
inline — anything larger gets auto-persisted to a file under `/state/reminders/` \
|
||||
(the manager's own state mount) and the inbox message becomes a short pointer. \
|
||||
Pass `file_path` if you want to control the destination yourself."
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue