Sharing & collaboration

A canvas is a shared, live space. Everyone in it sees the same frames, documents and chats, with changes appearing as they happen. If a teammate asks the agent for something, you watch it stream in too.

Sharing a canvas

As the owner, click Share in the canvas’s top right, or Share in the canvas menu on the home screen. Invite people by the email address of their Screenplay account. People with access lists everyone; Remove takes someone off, after you confirm.

There are two roles:

• Owner can rename, share, and delete the canvas.
• Collaborators can do everything else: add repositories and start chats (from the sidebar or Canvas settings), chat with the agent, and edit the canvas. They can pin the canvas and file it into their own folders. Their Delete is Leave.

There’s no public link sharing. Copy link copies the canvas’s address, but only people with access can open it.

Seeing each other

• Cursors. Everyone’s pointer shows on the canvas with their name, in their color. Selections are outlined in that color too.
• Avatars. The top right shows who’s here. Click an avatar to follow that person: your view tracks their viewport as they pan and zoom. Click again, or your own avatar, to stop.
• Cursor chat. Press / to type a short message (up to 140 characters) that floats next to your cursor for everyone to see. ↵ or Esc closes it.

In a chat, each message shows the name of whoever sent it, and a question the agent asked says who answered it. Commits are made under the name of whoever sent the message, so git history stays accurate on a shared canvas.

Comments

Press C (or pick Comment in the toolbar), hover a frame or mockup to outline the element under the pointer, then click to pin a comment to it. The comment is anchored to the chat, the route and the element, so its pin follows the element and shows only while the frame is on that route.

Type your comment and click Comment (⌘ ↵).

Pins are numbered in the order their threads were started and are highlighted when unread. Open a pin to see its thread in a card beside the element: reply (type @ to mention someone), Resolve or Reopen, edit your own comments, and use the card’s menu for Mark as unread or Delete thread.

The comment button in the top bar shows how many threads are open, with a dot when some are unread. It opens the Comments panel, which groups threads by frame and route behind Open, Mine, Unread and Resolved filters. J and K step through the threads, opening each one’s card, and E resolves or reopens it. The eye in the panel’s header hides the pins. A comment whose frame or element no longer exists is listed as Detached. In play mode you see and add the same threads.

Send threads to the agent

A comment can go straight to the agent that builds what it’s pinned to. Pick Send to agent from a thread card’s menu, or tick threads in the Comments panel and click Send N to agent at its bottom. Only open threads on a chat whose code is running get a checkbox. Threads for the same chat go to its agent together, as one message that names each of them. A thread on a document goes to the chat that wrote it (see Documents).

Each thread then shows where the agent is with it: Queued, Agent working, and finally Addressed. When it’s addressed, the agent’s reply is added to the thread, and the chip names the commit it made, if any. Resolving the thread is still up to you. If the agent’s turn fails or is stopped, the thread drops its status so you can send it again.

Comment on document text

Select text in a document and click Comment at the end of the formatting toolbar. The composer opens at the document’s right edge with the quoted passage and its line number, and the passage stays highlighted while you write. Once you post, the passage keeps a highlight and the thread’s pin sits beside it. Click the highlight or the pin to open the thread.

With the Comment tool on (C), you can also drag across a document’s text without opening it for editing. Letting go opens the same composer on that passage. Click without dragging to pin a comment to a spot instead.

Terminal tabs stay private

Terminal tabs belong to the person who opened them and aren’t visible to collaborators.