Collaboration

Name tags, comments in the code and suggested changes

See who each cursor belongs to, read comment threads right under the lines they're about, suggest a change someone can apply in one click, and react or reply in chat.

4 min readUpdated 26 Oct 2026

Name tags on cursors

Every teammate's cursor carries their name in their colour, like in VS Code — on phones too. In Editor settings → Teammates' name tags choose Always, While typing (the tag shows while they type, then fades) or Hover (no tag; point at the cursor to see who it is — on a phone, where there's no hover, the cursor shows without a name). KODEO for VS Code follows the same setting.

Comments in the code

An open comment thread shows as a small card under the line it's about — who wrote it, the start of the comment, how many replies. Click or tap it to open the thread in the Comments panel (the panel opens if it was closed). Turn the cards off in Editor settings → Comments in the code; the line stays highlighted and the margin icon stays.

Type @ in a comment or in chat and everyone in the workspace is offered — people in the room first — narrowing as you type. Pick one with the arrows and Enter (or a tap) and they get a notification.

Suggesting a change

When you comment on a selection, tick Suggest a change and edit the text. The card in the code then shows the lines it would remove and add, with an Apply button, and the thread in the Comments panel shows the same diff. Anyone who can edit the file can apply it: the lines are replaced (in the live session, so it shows for everyone at once), the thread says who applied it, and whoever suggested it gets a notification. If those lines have changed since the suggestion was made, nothing is applied — KODEO says so, and you make the change by hand or ask for a new suggestion.

In VS Code a thread with a suggestion has an Apply Suggestion button in its title bar. To suggest a change there, select the lines and run KODEO: Suggest a Change to These Lines (also on the right-click menu): it copies a ``` `suggestion ``` block with those lines and opens the comment box — paste, edit the lines, add a note and press Comment.

From the terminal, kodeo comments shows the diff, and kodeo comment apply <id> (inside the project's linked folder) puts the change into your copy of the file, pushes that file and marks the suggestion applied.

Reactions and replies

React to a comment or a chat message with 👍 ❤️ 👀 🚀 ✅ or 😄. In chat, Reply quotes the message you're answering — click the quote to jump to it.

Chat understands a little formatting: wrap code in three backticks for a coloured block, or one backtick for inline code. Write a file — src/app.ts, ./App.css, or a file and line like src/app.ts:42 — and it becomes a link that opens it (at that line). A bare file name works when only one file in the project has it, and the case doesn't have to match; names that aren't files in the project stay plain text. When you open the chat, a New line marks where the messages you haven't read start.

On a phone, the Team button and its People, Comments, Chat and History tabs show how many new messages, comments and checkpoints are waiting (People shows how many are here). When a message or a comment arrives while its panel isn't open — on a laptop or a phone — a small toast says who and what, with Open chat or Open the thread; several in a row become one toast ("3 new messages in chat"). A reply to your message says "… replied to you", and a reaction to one of your messages gets a toast too ("Meera reacted 🚀 to your message") and counts on the Team button. With the panel open there's no toast, and a mention shows only once.

Toasts stay out of the way of your code. On a laptop the newest sits in the corner with the others tucked behind it ("+2") — point at it to see them all. On a phone a toast is one line under the top bar: tap it for the whole text, tap +1 to see the rest, swipe it up or sideways to put it away. VS Code's chat has replies, reactions and file links too, and kodeo chat shows replies and reactions.

Still have a question about this?

Assist answers from this article — in any language.

More in Collaboration