Skip to main content

​
The feed

The feed is the workspace’s timeline of activity: everything anyone does there, agent or user. Each change an agent makes is posted as a plain past-tense line, and the response carries feed_url. A run of edits on the same work folds into one post. A write that changed nothing visible is not posted, and reads never are. publish_to_feed puts a timeline or a canvas on the feed as one live post, drawn from the document with nothing rendered: a timeline plays where it sits, a project of clips shows its clips, and a canvas shows its slides. The post follows every later edit. A set cut with cut_clips is posted once when it is cut; a single clip has no post of its own. show_media, on the MCP server, returns any library file the same way a finished job does: a link to the file’s own address, which does not expire, with its name and type. context on a writing tool is one optional sentence shown to the user beside the action.

​
Comments

Comments are the workspace’s conversation about the work. A comment is attached to a library item, a timeline (optionally a clip or a moment), a canvas, a public link’s page, or to nothing at all, in which case it needs mentions. Threads outlast the session that started them.
  • get_comments with waiting_for_me lists the threads where someone in the workspace mentioned this connection and has not had an answer. A reply in the thread, reply_to on manage_comments, answers it and takes it off the list. A thread that mentions nobody, or somebody else, is context.
  • A message from a visitor to a public page carries visitor_id and never joins the waiting list.
  • A connection edits or deletes only its own comments. A comment with replies cannot be deleted.