Repository navigation
parro-api-client 0.7.0
·
14 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
Reply from the terminal: chat-send sends a text message to a chat you are in. This changes the
client's promise again: it reads, and it can change two things, only when you ask: mark items as
read, and send a text message. Real people receive what you send, under your name, and as far as we
know a message cannot be taken back.
Added
chat-send ID "text"(or--file PATH,--file -for standard input). It shows the chat, who
receives the message and the exact text, and asksSend this message? [y/N].--yesskips the
question for scripts; without a terminal and without--yes, nothing is sent.- It refuses empty text and chats that are archived, that you have left, that have replies switched
off, or that are with a bot. - The MCP tool
parro_send_chat_message, only when you setPARRO_ALLOW_SEND_CHAT=1(a switch of
its own). Withoutconfirm: trueit only returns the preview, and it is marked as destructive so
MCP clients ask first. An assistant also reads what others write, so please read the warning in
the README before you switch it on. - The spec describes
POST /chatroom/{id}/chatmessage, and says what is not known about it.
Changed
- A message is never sent twice on its own: after a timeout or a server error the client says it may
or may not have arrived. The text is never logged or stored. - The README, the help text,
SECURITY.mdand the User-Agent describe the new promise. - Writes no longer follow redirects.
- Every MCP tool now states all four hints (
readOnlyHint,destructiveHint,idempotentHint,
openWorldHint), matching what it does. MCP clients can use them to decide when to ask you.