Agent workflow

The recommended loop for implementing Montra tickets and reporting progress back.

Montra documents are built from screen recordings: a person narrates what they want while pointing at real UI, and Montra turns that into tickets whose bodies are markdown implementation specs. The connector gives an agent everything the person captured — and a way to report progress back. This is the loop that works well.

1. Find the work

   Start from list_documents (optionally narrowed by a folder from list_folders), or from a pasted share link via get_document_by_share_url. Then open the document with get_document — it returns the document, its folder, its latest generation status, and the visible tickets in order.

2. Read the full spec before implementing

   List views omit ticket bodies. Call get_ticket for each ticket you are about to work on — the body field is the markdown implementation spec.

   Then fetch get_ticket_images and actually look at the images. They are real UI captures the person marked up while recording — arrows, boxes, and notes are instructions, not decoration. For surrounding intent, get_transcript returns the narration; treat it as supporting context, the tickets remain the spec.

3. Clarify before guessing

   If a ticket is ambiguous or underspecified, ask the person clarifying questions first instead of implementing a guess. Once resolved, record the clarified scope on the ticket itself with update_ticket so the spec stays true.

4. Implement, then report back

   As soon as a ticket is finished, call set_ticket_status with done — that is how progress reaches the person who recorded it. If you exported the ticket to Linear or Notion, record it with link_ticket_issue so the Montra ticket links back to the downstream issue.

Rules of the road

• Overwrites are total. update_ticket and update_document replace each field you pass outright — send the complete new text, never a fragment or a diff. Fields you omit are untouched.
• Edits are protected. Ticket writes made through the connector are flagged as manual edits, so a later background generation will not silently overwrite them.
• Signed URLs are short-lived. Image and media URLs from get_ticket_images (and member-resolved share links) expire — fetch them while working the ticket rather than storing them.
• Scope is the bound workspace. Anything outside the workspace chosen at consent reads as not found. Share links are the one deliberate exception.
• Deletes are soft. delete_ticket removes the ticket from the document but it stays recoverable from the Montra app.