Melso Agents is available only internally or by private invitation. Agents-specific features require existing access. For the autónomo fiscal service, see Get started.
/input to request execution. /messages posts discussion without scheduling a Run. On task.needs_input, fetch the interaction identified by the event and answer as its recipient. Answering or declining can enqueue a continuation Run; use the Task ID to track it.
A completed Run’s reply is the newest message with role: "assistant" whose run_id is that Run’s ID. The Messages reference defines these fields on TaskMessageResponse, also used by task.message stream events. Melso stores the reply with secret-looking values redacted. A reply that arrives double-escaped, with no real line break inside it but \n or \r escape sequences in its place, is decoded (\n, \r, \t and \\); leading and trailing line breaks do not count. Any single-line reply that contains \n or \r is decoded the same way, including a path such as C:\new\folder. Other replies keep their backslashes, so code and paths in a multi-line answer stay intact. The Run’s result.output keeps the raw harness text, so read the reply from the messages. kind: "no_response" marks a Run that finished without text or attachments, and a message with failure_reason reports a Run that stopped.
Clarification payloads
payload.questions contains 1–20 objects with unique id:string, label:string, type:string, optional required:boolean, and options:[{value:string,label:string}] for selection types. Supported types are text, textarea, date, boolean, number, single_select, multi_select. Answers use matching JSON types; multi-select is an array of strings. Omit optional unanswered keys; an empty string is not a skip. Required answers cannot be omitted.
Example respond body: {"response":{"answers":{"approach":"durable","budget":100}}}. Use the Interactions reference with the IDs and types from the stored questions.
Connection interactions use payload.connect:string[] instead of questions. They require the recipient to complete account authorization; posting arbitrary answers does not bypass the server connection check.