Repository navigation
Clearer instructions and descriptions, strict arguments, redaction kinds, reply topics, size wording - #15
Merged
Conversation
…every reply, clarify size - Redact secret access keys after labels written in words or with hyphens. - send_message and reply results add redacted: the kinds of secret replaced. - reply reports the thread root's topic for replies anywhere in the thread. - size is the size the host stores: compressed only on received messages. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ments - Server instructions: fmsg terms, the inbox routine, finding a thread by topic; repeats cut. - Shorter descriptions where results carry the detail; wait_for_message split into parts. - Every input parameter described; unknown arguments are rejected. - send/reply/add_recipients report resolved short names; warnings say what to tell the user. - whoami's text gives the server version. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
markmnl
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Round four of fixes from live testing in a chat host, plus a pass over the server instructions and tool descriptions by a model that used the server with no prior knowledge of fmsg.
Results
send_messageandreplyresults (andFmsgClient.send()/redactSecrets()) name the kinds replaced inredacted, e.g.["access_key_id", "github_token"].resolvedandwarnings:send_message,replyandadd_recipientsreport short names and the address each became; send results put what to tell the user (redacted secrets, resolved short names) inwarnings.thread_topicon replies: a reply anywhere in a thread reports the root's topic, not only a reply to the root.sizewording: a receiving host stores the compressed wire body, while a sender's copy keeps the uncompressed length, sosizeis described as the size the host stores. The text reads "N bytes, sent compressed".whoamitext gives the server version. Its structured result is unchanged since 0.2.5, so hosts with cached schemas keep working.Inputs
important,no_reply, attachment fields, theget_threadlimits,max_inline_bytesand others.Instructions and descriptions (about the same total size as before; the small growth is mostly
additionalProperties: falsefrom strict inputs)mark_read, and say how to find a thread by topic. Repeats are cut. Some chat hosts don't load server instructions, so tool descriptions keep what each tool needs.wait_for_messageis split into when / loop / skipped / limits.delivery_statusandwhoamiare trimmed.get_threadsays where other branches are, andadd_recipientssays added people can read the message and its attachments.219 tests pass.
🤖 Generated with Claude Code