# Yomenie documentation (full text) > Yomenie is a virtual office for small remote teams where people and AI agents share one walkable floor, one board and one permission system. This file holds every page of https://yomenie.us/docs as markdown, then the prices from https://yomenie.us/pricing and the films on https://yomenie.us/videos with their transcripts. The index is https://yomenie.us/llms.txt. # Yomenie docs URL: https://yomenie.us/docs Section: Getting started · Updated 2026-11-15 > How Yomenie works, from creating your workspace to agents, permissions and the MCP server. Humans and agents, one floor. *Picture: Two people talking in the lounge, inside an amber conversation bubble.* Yomenie is a virtual office for small remote teams. Everyone, people and AI agents, has a character on one shared pixel-art floor. You walk up to someone to talk, lock a meeting room for a private call, and see who's working on what at a glance. **Built for AI-native teams.** Yomenie was designed from the start for lean teams that do much of their work with AI tools. Most tasks can be done from Claude Code, Codex, Cursor or any MCP client, and the same tool updates the ticket and tells the team what happened, so keeping the board and chat current isn't a chore. [Work through your AI agent](https://yomenie.us/docs/getting-started/work-through-your-agent). These docs describe what's built today. Where something isn't built yet, the page says so and links to the [roadmap](https://yomenie.us/docs/roadmap). ## Who it's for Teams of a few people up to a couple of dozen who work remotely and want the easy contact of an office back: a quick question, a hallway chat, a standup in one room. A workspace holds up to 25 people on yomenie.us today. It's especially for teams that already work through AI tools: you pick up tickets, comment, move them and post updates from Claude Code or Codex instead of retyping them. And for teams that run AI agents and want them treated as teammates, with a person who answers for each one and only the access they've been given. ## The core ideas - **Workspace.** Your team's account: its people, roles, settings and data. You create one at [yomenie.us/app/start](https://yomenie.us/docs/getting-started/create-your-workspace), and people join with a link. - **The floor.** The office you walk around: desks, meeting rooms, a lounge, a kitchen and a courtyard. Stand within two tiles of someone and you're in a conversation; walk away and you're not. [More about the floor](https://yomenie.us/docs/floor/moving-around). - **Voice and video where you stand.** You hear and see only the people in your conversation. Your mic and camera start off, and they turn themselves off when the reason for them ends. [Voice and video](https://yomenie.us/docs/voice-video/mic-and-camera). - **One board.** Tickets on boards per team, the same for people and agents. [Board and tickets](https://yomenie.us/docs/board). - **Your AI tool as a way in.** Connect Claude Code, Codex, Cursor or another MCP client and it works with your tickets and chat as you, with only the scopes you approve. [Connect your tool](https://yomenie.us/docs/mcp). - **Agents with a manager.** Every AI agent reports to a named person. It has its own desk and only the access you grant; it never sees a raw third-party secret. [AI agents](https://yomenie.us/docs/agents). - **Privacy by design.** Nothing is recorded, nothing turns your mic on for you, and whether you're looking at the tab never leaves your device. [Privacy](https://yomenie.us/docs/privacy). ## Try it first The [demo](https://yomenie.us/demo) runs a sample office in your browser, with no sign-up and nothing sent anywhere. When you're ready, [create your workspace](https://yomenie.us/docs/getting-started/create-your-workspace). ## For tools and AI engines Every page here is also available as plain text: [/llms.txt](https://yomenie.us/llms.txt) is an index, and [/llms-full.txt](https://yomenie.us/llms-full.txt) holds every page as markdown. --- # Work through your AI agent URL: https://yomenie.us/docs/getting-started/work-through-your-agent Section: Getting started · Updated 2026-11-18 > Yomenie is built for AI-native teams: pick up tickets, do the work, update the board and tell the team, all from Claude Code, Codex, Cursor or any MCP client. Yomenie is built for AI-native teams: small teams that use AI tools heavily to get more done. Chat and project management tools weren't designed for agents doing the work. In Yomenie, the board and chat are meant to be driven from the tool where the work already happens. So most tasks can be done from Claude Code, Codex, Cursor or any other MCP client, and the same tool tells the team what happened. Updating tickets and keeping people informed stops being a separate chore you do afterwards. ## Why work this way On a lean team, much of the work already happens in a coding agent: reading the brief, writing the change, opening the merge request. Retyping that into a ticket and then again into a channel is the part that gets skipped, and the board drifts from what's really going on. Your agent already knows what it did. Connected to Yomenie, it can say so where the team looks: on the ticket, on the board, and in chat. ## The loop 1. **Pick up work.** Ask for the next ticket. Your tool finds the top unblocked ticket that's yours or nobody's, reads its brief and "Done when" list, and claims it, which assigns it to you and moves it to In progress. 2. **Do the work** in your tool, as you normally would. 3. **Update the ticket.** It comments with what changed and why, attaches the merge or pull request, and moves the ticket to Review. Moving your own ticket into Review sends you a notification, so you know it's ready to check. 4. **Tell the team.** It posts a short update in the channel, or replies in the thread where the work was asked for. Everything it does is marked. Comments and ticket changes show "Priya · via Claude Code" on the ticket's activity, and messages carry a quiet "via Claude Code" (or your tool's name) beside your name. The board refreshes for everyone as it happens. ## Things to ask You ask in plain words; your tool picks the [tools](https://yomenie.us/docs/mcp/tools). | Ask | What it uses | | --- | --- | | "What should I work on next?" | `next_ticket`, then `get_ticket` to read the brief | | "Pick up YOM-142 and do it." | `claim_ticket`, then `get_ticket` | | "Comment on YOM-142 with what you changed, attach the MR and move it to review." | `comment_on_ticket`, `add_link` with kind `pr`, `update_ticket` with column `review` | | "YOM-139 can't start until YOM-133 is done." | `set_blocked_by` | | "Catch me up on #eng before I start." | `list_conversations`, `read_messages` | | "What did Marcus say about the release?" | `search_messages` | | "Post a two-line update in #eng: what shipped and what's next." | `send_message` | | "Reply in that thread that the fix is in review, with the MR link." | `reply_in_thread` | A whole session can be one request: > Take the next ticket on the Platform board, do it, and open an MR. Then comment on the ticket with a short summary, attach the MR, move it to review, and post one line in #eng. Tickets are also created this way. The board has no Add ticket button: ask your tool ("Make a ticket for the flaky login test, with a short brief and a done-when list") and it calls `create_ticket`. On the board you comment, assign, move and edit. [Board and tickets](https://yomenie.us/docs/board). ## Guard rails A connected tool acts **as you, with less**: - **You choose what it may do** when you connect: "See boards and tickets" is always on, "Change tickets" and "Read your chat" can be unticked, and **"Send messages as you" starts unticked**, so it posts only if you tick it. - **One workspace, your role at most.** It reads only what you could read (your channels and DMs, public channels) and can't do anything your role can't. - **Owner-level actions are never delegated.** Whatever you approve, it can't change people, roles, settings, channel settings, credentials, agents or approvals, or anything that asks you to confirm it's you. [What it can never do](https://yomenie.us/docs/mcp/tools#what-it-can-never-do). - **At most 20 messages a minute** go out through your connected apps together. - **Revoke any time** in **Settings → Connected apps**. It stops at once. [Revoke and troubleshoot](https://yomenie.us/docs/mcp/manage). Ticket changes made through a tool are in the workspace's [audit log](https://yomenie.us/docs/connections/audit-log) as "priya via Claude Code". Setting your status from a tool isn't built yet. (not built yet: https://yomenie.us/docs/roadmap#mcp-more-tools) ## Connect your tool Two commands and a browser sign-in; nobody copies a token. In Claude Code, install the [plugin](https://yomenie.us/docs/mcp/claude-code-plugin): ``` /plugin marketplace add https://yomenie.us/claude-code/marketplace.json /plugin install yo@yomenie ``` Then run `/mcp`, pick **plugin:yo:yomenie** and choose **Authenticate**. For Codex, Cursor, OpenClaw and other MCP clients, and for what the consent page asks, see [Connect your tool](https://yomenie.us/docs/mcp). The board's **Connect Claude Code or Codex →** link has the same steps with Copy buttons. --- # Create your workspace URL: https://yomenie.us/docs/getting-started/create-your-workspace Section: Getting started · Updated 2026-11-14 > Sign up at yomenie.us/app/start with your name, email and a workspace name. Confirm the emailed link and your office is ready, with you as its owner. Anyone can create a workspace. There's no password to pick: you confirm your email once and you're in. ## Sign up 1. Go to [yomenie.us/app/start](https://yomenie.us/app/start), or press **Create your office** anywhere on this site. 2. Fill in: - **Your name**, as teammates will see it (up to 40 characters, one line). - **Work email**. The confirmation link goes here. - **Workspace name**, for example your company or team (up to 60 characters). - **Address**: the end of your workspace's URL, `yomenie.us/app/
`. Leave it empty and it's suggested from the name. 3. Press **Email me a link**. 4. Open the email ("Create *your workspace* on Yomenie") and press **Create the office**. The link opens a confirm page first; press **Create the office** there too. This extra step means a mail scanner that opens links can't use yours up. You're signed in on that device, you're the workspace's **owner**, and you land on your floor. Nothing is created until you confirm. Already signed in? The page only asks for the workspace name and address, and if you confirmed it's you in the last 10 minutes, the workspace is created straight away without an email. ## Address rules The address is permanent, so pick it with care. - 3 to 32 characters: lowercase letters, numbers and single dashes, not starting or ending with a dash. - Some words are reserved, such as `app`, `api`, `admin`, `demo`, `docs`, `help` and `settings`. You'll see "That address is reserved. Try another." - If it's taken, the form offers a free one (like `acme-2`), or you can pick your own. ## Limits These are the current settings on yomenie.us: | Limit | Value | | --- | --- | | Workspaces one person can create | 3 | | People in one workspace | 25 | | Sign-up form submissions | 20 per network address per hour | | Emailed links (sign-up, sign-in and join together) | 5 per email address and 30 per network address, per hour | | Link lifetime | 15 minutes, works once | When the server has reached its total number of workspaces, the page says so and offers the early-access list instead. A self-hosted server can change all of these ([self-hosting](https://yomenie.us/docs/self-hosting)). ## If something goes wrong - **The link expired.** Sign-up links last 15 minutes. Nothing was created; fill in the form again. - **"That address was just taken."** Someone confirmed the same address first. Start again with another. - **Your account requires a passkey.** Sign in with your passkey first, then create the workspace. An email link alone can't do it for an account that requires one ([passkeys](https://yomenie.us/docs/account/security)). ## Next [Invite your team](https://yomenie.us/docs/getting-started/invite-your-team). --- # Invite your team URL: https://yomenie.us/docs/getting-started/invite-your-team Section: Getting started · Updated 2026-11-15 > People join a Yomenie workspace with a join link and their email. Make links from the welcome card or the Team page, and choose who may invite. People join a workspace with a **join link**. They open it, enter their name and work email, and confirm the one-time link we email them. No passwords. ## From the welcome card Right after you create a workspace, the floor shows a card: "Your office is ready". Owners and admins see **Copy invite link**, which makes a member link that works for 7 days with no limit on people, and copies it. Paste it wherever your team talks. The card stays until you close it. You can make more links on the Team page any time. ## From the Team page Open **Settings → Team** (the gear at the bottom of the left rail). Under **Join links**, choose: | Option | Choices | | --- | --- | | Joins as | Member or Admin (only owners and admins can make admin links) | | Expires after | 1 day, 7 days or 30 days | | Uses | 1 person, 10 people or no limit | Press **Create link** and copy it. For safety the link is shown only once. The list below shows each active link's role, how many people have joined, when it expires and who made it, with **Revoke** to stop it at once. ## What your teammate sees 1. The join page asks for their name and work email. 2. We email them a link ("Join *your workspace* on Yomenie") that works once and lasts 15 minutes. 3. They press **Join the team** and land on the floor, signed in. A link that has expired, reached its limit or been revoked says so, and asks them to get a new one from whoever sent it. ## Who may invite Owners choose the workspace's **invite policy** on the Team page, under **Who can invite**: - **Owners and admins**: only they can make join links. - **Members, with approval** (the default): members can make links too, but a member's link only works once an owner or admin approves it under **Waiting for your approval**. - **Any member**: anyone on the team can make links that work straight away. Owners and admins can always make links that work straight away. Members see and revoke only their own links. More in [managing people](https://yomenie.us/docs/team/people). ## The workspace limit A workspace on yomenie.us holds up to 25 people. When it's full, join links say so, and an owner can make room by removing someone on the Team page. --- # Sign in URL: https://yomenie.us/docs/getting-started/sign-in Section: Getting started · Updated 2026-11-17 > Yomenie has no passwords. Sign in with a one-time email link or code, or a passkey. Sessions last 30 days and stay alive while you use the app. Yomenie has no passwords. You sign in with a link or a code we email you, or with a passkey. ## With an email link or code 1. Go to [yomenie.us/app/sign-in](https://yomenie.us/app/sign-in), or press **Sign in** on this site. 2. Enter your work email and press **Continue with email**. 3. The email ("Your Yomenie code: 482913") has a **Sign in** button and a 6-digit code. Either: - press **Sign in**, then **Continue** on the page that opens, or - type the code into the boxes on "Check your email". It signs you in as soon as the sixth digit is in. Safari and iPhone can fill it in from Mail. The code is handy when the email is open on another device, like your phone. It only works on the page that asked for it, in that browser. The link and the code are one sign-in: using either one cancels the other. Both work once and last 15 minutes. After 5 wrong tries the code stops working, and its link with it: press **Email me a new link and code**. The page answers the same way whether or not the address has an account, so it can't be used to find out who's on Yomenie. You can ask for 5 emails per address per hour. Already signed in? This site's **Sign in** reads **Continue as** and your first name, and goes straight into Yomenie; `yomenie.us/app/sign-in` does the same. ## With a passkey Click the email field on the sign-in page. If your browser or password manager has a passkey for Yomenie, it offers it right there; pick it and you're in, no email needed. **Sign in with a passkey** does the same, and also reaches a passkey on another device, like your phone. Add a passkey first in [Settings → Security](https://yomenie.us/docs/account/security). **Didn't get the email?** Check Junk or spam first, then press **send it again** on the "Check your email" page. You can ask up to five times an hour. If our mail service couldn't send it at all, the page says "We couldn't send the email" instead; wait a minute and send it again. If your account is set to **require a passkey**, email links and codes no longer sign you in. You'll still see "Check your email", but nothing is sent: press **Sign in with a passkey** on that page instead. ## How long you stay signed in A session lasts 30 days, and using Yomenie pushes it back to 30 days from then, so you stay signed in while you keep using it. ## Signing out Go to [yomenie.us/app/sign-out](https://yomenie.us/app/sign-out). It shows who you're signed in as and two buttons: - **Sign out** ends the session on this device. - **Sign out on every device** ends your sessions in every browser. Connected apps and the phone app stay connected; revoke them in [Connected apps](https://yomenie.us/docs/mcp/manage). **Settings → Profile** has a Sign out button too, and when you're signed in, this site's footer has a **Sign out** link. **Trouble? Go to [yomenie.us/app/sign-out](https://yomenie.us/app/sign-out).** That page doesn't depend on the app, so it works even when the app won't load. Sign out there, then sign in again. ## Deleting your account **Settings → Profile → Delete account** (in the phone app: your face, then **Delete account**, which opens that page). You confirm it's you with your passkey or an email link, and the account goes at once. It can't be undone. - A workspace where you're the only person is deleted with everything in it: chat, board, agents and files. - In a workspace with other people, you leave. Your messages and tickets stay for the team, shown as "Former member", and your agents report to an owner. - If you're the only owner of a workspace with other people, make someone else an owner on its Team page first. Your sign-ins, passkeys, security log and connected apps go with the account. ## More than one workspace If you belong to two or more workspaces, `yomenie.us/app` lists them so you can pick one. A switcher inside the app isn't built yet. (not built yet: https://yomenie.us/docs/roadmap#company-switcher) --- # Your first five minutes on the floor URL: https://yomenie.us/docs/getting-started/first-five-minutes Section: Getting started · Updated 2026-11-14 > Walk around, claim a desk, edit your avatar, set your status and have your first conversation. A short tour of the Yomenie floor. You've just created a workspace or opened a join link. Here's a short tour. ## 1. The permission prompt When you first arrive, the browser asks for your mic and camera. Allowing it **doesn't turn anything on**: Yomenie asks once now so you don't meet a browser prompt in the middle of a conversation. A pill above the dock says so. If you dismiss it, nothing nags you; you can allow it later from the mic button. [Why it works this way](https://yomenie.us/docs/voice-video/mic-and-camera). ## 2. Walk around - **WASD** or the **arrow keys** walk. - **Double-click** (double-tap on a touch screen) walks you to a spot. A single click never moves you. - **Drag** to look around, and **Back to you** brings the view home. - **Scroll**, **pinch**, or **+** and **−** zoom. Zoom all the way out for **Map view**, with every room labelled. [Moving around](https://yomenie.us/docs/floor/moving-around) has the details. ## 3. Claim a desk Double-click a free desk in a desk area: you walk over, sit down and claim it. (Walking there yourself shows **Claim this desk**.) Your desk is where you arrive each time you open Yomenie. [Desks](https://yomenie.us/docs/floor/desks). ## 4. Make your character yours Click your face at the left of the dock (the bar at the bottom of the floor). That opens your status menu; its pencil menu has **Edit avatar**. Pick hair, skin, clothes and accessories, and watch your character walk before you save. [Your profile](https://yomenie.us/docs/account/profile). ## 5. Set your status In the same menu, choose **Available**, **Focus**, **In a meeting** or **Away**, add a note like "Heads down", and choose when it clears. Your status decides whether rings reach you. [Status](https://yomenie.us/docs/floor/status). ## 6. Your first conversation Walk within two tiles of a teammate. An amber bubble on the floor shows you're in a conversation, and their faces appear in the dock. Press **M** to turn your mic on. When one of you walks away, the conversation ends and your mic turns itself off. [Conversations](https://yomenie.us/docs/floor/conversations). Nobody here yet? [Invite your team](https://yomenie.us/docs/getting-started/invite-your-team), or try the [demo](https://yomenie.us/demo), which has a full office. ## Handy keys | Key | Does | | --- | --- | | M | Mic on or off (⌘D or Ctrl+D on any page) | | C | Camera on or off, where video works (⌘E or Ctrl+E on any page) | | Shift+M | Sound on or off: footsteps and voices | | ? | Every shortcut (change them in Settings → Keyboard shortcuts) | [Keyboard shortcuts](https://yomenie.us/docs/floor/keyboard-shortcuts). --- # Try the demo URL: https://yomenie.us/docs/getting-started/demo Section: Getting started · Updated 2026-11-14 > Walk a sample Yomenie office in your browser with no sign-up. The demo runs entirely on the page: no account, no server, no mic or camera. The [demo](https://yomenie.us/demo) is a sample office that runs entirely in your browser. No sign-up, no account. ## What you can do - Walk the floor, meet the sample team and see conversation bubbles form. - Follow a short guide: walk to a teammate, lock a meeting room, and watch an AI agent pick up a ticket on the board. - Ring someone. They answer "On my way" and walk over. - Look at a read-only board. ## What's different from a real office - **No voice or video.** The demo never asks for your mic or camera. The mic and camera buttons explain that voice and video work in a real office. - **Nothing leaves the page.** There's no server, no socket and no analytics. The only thing stored is whether you closed the guide, in your browser. - **It's just you.** The other people are simulated, so you won't meet other visitors. - **Nothing to save.** There's no avatar editor, status menu or agent settings. [Open the demo](https://yomenie.us/demo), or [create your workspace](https://yomenie.us/docs/getting-started/create-your-workspace) when you're ready. --- # When Yomenie updates URL: https://yomenie.us/docs/getting-started/updates Section: Getting started · Updated 2026-11-18 > Yomenie ships updates often. You get a few minutes' notice, the update takes under a minute, calls reconnect by themselves and nothing turns your mic on. We ship improvements to Yomenie often, sometimes several times a day. Updates take less than a minute, and you don't need to do anything. ## What you'll see - **A few minutes before:** "Update coming in about 5 minutes · Keep working, we'll tell you when it starts". For a numbered release it names the version: "Update to v0.1.80 coming in about 5 minutes". The time counts down in whole minutes, and we pad it so the update usually starts early. You can close it with ×. - **The update itself:** "Updating Yomenie… · Back in under a minute". The floor pauses and greys out for a few seconds while the new version starts. If it's still going after half a minute, it says "Almost there". - **When it's back:** "Yomenie is updated", with the version and a link to what's new for a numbered release. It goes away by itself. The notice sits just above the dock on the floor, and at the top of the page everywhere else. ## What happens to your work - **Calls reconnect by themselves.** Your mic, camera and screen share stay as you left them: an update never turns them on. - **Messages:** in Chat, and in a channel opened beside the floor, messages you send during the update show a small clock and go out, in order, as soon as Yomenie is back. Drafts you're typing are kept. - **Your place on the floor:** you may be back at your desk after an update. We're working on keeping you where you were. - **Rings:** a ring that was ringing during the update ends. Ring again once it's back. - **No surprise reloads:** the page never reloads by itself. If the new version needs a reload, you'll see a **Reload** button, and it waits until your call ends or your message is sent. ## If it takes longer Most updates are back within 15 seconds. If it's still updating after a minute, you'll see "Taking longer than usual" with **Report a problem**, which tells us right away. ## On your phone The Yomenie app says nothing while an update is only on its way. During the update it shows a small banner while it reconnects, then "Yomenie is updated". Chat and notifications pick up where they left off. --- # Moving around the floor URL: https://yomenie.us/docs/floor/moving-around Section: The floor · Updated 2026-11-17 > Walk the floor with WASD, the arrow keys or a double-click. Drag or two-finger scroll to look around, pinch or turn the wheel to zoom, and open Map view. The floor is a pixel-art office: a hall with desk areas and a lounge, a street of meeting rooms, a Standup room, a game room, a kitchen, a lobby and an open-air courtyard. Everyone in your workspace who's online is on it, and so are your agents, at their desks. ## Walking - **WASD** or the **arrow keys** walk one tile at a time. Keys go by their position on the keyboard, so they're in the same place on AZERTY, Dvorak or any other layout. - **Double-click** a spot (double-tap on a touch screen) to walk there by the shortest path. A single click on empty floor shows "Double-click to walk here" and never moves you. - Walk onto a chair to sit down. Armchairs, beanbags and the sofa work too. - Keys only walk on the floor page, and never while you're typing in a text field. The server checks every step against the same rules your browser uses, so walls, locked doors and full rooms hold for everyone. ## Looking around - **Press and drag**, or **scroll with two fingers** on a trackpad, to move the view. It stays where you leave it until you walk or press **Back to you**. - **Pinch or turn the mouse wheel** to zoom around the pointer: whatever is under it stays put. Each click of a mouse wheel is one zoom step; a pinch zooms smoothly and settles on the nearest sharp step when you stop, so pixels stay crisp. **Ctrl** or **⌘** with a scroll zooms too. **+** and **−** zoom around the middle of the view. - Zooming in on something other than yourself moves the view, like dragging it. Walk or press **Back to you** to come back. - **Click someone** to open their card: name, status, what they're working on and, for agents, who they report to. From there you can walk over, ring them, [follow them or ask them to come with you](https://yomenie.us/docs/floor/following). Esc closes it. - **Hover someone for their name** wherever it's hidden: a person in a private room with two or more people (the room shows one label for the group), a face in the dock or a meeting room's join card, and a name cut short on a small video tile. On a touch screen, tap them to open their card. ## Map view Zoom all the way out for **Map view**. It shows the building's outline with each room as a coloured block and a label on top, and everyone as a round face with a presence dot. - Hover a room's label for its full name, and whether it's locked, full, or a video meeting. - Only your own name shows. Hover a face for that person's name, or click it to open their card. - A small door icon marks rooms that can be locked; a lock and a headcount show while one is locked. - Click a room's label to open its card. Owners and admins change the room's settings there ([meeting rooms](https://yomenie.us/docs/floor/meeting-rooms#room-settings)). - Double-click anywhere to walk there. ## Sounds Footsteps are synthesised in your browser and change with the floor: wood, tile or carpet. Other people's steps are quiet, fade with distance, and never carry through a private room's walls. **Shift+M** or the speaker button in the dock mutes footsteps and voices. ## On any page You stay on the floor while you use chat, the board or any other section, so a conversation or call keeps going. Your character stays where it is until you come back to the floor page. The [dock](#the-dock) shows under the page whenever there's something to control. ## The dock The bar at the bottom centre holds your controls, left to right: - **Your face** with your presence dot: opens your status menu. - **Who you're with**: their faces and names ("Shalomi and 2 others"), with an amber ring while someone speaks. In a meeting room, the room's name and headcount instead. It's a button: its menu has **Come with me**, to ask them to [follow you](https://yomenie.us/docs/floor/following), and **Follow *name*** for each of them. - **Lock**, when you're in a conversation or a lockable room. - **Ring**, the amber phone, while someone near you can't hear you: their mic is off, or they're close by but not in your conversation. It goes away once everyone in your conversation has their mic on. See [Rings](https://yomenie.us/docs/floor/rings). - **Mic**, with a small arrow for audio and video settings. - **Speaker**: sound on or off. - **Camera**, where video works. - **Leave**, the red hang-up, to step out of a conversation where you stand. - **Go to my desk**, the desk icon at the end, when you've [claimed a desk](https://yomenie.us/docs/floor/desks) and aren't sitting at it. It walks you there and sits you down. Every button has a tooltip; the ones with a key show it. Hints show as small pills above it: a knock at the door, a ring, "Following Bud · Stop", a note that your mic turned itself off. --- # Conversations and bubbles URL: https://yomenie.us/docs/floor/conversations Section: The floor · Updated 2026-11-17 > Stand within two tiles of someone and you're in a conversation. Lock it, let people in when they knock, or leave where you stand. *Picture: Two people in the lounge inside an amber conversation bubble.* Conversations on Yomenie work the way they do in a room: you talk to the people near you. ## Who's in a conversation - **Within two tiles.** Stand within two tiles of someone and you're in a conversation with them. Chains count: if you're near Ana and Ana is near Ben, all three of you are in one conversation. - **Once you stop.** Walking past people doesn't pull you into their conversation. You join when you stop beside them, about half a second later. If you're already in a conversation, moving around inside it keeps you in, and walking out of range leaves it at once. - **A private room is one conversation.** Everyone inside a meeting room, the Standup, the Huddle or a focus booth is in that room's conversation, wherever they stand in it. Its walls keep everyone else out. - **Walk away and it ends.** Step out of range and you're out. A soft amber bubble on the floor shows each open-space conversation, and the faces of the people you're with appear in the dock. You hear, and are heard by, the connected people in your conversation, and nobody else ([voice and video](https://yomenie.us/docs/voice-video/mic-and-camera)). Who counts: people who are online and agents that are running. Agents are in the conversation on the floor, but they never receive audio or video. ## Locking a conversation Anyone in an open-space conversation can press **Lock** in the dock. The bubble turns slate with a "Locked" tag, and newcomers who walk up aren't added. - Someone outside can press **Ask to join**. Everyone inside sees it, and anyone can press **Let in**. - The lock lasts as long as the conversation. Locks and knocks aren't stored or logged anywhere. ## Raise your hand In a conversation with someone else, like the Standup, press the **hand** in the dock (or H on the floor page) to say you'd like to speak without talking over anyone. - Everyone else in the conversation hears a soft chime, unless their sound is off or they're focusing. - Your tile gets an amber ring and a hand, with your place in the queue when several hands are up, camera on or off, and moves to the front, right after their own. Your face in their dock, your row in the participants pane and in the people panel say so too. - It goes down when you press it again, when you turn your mic on to speak, or when you leave the conversation. Nobody else can raise or lower your hand. Hands aren't stored or logged anywhere. ## Leave conversation Press **Leave** in the dock to step out of a conversation where you stand, without walking off. You stop hearing and being heard at once, and any live mic or camera turns off. Your next step brings you back into grouping as normal. ## Meeting rooms Rooms with doors work differently: the door itself can be locked from inside, and a locked door is a wall. See [meeting rooms](https://yomenie.us/docs/floor/meeting-rooms). --- # Meeting rooms: doors, locks and capacity URL: https://yomenie.us/docs/floor/meeting-rooms Section: The floor · Updated 2026-11-17 > Lock a meeting room from inside; people outside knock. Admins rename rooms, set video, capacity and agent rules, and repurpose rooms, like a restroom. *Picture: Meeting room 1 with its door locked and three people at the table.* The office has private rooms along the meeting street: Meeting rooms 1 to 3, the Huddle and two focus booths, plus the Standup room in the west wing. Everyone inside a room shares one conversation, and the walls keep everyone else out. ## The room's label Once two or more people are in a private room, their name tags give way to one label at the top of the room: the room's icon (a lock while it's locked) and how many are inside, like "Standup · 10". In a video meeting, the participants pane lists everyone. If you're in the room's conversation, the label says who is speaking ("Kas speaking", or "Kas and Avindi" when two talk at once) and their own name tag shows above their head while they talk, so you can see where they sit. It stays for a second after they stop. People outside the room see the count only, never who is speaking. ## Locking the door Meeting rooms 1 to 3 have real doors. Anyone inside can lock the door: - with the **lock panel** on the wall just inside, beside the door (hover it for "Lock the door", click once), or - with **Lock the door** in the dock. While it's locked, the door is a wall for everyone outside. The server enforces it with the same rule your browser uses, so nobody walks in by accident or on purpose. There's **no admin override**, owners included. People inside can always walk out; coming back in means knocking. The lock clears itself when the room empties. Locks aren't stored or logged. ## Knocking At a locked door, the dock shows "Meeting room 1 is locked · Knock". You can also click the door itself. People inside see "*Name* is knocking · Let in", and anyone inside can let you in. That gives you a pass for 60 seconds or until you enter. If you double-click inside a locked room from outside, you walk to the nearest free tile by its door. ## Capacity and full rooms Closed rooms (rooms with walls and a few doorways) can have a capacity. When a room is full, its entrance is closed to anyone outside, and the dock says "*Room* is full". Lowering a capacity never moves anyone out. Open areas such as the desk areas, the lounge and the meeting-street corridor can't have one. ## Room settings Owners and admins change a room from **Map view**: zoom all the way out, then click the room's label. The room card shows: | Setting | What it does | | --- | --- | | Name | What everyone sees, up to 40 characters | | Video | Off, Available or Video meeting ([video meetings](https://yomenie.us/docs/voice-video/video-meetings)) | | Lockable | Only for rooms with a door. Turned off, the lock and any knocks clear at once and the door stays open | | Capacity | Empty means no limit. Closed rooms only | | Agents | **Can walk in**, or **Must be let in** by someone inside | | Used as | A different purpose for the room (below). Only rooms with a preset that fits | **Save** appears once something changed, and **Reset to default** once the room differs from the original. Every change takes effect for everyone at once and is written to the [audit log](https://yomenie.us/docs/connections/audit-log). Members see a one-line summary instead, like "Video meeting · Lockable · 6 seats" or "Restroom, was a focus booth · No video". ## Giving a room another purpose A workspace can use a room for something else. The room's walls, door and place stay the same; its furniture and props change to a set that fits inside it, and its seats come with that set. Each workspace chooses for itself, so one can have a restroom where another keeps its focus booth. | Purpose | What's in it | Rooms | | --- | --- | --- | | Restroom | Toilet stalls with doors, sinks with a mirror, a plant. No seats, no camera, and it can't be locked: the floor lock is for meetings | Focus booths A and B, the Huddle | | Phone booths | A row of phone nooks between felt panels, each with a chair | Focus booths A and B, the Huddle | | Quiet room | Armchairs, beanbags, a lamp and plants. No camera unless you turn it on | Focus booths, the Huddle, Meeting rooms 1 to 3 | | Storage | Shelving, cabinets and boxes. No seats | Focus booths, the Huddle, Meeting rooms 1 to 3 | | Kitchenette | A counter with a coffee machine, a fridge, a water cooler and a small table | Focus booths A and B, the Huddle | A room given a purpose takes its name ("Restroom") unless you renamed it, and its video default. A meeting room used as a quiet room or for storage keeps its door and lock. Anyone standing where new furniture goes moves to the nearest free spot. Rooms with claimed desks can't be repurposed until their desks are released. Choose **Used as** on the room card, or ask your AI tool through MCP: "Turn Focus booth B into a restroom" calls `update_room` with `purpose: "restroom"`. To undo it, pick the room's original purpose, or ask for "the original floor": `reset_floor` puts every room's furniture back in one go (and, with `all`, every room's settings too). ## Changing the layout Walls, doors and rooms are the same for every workspace today; only what's inside a room can change (above). A floor editor isn't built yet. (not built yet: https://yomenie.us/docs/roadmap#floor-editor) --- # Desks URL: https://yomenie.us/docs/floor/desks Section: The floor · Updated 2026-11-17 > Claim one desk in a desk area and you arrive there each time you open Yomenie. Come back within 15 minutes and you return to where you stood. The hall has two desk areas. Each person can claim one desk. ## Claiming a desk Double-click a free desk: you walk to its chair, sit down and claim it. Or walk there yourself; when you stand at a free desk, the floor shows **Claim this desk**. Double-click your own desk to walk back and sit. Claiming a new desk releases your old one. Hover any desk to see whose it is, or "Unclaimed desk". To give your desk back, sit at it and click your desk, its chair or yourself. **Release this desk** appears beside you; click elsewhere or press Esc to close it. While you just sit there, nothing shows. An agent's desk is set on the agent, and nobody can claim a desk someone else holds. Desk claims are written to the [audit log](https://yomenie.us/docs/connections/audit-log). ## Go to my desk Once you have a desk, the dock ends with a desk icon whenever you're on the floor page and not sitting at it. Press it (the tooltip says "Go to my desk · Desk 4") to walk there the usual way and sit down. If you were following someone, that stops. You can also click your desk or its chair from anywhere on the floor: **Return to desk** appears above it, and clicking that walks you back and sits you down. Click the desk again, click elsewhere, press Esc or walk off to close it. ## Where you arrive - **Normally, at your desk**, sitting down. Without a desk, you arrive at the entrance. - **Back within 15 minutes?** If you reload or your connection drops, you return to where you stood (seated again if you were sitting), so a reload doesn't send you back to your desk. If that spot is no longer open to you, for example a room was locked meanwhile, you land just outside its door. Where you stood is kept in memory only, for 15 minutes, and used up when you return. It's never stored or logged. --- # Status and status text URL: https://yomenie.us/docs/floor/status Section: The floor · Updated 2026-11-14 > Set yourself to available, focus, in a meeting or away, add a short note and choose when it clears. Online only means your tab is open right now. Your status says what you're up to. Only you set it; nothing changes it for you except the "Clear after" you chose. ## Setting your status Open the status menu from your face in the dock, your own row in the people panel, or **Set status** on your own floor card. Then: 1. Pick a status: **Available**, **Focus**, **In a meeting** or **Away**. The arrow keys move between them and save. 2. Type a note in "What's your status?" (up to 80 characters, one line), or pick a preset: In a meeting, Lunch, Heads down, Back in 15. "In a meeting" also sets your status to In a meeting. 3. Choose **Clear after**: Don't clear, 30 minutes, 1 hour, or Today. Everyone sees the change at once: on your floor card, in the people panel and in your presence dot. When the time is up, your status goes back to Available and the note clears. ## What each status does Your status decides what happens when someone [rings](https://yomenie.us/docs/floor/rings) you: | Status | Dot | Rings | | --- | --- | --- | | Available | Green | Chime | | Focus | Orange | Arrive quietly, without a sound | | In a meeting | Red | Aren't delivered; the caller is offered a message instead | | Away | Grey | Aren't delivered | ## Online is separate "Online" only means you have Yomenie open right now. The people panel lists people who are connected first and shows everyone else with a grey offline dot. Connecting or disconnecting never changes your chosen status. Your status and note aren't written to the audit log: they're personal, and they change often. A status that follows your calendar isn't built yet. (not built yet: https://yomenie.us/docs/roadmap#calendar-sync) --- # Rings URL: https://yomenie.us/docs/floor/rings Section: The floor · Updated 2026-11-16 > Ring a teammate to talk, even when Yomenie is in a background tab. When they pick up, both mics turn on. Their status decides how it arrives. A ring is a tap on the shoulder: "can we talk?" It reaches someone even when Yomenie is in a background tab, and when they pick up, both of your mics turn on, so you can talk straight away. ## Ringing someone - Click someone on the floor and press **Ring *name*** on their card, or - press **Ring**, the amber phone in the dock. It shows while someone near you can't hear you: someone in your conversation with their mic off, or someone within talk range who isn't in your conversation. With several, it opens a menu. Once everyone in your conversation has their mic on, it goes away, or - press R on the floor page. It does what the dock's Ring button does: it rings the one person near you who can't hear you, or opens the Ring menu with the first person picked when there are several (arrows and Enter choose). With someone's card open, it rings them. With nobody to ring it does nothing. You can put Ring on another key in **Settings → Keyboard shortcuts** ([keyboard shortcuts](https://yomenie.us/docs/floor/keyboard-shortcuts)). While your ring rings, the phone's waves pulse gently (not if you've asked your system for reduced motion), and pressing it again (or R) cancels the ring. You can ring people who are online. Agents never ring or get rung. While it rings, your pill says "Ringing *name*… Your mic goes live when they answer." with **Cancel**. ## What you hear - **While it rings**, a soft ringback, like a phone line: two short tones, then a pause, repeating. It stops when they answer, decline, don't answer, aren't available, when you cancel, or when you leave. It plays for someone who is focusing too: only you hear it. - **When they pick up** (**Accept** or **On my way**), a short, warm rising chime. - **"In 5 minutes", "Can we chat instead?" or a decline** get one soft low note. No answer and a ring that couldn't be delivered make no sound. These follow your speaker mute (**Shift+M**): muted, you hear none of them, and muting stops the ringback. They're made in your browser; nothing is recorded or sent. ## Your mic while it rings Pressing **Ring** (or R) opens your mic in that click or key press, but nothing is sent while it rings: the dock's mic button shows it's **ready** (a light amber fill with a dashed outline). Your browser may show its mic light meanwhile. - When they accept and you're in the same conversation, it goes live: "*Name* answered. Your mics are on." If they accepted muted, it says "*Name* answered and is listening." - If they accept from across the office, it stays ready until you're together, and turns itself off after 2 minutes if you never meet. - **Cancel**, a decline, no answer, "In 5 minutes" or "Can we chat instead?" turn it off again ("Your mic is off again"). - Clicking the ready mic button turns it off too. A mic that was already on stays as it is. ## What they see Their [status](https://yomenie.us/docs/floor/status) decides: - **Available**: a chime, a card above their dock, the tab title flashing "*Your name* is ringing you", and a system notification if the tab is in the background and they've allowed notifications. - **Focus**: the same, without a sound. You see "*Name* is focusing, they'll see it". - **In a meeting** or **Away**: it isn't delivered. You're offered a message instead. They can answer with: - **Accept · mic on**: turns their mic on in that click and picks up ("Mic on: you accepted *your name*'s ring"). - **Accept muted**: picks up without the mic. Their mic button keeps a quiet amber outline until they turn it on. - **On my way**, **In 5 minutes** or **Can we chat instead?** (which opens a direct message). These never touch the mic. - **Decline**. If they accept from out of talking range they see "You accepted. *Your name* is in the kitchen" with **Walk to *your name***. Their mic is on, but nobody hears it until you're in the same conversation. **Accept** on the system notification or in the phone app counts as their click: the mic turns on in their newest Yomenie tab if the browser already allows it, otherwise the dock asks them to **Turn on mic** when you meet. After that the usual rules apply: the mic turns itself off when the conversation ends ([conversations](https://yomenie.us/docs/floor/conversations)). ## Limits - A ring nobody answers in 30 seconds is marked missed. You see "No answer · We'll let *name* know" with **Leave a message**, and it goes under their bell as "*Your name* rang you at 14:05" with **Ring back** and **Message**, pushed to their devices like a direct message (quietly in Focus, not at all in a meeting or away). A ring they decline while focusing goes there too. - You can ring the same person once every 30 seconds, and have one ring going at a time. - If either of you leaves, the ring ends. ## Notifications and sound - The chime follows your speaker mute (**Shift+M**), like the ringback and answer sounds you hear when you ring someone. - Yomenie only asks for notification permission when you click: **Notifications on this device** in audio settings, or "Notify me on this device" once after you miss a ring. With it on, a ring reaches the device even when Yomenie is in the background, with **Accept** and **On my way** on the notification ([notifications](https://yomenie.us/docs/account/notifications)). - Your own device decides between a chime, a flashing title and a notification. Whether you're looking at the tab is never sent to the server. Answered and cancelled rings aren't stored or logged. A missed ring is kept under the bell for 30 days, like any notification, and never in the audit log. ## When someone walks up to you Walking over to someone works too. When someone clearly came to see you, Yomenie tells you "*Name* is at your desk". It never fires for people walking past, bumping into you or sitting at the next desk. It counts only when all of these hold: - They **arrived**: they weren't within talking range of you, and now are. Your desk neighbours, the Standup circle and people you're already with never count. - They **stopped**: they stayed beside you for **6 seconds** without taking another step. - They **meant it**: they walked to you (double-clicking your desk, **Walk over** on your card, **Walk to** after a ring), they face you, or they're at your claimed desk. - You aren't already talking (with a mic on), and they didn't sit down. - You're both people. Agents never visit or get visited. - Your [status](https://yomenie.us/docs/floor/status) allows it: Available gets it, Focus gets it without sound, Meeting and Away get nothing. - At most once per person every 10 minutes, and 6 an hour in all. What you see is decided on your device. On the floor page, in front of you, nothing: you can see them. With the tab in the background, a notification (if you've allowed them). On another page, a pill above the dock with **Go to floor** and **Message**. If you don't come over within a minute (take a step, turn your mic on or ring them), it goes under your bell as "*Name* stopped by at 14:05", with **Ring back** and **Message**, and to the Yomenie app on your phone. The person who came over is never told whether you saw it. If you haven't come after about 20 seconds, their pill offers **Ring *your name***. Turn it off with **When someone walks up to me** in **Settings → Notifications**. Arrivals and cool-downs are kept in memory only, never stored. --- # Following someone URL: https://yomenie.us/docs/floor/following Section: The floor · Updated 2026-11-16 > Follow a teammate or an agent around the Yomenie floor, or ask people to come with you. You walk behind them through doors and into meeting rooms. Taking someone somewhere used to mean they kept double-clicking after you. Now one of you leads and the other follows: the follower's character walks a tile or two behind the leader, through doors, into rooms and across the floor. ## Following someone Click someone on the floor and press **Follow** on their card, or, in a conversation, press who you're with in the dock and choose **Follow *name***. You can follow people and agents (handy for watching what an agent does). Agents never follow anyone. While you follow, **Following *name* · Stop** shows above your dock. Your view stays on your own character, as always. ## Come with me To take people somewhere, ask them to follow you: - press **Come with me** on someone's card, or - in a conversation, press the faces and names in the dock (who you're with) and choose **Come with me**. With several people, it asks everyone in the conversation. They see **"*Your name* asks you to follow · Follow · Not now"** above their dock. It goes away after 30 seconds, and it never shows during a ring. Pressing Follow starts following you. While people follow you, **"Kofi is following you"** (or "Kofi and 2 others are following") shows above your dock with **Stop**, and your own card lists who follows you. ## Doors and meeting rooms The follower's browser plans the walk and sends the same single steps you'd make by hand, so the server checks every one: walls, closed doors and full rooms hold as usual. Several followers line up behind the leader, each on their own tile. When the leader walks into a locked meeting room, the people following them are let in, the same as a knock someone answered. It's only for the people actually following, and only when the leader just walked in: following someone who's been in a locked room for a while means knocking, like anyone. If a follower can't get in (the room is full, say), they stop by the door with a note such as "Meeting room 1 is full · Stopped following". ## When it stops Following stops, with a note saying why, when: - the follower presses a walk key, double-clicks somewhere else, presses **Esc** or **Stop**; - the leader presses **Stop** (stop leading) or **Leave**; - either of them disconnects, or is away from the floor page for more than a few seconds; - the leader sits down and the follower has caught up; - the follower can't get into the room the leader went into. ## Privacy Following never turns on a mic or camera. Walking into a meeting room as a follower is the same as walking in yourself: the usual join card shows, and your mic and camera stay as they were until you press something. Who follows whom isn't stored or logged anywhere; it lives in the server's memory while it lasts, like a ring. --- # Keyboard shortcuts URL: https://yomenie.us/docs/floor/keyboard-shortcuts Section: The floor · Updated 2026-11-17 > Every Yomenie keyboard shortcut: walking, mic, camera, sound, Ring, raise hand and zoom. Change those keys, or walk with the arrows only. Press ? anywhere outside a text field, or **?** → **Keyboard shortcuts** at the bottom of the left rail, to see every shortcut. ⌘ is for a Mac; on Windows and Linux it's Ctrl. ## The defaults | Shortcut | Does | Where | | --- | --- | --- | | W A S D or arrows | Walk | Floor page | | Double-click | Walk to a spot | Floor page | | M | Mic on or off | Floor page | | ⌘+D | Mic on or off | Any page | | C | Camera on or off (at a video meeting's join card: mic and camera) | Floor page, where video works | | ⌘+E | Camera on or off | Any page, where video works | | Shift+M | Sound on or off: footsteps and voices | Floor page | | R | [Ring](https://yomenie.us/docs/floor/rings): the person near you who can't hear you, or the person whose card is open (with several near you, opens the Ring menu); again to cancel | Floor page | | H | [Raise or lower your hand](https://yomenie.us/docs/floor/conversations#raise-your-hand) | Floor page, in a conversation | | + − | Zoom in or out | Floor page | | Esc | Close a card or menu | Anywhere | | ⌘+K | Search people, agents and channels | Any page | | ? | This list | Any page | Keys go by their position on the keyboard, not the letter printed on it, so they sit in the same place on AZERTY, Dvorak or Cyrillic layouts. Keys you type into a text field are never shortcuts, and ⌘ or Ctrl combinations never walk. ## Changing them Open **Settings → Keyboard shortcuts** (the gear at the bottom of the left rail, or the **Settings** link at the bottom of the shortcuts list). It shows the same list, and there you can: - **Change** the mic, camera, speaker, Ring or raise-hand key, then press the new key: one key or Shift plus a key (letters, digits or punctuation). Esc cancels. - Choose how you walk: **WASD and arrows**, or **Arrows only**, which frees W, A, S and D for other shortcuts. - **Reset to defaults** puts everything back (it shows once something differs). A key that's already taken is refused with the reason under its row, like "S is used to walk down". Esc, Tab, Enter, Space, ?, + and −, the arrows and anything with ⌘, Ctrl or Alt are reserved, and ⌘D and ⌘E stay fixed. Your keys are saved in this browser only, and every tooltip and hint shows your own keys right away. ## The first-time tip The first time you're on the floor, a small pill above the dock shows your mic, camera and help keys. It fades after 15 seconds, or close it with ×, and it doesn't come back. --- # The office scoreboard URL: https://yomenie.us/docs/floor/scoreboard Section: The floor · Updated 2026-11-15 > Screens on the office walls with the numbers your team cares about, pushed from your tools or counted from a board, and a small celebration when they move. Screens hang on the office walls. Each shows up to three numbers a team cares about: releases today, tickets done this week, tickets in review. When one moves, the office notices. Every workspace starts with one screen, **Hall**, above the Support desks. Owners and admins can put more on fixed spots around the floor: | Spot | Where | | --- | --- | | Hall | Above the Support desks | | Platform | Above the Platform desks, on the Standup wing's wall | | Standup | On Standup's north wall, in place of its screen | | Meeting rooms 1, 2 and 3 | On each room's north wall, in place of its screen | | Kitchen | On the kitchen's north wall | One screen per spot. A spot without a scoreboard shows an ordinary wall screen with charts, like the others around the office. Yomenie is a scoreboard, not an analytics tool. Your tools push finished numbers; Yomenie stores them, shows them and celebrates when they go up. The only counting it does itself is of your own tickets. ## Read it - **On the floor:** each column is a label, the number and an arrow (up or down since yesterday or last week). Numbers are drawn in pixels, so they stay sharp at every zoom. A screen with nothing on it shows its name. Hover a screen to see its name. - **Click a screen** for its card: the screen's metrics, then every other metric you're allowed to see, each with its value, the change, the last 14 days, progress towards its target, where it comes from, when it was last updated and which screens show it ("On Hall, Platform", or "Not on a screen"). A number that hasn't been updated for a day (or its own limit) is shown as stale. Owners and admins see **Edit in Settings** and a link to fix a metric's screens; an empty screen says "Nothing on this screen yet". ## Who sees what **Screens are public.** Everyone on the floor sees every screen, and the same numbers on it, so a screen only shows metrics everyone in the workspace can see. A screen can belong to a team; that says where it belongs (and which boards Settings suggests for counting), and hides nothing. Each metric is visible to everyone in the workspace, to owners and admins only (it carries a lock chip), or to one team. Metrics for owners and admins or for one team never go on a screen: they're in Settings and in the screen cards' lists, for the people allowed. Owners and admins see every metric, since they set them up. Agents never see metrics. The server sends each person only the metrics they may see. A metric that's on a screen stays visible to everyone: to make it more private, take it off its screens first. ## Celebrations A metric can celebrate when it goes up, when it first reaches its target in the current period, or when it beats its record. Your browser decides how to show it, from things that never leave your device: - **On the floor page:** every screen showing the metric glows amber and shows what happened, confetti falls in front of it, and a short gong plays. If none of those screens is near your view, you just get the pill. - **Your status:** focusing silences the gong; in a meeting or away, there's no gong and no confetti. - **Your sound:** the speaker button (`Shift+M`) mutes the gong too. - **Inside a private meeting room,** or with reduced motion turned on in your system: no confetti. - **On other pages:** only a small pill above the dock, like "v0.1.33 · Releases today: 4 · Hall", naming the screens it played on. At most one celebration per metric every 10 seconds. Celebrations aren't stored. A metric can also post a short message in a channel as **Scoreboard** ("Releases today: 4 (v0.1.31)"). ## Set it up Owners and admins manage screens and metrics in **Settings → Scoreboard**. Everyone else can read the page. ### Screens The **Screens** section lists every screen with its spot, its team and its metrics. **New screen** asks for a name, a free spot (by place, like "Hall, above the Support desks"), a team or the whole workspace, and up to three metrics in order (move them up and down). **Count from board** adds a counted metric for one board, the screen's team's boards first. Editing and deleting ask you to confirm. Changes show on the floor at once and are in the audit log. ### Metrics 1. Choose **Add a metric**: a name, a key (what tools push by, like `releases_today`), a format (number, currency with a three-letter code, or percent) and a source: - **Push URL:** your tools send the number. - **Board:** counted from your tickets: done today, done this week, or in review now, on every board or on one (**Count from board**). - **By hand:** you type the value in Settings. 2. Pick when it **resets** (never, daily at midnight, weekly on Monday) and its **timezone**. A count that resets starts again from 0 after the boundary; yesterday's number stays in its history. 3. Add a **target** if you like ("10 per week": for a daily count, the week's days are added up), who can see it, which screens **show** it and what to celebrate. A new metric visible to everyone starts ticked for the Hall screen when it has room; leaving every screen unticked says so ("Add metric, not on a screen"). A screen has room for about ten letters per column: give it a **short label for the screen** ("IN REVIEW"), or it shows as many whole words of the name as fit. Your AI tool can do all of this too, through [MCP](https://yomenie.us/docs/mcp/tools#scoreboards), if you're an owner or admin and allowed "Manage workspace settings". The push URL stays here. ## Push numbers from your tools The workspace has one push URL. Make it in **Settings → Scoreboard → Push URL** (confirm it's you with your passkey or an email link). It's shown **once**: copy it into your CI's secrets. ```sh curl -fsS -X POST "$YOMENIE_METRICS_URL" \ -H 'content-type: application/json' \ -d '{"key":"releases_today","increment":1,"note":"v0.1.31"}' ``` - Send `increment` to add to the number, or `value` to set it. - `note` (or `label`), up to 120 characters, shows with the celebration. - An unknown key is a `404`: pushes never create metrics. Board and by-hand metrics can't be pushed (`409`). - Up to 60 pushes a minute per URL (`429` with `Retry-After` beyond that). - Treat the URL like a password. **Regenerate** it if it leaks (the old one stops at once) or **Revoke** it. Changes to metrics and to the URL are in the audit log; pushed values aren't. ### Releases from a deploy job Add the push as the last step of your deploy, after the health check, so it never fails a deploy: ```sh if [ -n "$YOMENIE_METRICS_URL" ]; then curl -fsS -X POST "$YOMENIE_METRICS_URL" -H 'content-type: application/json' \ -d "{\"key\":\"releases_today\",\"increment\":1,\"note\":\"$CI_COMMIT_TAG\"}" || echo "scoreboard push skipped" fi ``` Store `YOMENIE_METRICS_URL` as a masked, protected CI/CD variable. --- # Agent helpers on the floor URL: https://yomenie.us/docs/floor/agent-helpers Section: The floor · Updated 2026-11-17 > Your AI session walks beside you on the Yomenie floor and its sub-agents work at your desk. When one needs you, you get a notification. When you work through Claude Code, Codex, Cursor or another tool [connected over MCP](https://yomenie.us/docs/mcp), your team can see it: the session floats at your shoulder as a small violet character, and the sub-agents it starts work at your desk. ## What you see - **The session** (the lead) is a 12-pixel character beside you, on the side away from where you face. It appears as soon as your tool does something in Yomenie (just connecting doesn't count), and two windows of the same tool are two sessions. - **Sub-agents work at your desk.** If you've [claimed a desk](https://yomenie.us/docs/floor/desks), they're the smaller 8-pixel characters around it: up to six, and a small "+2" stack on the desk for the rest. They pop in with a spark and leave with a sparkle and a puff when they're done. With no desk, they walk your own path behind you instead. - While you're away from the floor, your helpers keep working at your desk, the session too. - **At rest, each character has its own little loop**: the owlet blinks, the tomte hammers, the firefly pulses, Anansi weaves, the kodama rattles, the lantern spirit flickers. Busy helpers move a little faster; one waiting for you dozes, with a "z" drifting up. - **A small icon pops above a helper for a moment** when it starts or changes task, chosen from its role: a flask for tests, a magnifier for review, a hammer for building, a map for exploring, a quill for docs. A role it doesn't recognise gets no icon. - **Hover** a helper to see its name. **Click** it for its card: name and role, whose session it is and for how long, its task, its ticket (click to open it), a line about its character ("Owlet: watchful, never misses a failing test"), what it's waiting for, if anything, and the others at the same desk. - The people panel lists **Working now · 2 sessions, 5 agents** under Agents: each session with its sprite, app and ticket, and its sub-agents indented under it with role, task and ticket. Click a session to find it on the floor, or a sub-agent to open its ticket. The arrow beside a session folds it to one row (remembered in this browser). The person's own row says **"Lark and 3 helpers"**. - On the board, a ticket a helper works on says **"Wren is on it · Bud's Claude Code"**. - In Map view helpers aren't drawn; a small violet number on each face says how many there are. Helpers never block anyone and you can't bump into them. Teammate agents (the ones with a manager and a desk, like Iris or Juno) stay full characters and never have helpers. With reduced motion turned on in your system, helpers hold still: no bobbing, no loops, no icons. ## When a helper needs you When your tool asks you a question and stops to wait for your answer, it marks the helper as waiting (see [the MCP tools](https://yomenie.us/docs/mcp/tools#agent-helpers)). You get a notification, **"Pip is waiting for you"**, with the question and the ticket, under the bell and pushed to your devices like a direct message. On the floor the helper dozes, and its card says "Waiting for Lahiru: which API version?". There's no question mark over anyone's head. Answer in your AI tool. The notification is marked read by itself as soon as the helper carries on, or when it ends. A newer question from the same helper replaces the older one. Turn these off in Settings → Notifications → **When my agents need me** (they still show under the bell). ## How helpers start and end Your session appears with your tool's first call. Every helper, session or sub-agent, gets 15 minutes when it starts, and each call that touches it keeps it at least 10 minutes after that call (30 minutes while it waits for you). A call your session makes itself keeps the session and all its sub-agents; a call a sub-agent makes keeps it and the session. So a sub-agent that codes or runs tests for a long stretch without calling Yomenie stays on the floor as long as your session is busy. A helper leaves at once when it ends, otherwise when its time runs out. When Yomenie updates or restarts, helpers still within their time come back as they were, with the same names, tasks and tickets, and your tool carries on with the same ids. No two helpers shown in a workspace share a name. Sub-agents come from the tool itself: when it splits work, it registers each sub-agent with a role, a short task and the ticket if there is one, and ends it when it returns. With Claude Code, the [Yomenie plugin](https://yomenie.us/docs/mcp/claude-code-plugin) makes sure every sub-agent is registered and ended, and that a question it waits on reaches you. Everyone in the workspace sees a helper's name, role, task and what it's waiting for. Tasks are cut to 80 characters and questions to 120, on one line, and anything that looks like a token or an email is removed. Nothing about helpers is added to the audit log. ## Past sessions When a session or sub-agent leaves the floor, it stays in the history for 90 days: which app ran it, when and for how long, its task and ticket, each sub-agent with its role and how it ended (done, or faded when nothing touched it for a while; sessions from before helpers came back after a restart may say stopped when Yomenie restarted), and what each one did: the tools it called and what they acted on, like **Claim ticket · YOM-12** or **Read messages · #design ×3**. Never the text of a message, a ticket's description, a comment or anything else your tool sent. A person's activity page shows their past sessions, and your AI tool can read them with `list_agent_sessions` (see [the MCP tools](https://yomenie.us/docs/mcp/tools#agent-helpers)). Everyone in the workspace can see them, except the names of private channels they aren't in and other people's direct messages. The outcome a tool writes when a sub-agent ends is shown only to you. ## The characters Every helper gets its own character, picked from its id so everyone sees the same one, and a short name from one neutral list (Wren, Pip, Nib, Moss, Lumi, Hoot…). Names are never matched to a character's culture, and each character's line is about how it works, never about a people or a place. The set mixes folklore, fantasy and plain creatures: Heinzelmännchen, Tomte, Dokkaebi, lantern spirits and Kodama, Alebrije, Domovoi, Anansi the spider, halflings, gnomes, imps, apprentices, familiars, pebble golems, fireflies, owlets, wisps, glow lanterns, violet bees, jellies, paper cranes, sprouts and bolts. Every one has a violet body, never a human skin tone, and none is drawn as a costume or a stereotype. ## Turn them off Settings → Profile → **Show my agents on the floor** (on by default). Off hides all your sessions and sub-agents from everyone, on the floor and in your past sessions; you still see your own history, and your tool keeps working as before. --- # Mic and camera: off by default, off by themselves URL: https://yomenie.us/docs/voice-video/mic-and-camera Section: Voice and video · Updated 2026-11-15 > In Yomenie your mic and camera start off, turn on only with your own click or key, and turn themselves off when you leave the room or the conversation. You hear and see the other people in your [conversation](https://yomenie.us/docs/floor/conversations), and they hear and see you. Nobody else does. The server enforces that, not the browser: audio and video only flow between connected people in the same conversation, and walls and locks hold on the server. ## Off by default - Your **mic starts off** on every visit, and so does your **camera**. Neither is ever restored after a reload. - Only you turn them on, with your own click or key: **M** (or **⌘D** / **Ctrl+D** on any page) for the mic, **C** (or **⌘E** / **Ctrl+E**) for the camera. - Nothing turns them on for you: not joining a room, not a video meeting, not a ring, not an agent, not another person. When you meet someone who could hear you while your mic is off, the mic button gets an amber outline and "Turn on mic". It's a nudge, not a switch, and it doesn't come back in that conversation once you dismiss it. ## Off by themselves Capture ends when its reason ends. Yomenie turns your mic and camera off (and a [screen share](https://yomenie.us/docs/voice-video/video-meetings#screen-sharing), by the same rules), and tells you it did, when: - **You leave the room you turned them on in.** In a private room or a video meeting room, walking out turns them off, even if you were alone there. "Mic and camera turned off when you left Standup." - **Your conversation ends in open space** because someone walked away, you walked off, or you pressed Leave. "Mic turned off when you left the conversation." - **You walk into a room with video off.** The camera turns off. "Camera turned off: Focus booth A has no video." - **You press Leave** in the dock, anywhere. - **You close the tab.** You leave the floor at once and the camera stops. Some things don't count as an ending: - People coming and going inside your room. - Walking straight from one conversation into another. - The other person's connection dropping. Your mic stays as it is until they're back or you take a step, and nobody can hear you meanwhile. - A mic you turned on while alone in open space stays on. Stopping always ends the track, so the device is released and its light goes off. ## Always visible If you're live, you can see it: the mic and camera buttons, a speaking ring, your face in the dock showing your camera, and your self-view, which you can shrink but never hide while your camera is on. Only one Yomenie tab is in the call. Opening the board, chat or settings in another tab leaves your call where it is. Opening the floor in another tab or window moves your call there: the older tab turns your mic, camera and screen share off, leaves the call, and its floor page shows "You're on the floor in another tab" with **Use here**. Nothing comes back on by itself in either tab. [More in Privacy](https://yomenie.us/docs/privacy#one-live-tab). ## Listening never needs a mic You hear your conversation whether or not your mic is on. Browsers block sound until you click or press a key on the page; if that happens, the dock shows "Your browser paused sound · Enable sound". ## Agents and other things AI agents never receive audio, video or screen shares. They can be in a conversation on the floor, but not in the call. Agents joining calls isn't built. (not built yet: https://yomenie.us/docs/roadmap#agents-in-calls) To show your screen to your conversation, see [screen sharing](https://yomenie.us/docs/voice-video/video-meetings#screen-sharing). Nothing is recorded, and no frames or thumbnails are stored anywhere. More in [privacy](https://yomenie.us/docs/privacy). --- # Video meetings, the video strip and screen sharing URL: https://yomenie.us/docs/voice-video/video-meetings Section: Voice and video · Updated 2026-11-15 > Room video modes, the join card, a tile for everyone in the grid or strip, the participants pane, and screen sharing, one person at a time. Video works on top of voice: the people in your conversation can turn their cameras on, and everyone in the call shows as a tile, in a grid or a strip above the dock. ## Room video modes Every room has a video mode, which owners and admins can change in the [room settings](https://yomenie.us/docs/floor/meeting-rooms#room-settings): | Mode | What it means | Rooms by default | | --- | --- | --- | | **Off** | No camera here. The camera button is hidden, and a camera turns off as you walk in | Focus booths | | **Available** | The camera is there if you want it | Everywhere else | | **Video meeting** | A room meant for calls: you get the join card | Standup, Meeting rooms 1 to 3 | If an admin switches a room to Off while people are inside, their cameras turn off and they're told why. Switching a room to Video meeting only offers the join card; it never turns anything on. Video meeting rooms carry a small camera mark on their label in Map view. ## The join card Walk into a video meeting room with your mic and camera off and a card appears above the dock: the room's name, "Video meeting", the faces of who's there and how many are in. It offers: - **Join with mic** (M): turns your mic on. - **Mic and camera** (C): turns both on. - "Or just listen. Close with Esc." If you leave it alone, it closes itself after 10 seconds, the same as Esc: you just listen, and a thin line on the card shows the time running down. Rest your pointer on it, or tab into it, and it waits; let go and it gives you the full 10 seconds again. Joining, closing it, or turning your mic or camera on any other way answers it for that room. Walk out and back in, and it asks again. There's no "join automatically" setting: only your click or key turns anything on. ## Tiles, the grid and the strip Everyone in the call has a tile, like in any video call: their camera when it's on, otherwise their face, name and mic. Yours says your name with "(you)". A raised hand shows on any tile, camera on or off. - **In a video meeting room** (like the Standup) the tiles open as soon as someone else is there, cameras on or not, and start as a **grid**: everyone, as big as the space allows. Opening the tiles turns nothing on; the join card still asks. - **Elsewhere** they open above the dock once a camera in your conversation is on, as a **strip**. - **Grid** and **Strip** switch between the two. Your pick for video meetings is remembered in this browser. - Order: you first, then raised hands (first up first), then cameras on, then the rest. The strip shows up to six tiles, then "+N". - The corner button on a strip tile enlarges it, and **Hide** folds the tiles into the dock ("Show video" brings them back). - Your self-view can be minimised, but never hidden while your camera is on. - Off the floor page, the tiles fold into the dock and the faces there become live tiles. Tiles only show connected people; agents never have one. ## Participants In a video meeting room a **participants** pane sits on the right of the floor (on a wide screen): everyone in the room with their full name, mic, camera and raised hand, and a soft ring on whoever is speaking. Agents in the room are listed too, in violet. The tiles stop at its edge, so nothing is hidden behind it. Its buttons are for you only: your mic, your camera and your hand. Nobody can turn on someone else's mic or camera. Close it with ×, or use **People** above the tiles to show or hide it; Yomenie remembers your choice in this browser. To save bandwidth, tiles nobody can see (a hidden tab, a folded strip, a tile off screen) stop being received. Audio is never paused. ## Screen sharing **Share screen** sits in the dock right after the camera. Click it and your browser asks what to share: a whole screen, a window or a tab. Nothing is shared until you pick one, and only the people in your conversation see it. - **One person shares at a time** in a conversation. If someone is already sharing, the button says "Priya is sharing · Share yours instead", and pressing it asks first. Share instead, and their share stops; their dock tells them who took over. - **While you share**, a pill above the dock says "You're sharing your screen" with a small preview of what you're sending, and **Stop**. Your browser's own "Stop sharing" works too. - **Watching a share**, it shows big above the dock (at the top on a narrow screen) with the sharer's name. **Full window** fills the floor (Esc fits it back), and **Hide** folds it into the dock ("Show screen" brings it back). Camera tiles stay in the strip below it. Off the floor page, the dock says who is sharing; click it to watch. - **It stops by itself**, like the camera: when you leave the meeting room you started it in, when your open-space conversation ends, when you press Leave, when you walk into a room with video off, or when you close the tab. "Screen sharing turned off when you left Standup." - A share nobody is looking at (a hidden tab, a folded stage, another page) stops being received. - It's never restored after a reload, nothing starts it for you, and it carries no sound. Agents never receive it, and nothing is recorded. Screen sharing needs a desktop browser; phones and tablets can watch but not share. ## Where video works Video and screen sharing on yomenie.us run through Cloudflare Realtime. On a self-hosted server without it, voice works peer to peer and the camera and Share screen buttons are hidden ([self-hosting](https://yomenie.us/docs/self-hosting)). --- # Audio and video devices URL: https://yomenie.us/docs/voice-video/devices Section: Voice and video · Updated 2026-11-14 > Pick your microphone, speaker and camera in Yomenie's audio and video settings, check your level and preview your camera. Previews never leave your device. Open **Audio & video** settings with the small arrow beside the mic button (or beside the camera button) in the dock. ## What's there - **Microphone**: pick an input. A live level meter shows it working, even while your mic is off. That preview stays on your device and is never sent. - **Speaker**: pick an output, and press **Test speaker**. Some browsers (Safari, Firefox) don't let a page choose the speaker; there you'll see a line of help instead. - **Camera**, where video works: pick a camera, with a self-preview that runs only while the settings are open. If your camera is already on, it shows that instead of opening it twice. - **Notifications on this device**: messages, rings and approvals on this device when Yomenie is in the background. Your browser asks for permission only when you flip it ([notifications](https://yomenie.us/docs/account/notifications)). - **Set up mic and camera**, if the browser hasn't been allowed yet. - **Copy voice diagnostics**, for when something's wrong ([troubleshooting](https://yomenie.us/docs/voice-video/troubleshooting)). - A link to **Keyboard shortcuts**. Before you've allowed the mic, device names are hidden by the browser; the list says "Allow microphone to see device names". ## Switching and unplugging - Switching the microphone mid-call swaps it straight away, without dropping the call. - Your choices are saved in this browser, and kept while a device is unplugged, so it's used again when you plug it back in. - If the device you're using goes away, Yomenie falls back to the default and tells you. A camera that goes away turns off with a note; you're never switched to another camera by surprise. --- # Troubleshooting voice and video URL: https://yomenie.us/docs/voice-video/troubleshooting Section: Voice and video · Updated 2026-11-18 > Fix a blocked mic, a paused speaker, a silent peer or a camera that won't start. Report a problem; reports never include your audio. When something's wrong in a conversation with someone, a line above the dock says what, with one thing to do about it. ## "Your mic is off · Turn on mic" Your mic is off and someone could hear you. Press **M** (or ⌘D / Ctrl+D on any page), or click the mic button. ## "Mic blocked for this site" The browser has blocked the mic for yomenie.us, and the mic button turns red. Allow it in the browser's site settings (the icon at the left of the address bar), then press **Try again**. Yomenie notices when you allow it, and turns the mic on if you'd asked for it. If you dismissed the permission prompt when you first arrived, nothing nags you. The buttons stay calm until you try them. ## Other mic and camera problems Outside a conversation, a problem shows as a small note beside the mic or camera button: - **"No microphone found"** or **"No camera found"**: plug one in, or pick another in [Audio & video settings](https://yomenie.us/docs/voice-video/devices). - **"Your mic is in use by another app"** (or camera): close that app's call, then **Try again**. - **"Mic permission wasn't given"**: you closed the browser's prompt. Press **Ask again**. - **"Couldn't open the mic"** (or camera): the browser couldn't start it. Try again, or reload. - **"Camera blocked for this site"**: allow the camera from the icon left of the address bar, then try again. ## "Your browser paused sound · Enable sound" Browsers block sound on a page until you click or press a key on it. Press **Enable sound**, or click anywhere. ## You can't hear someone - Check the speaker button in the dock isn't muted (**Shift+M**). - Check their mic: their face in the dock shows whether it's on. - Check you're in the same conversation: their face should be in your dock. Yomenie watches each call and repairs it when audio stops arriving from someone whose mic is on. It also reconnects after your connection drops. ## "Updating Yomenie…" Yomenie is restarting for a new version. A few minutes before, a line above the dock (or at the top of the page) says **Update coming in about 5 minutes · Keep working, we'll tell you when it starts**. When it starts it says **Updating Yomenie… · Back in under a minute**: the floor stays on screen, dimmed, walking pauses and presence dots go grey until the new server is back. Your mic, camera and screen share stay exactly as you left them, and your call reconnects by itself. In Chat your draft stays, and messages you send meanwhile show a small clock and go out, in order, once Yomenie is back. Then it says **Yomenie is updated** (with the version and **What's new** for a numbered release) or **Yomenie is back**, and fades. If it takes more than a minute, it says so and offers **Report a problem**. More in [When Yomenie updates](https://yomenie.us/docs/getting-started/updates). ## "Yomenie was updated · Reload" A new version of Yomenie is live and this tab still runs the old one. Press **Reload** to get the fixes. The note waits until you're out of a call, no ring is going and you have no unsent message, and × hides it for this version in this tab. ## Strict networks Behind some corporate firewalls, peer-to-peer voice can't connect. On yomenie.us, voice and video go through Cloudflare Realtime, which helps. A TURN relay for self-hosted servers on the peer-to-peer path isn't built yet. (not built yet: https://yomenie.us/docs/roadmap#turn-relay) ## Report a problem The **?** at the bottom of the left rail opens the help menu; **Report a problem** is its first item, on any page (it's also at the top of [Audio & video settings](https://yomenie.us/docs/voice-video/devices) and in the status menu). The box starts with a draft from what your browser already knows, such as "I couldn't hear Kofi and Priya in Standup (around 14:43)." after a call where their audio stopped arriving; change it as you like. Say what went wrong, pick the kind of problem, add a screenshot if it helps, and send. You get a reference like R-7KQ2MX. **See what's sent** shows exactly what goes with it. When a call goes wrong (someone's mic is on but nothing arrives, your audio isn't going out, a connection drops, the camera won't start), Yomenie sends a report by itself and says "Sent a report to help fix this" above the dock; **Add a note** tells us more. After a call that had trouble, the dock offers "Call trouble? Report it" once. Turn automatic reports off in Settings, Profile. [Privacy](https://yomenie.us/docs/privacy#problem-reports) says what's in a report. Working in Claude Code or another [connected tool](https://yomenie.us/docs/mcp/tools#problems-with-yomenie)? Ask it to report the problem: `report_problem` sends it the same way and tells you the reference. If the app won't load at all, open **yomenie.us/app/report**: a plain page that works when the app doesn't. ## Copy voice diagnostics In [Audio & video settings](https://yomenie.us/docs/voice-video/devices), **Copy voice diagnostics** copies a short report to your clipboard: connection states, counters and recent events. Paste it wherever you're asking for help. It never includes audio, chat text, emails, tokens, device names or network addresses, and copying sends nothing: you decide where to paste it. (A problem report sends the same report to Yomenie's team.) --- # Chat: channels, messages and threads URL: https://yomenie.us/docs/chat Section: Chat · Updated 2026-11-16 > Yomenie chat: channels, DMs, threads, @mentions, links to #channels and tickets, reactions, editing, deleting, files and markdown. Chat lives next to the floor. Open **Chat** in the left rail, or click someone in the people panel to message them from any page. ## Channels Every workspace starts with **#general**. Anyone in the workspace can make a channel: press **+** beside **Channels** in the people panel, choose **Create a channel**, give it a name (lowercase letters, numbers and dashes, up to 40 characters) and pick who to add. Public channels are open to everyone in the workspace: anyone can read one, and posting in it adds you to it. Private channels are seen only by their members. Everyone in the workspace is in **#general**, like Slack: nobody can leave it, and owners and admins can't remove people from it. You leave #general only by leaving the workspace. New people are added to it when they join. ## Browse channels To find a channel to join, press **+** beside **Channels** and choose **Browse channels**, or click **Browse channels** under your channel list. You see every public channel with its topic and member count, and **Joined** on the ones you're in. - **Find a channel** searches names, topics and descriptions. Sort by **Name**, **Most members** or **Newest**. - **Join** joins the channel at once and opens it. It shows up in your sidebar straight away. - Click a row to preview the channel first: you read its history, and **Join channel** sits where the message box would be. - The arrow keys move through the list, **Enter** joins (or opens a channel you're in), and **Esc** closes it. - **Show archived channels** adds archived ones, with **View**. - Nothing matches? **Create #name** starts it, with the name filled in. Private channels never show here unless you're a member. The panel search (**⌘K**) also finds public channels you're not in, under **Join a channel**. ## Channel details and settings Click the channel's name at the top of the conversation (or its topic) to open **Channel details**. The faces and count on the right open the member list. It has four tabs: - **About**: the topic and description, who made the channel and when, whether it's public or private, **Copy link to channel** and **Leave channel** (in #general, a line saying everyone in the workspace is in it instead). - **Members**: everyone in the channel, people first and then agents, with the creator marked. Search the list, **Add people** (people and agents), remove someone, or leave. - **Apps**: the channel's [incoming webhooks](https://yomenie.us/docs/chat/incoming-webhooks) and the agents in it. - **Settings**: the name, who can post, and public or private, with one **Save changes**. Archive or unarchive is at the bottom. Who can do what: - **Topic and description**: any member of the channel, and owners and admins. - **Rename**: the channel's creator, owners and admins. - **Add people**: any member of a private channel. On a public channel people join themselves, and owners and admins can add others. - **Remove someone**: the channel's creator, owners and admins. Anyone can leave. Leaving a private channel means a member has to add you back. - **Who can post**: owners and admins choose **Everyone** or **Owners and admins only**. In an owners-and-admins channel everyone else reads, the message box says who can post, and incoming webhooks still post. - **Public or private**: owners and admins. Before it changes you see what it means: a channel made public shows its whole history to everyone in the workspace; a channel made private disappears for everyone who isn't a member. - **Archive**: the creator, owners and admins. An archived channel is read-only, leaves everyone's sidebar and pauses its webhooks until it's unarchived. Its history stays readable from a link. - **#general** can be renamed, but it always stays public, can't be archived and can't be left. Agents can still be taken out of it. - **A team's channel** (its About says "Team channel for Platform") follows its team: the team's people and agents are kept in it, and its name is the team's. Renaming it renames the team, so only owners and admins can; it stays public. See [a team's channel](https://yomenie.us/docs/board#a-teams-channel). Without a right, you see the setting as plain text with who can change it. Changes show up live for everyone in the channel, and they're in the workspace's audit log. If someone removes you while you have the channel open, it says so and links back to #general. ## Direct and group messages Click a person in the people panel to open your direct message with them. To talk with several people at once, press **+** beside **Channels**, choose **New group message**, pick up to seven others, and press **Open conversation**. Opening a conversation with the same people again takes you back to the one you already have. ## How messages look Direct and group messages are bubbles. Yours sit on the right in soft grey. Everyone else's sit on the left in white. Messages from one person close together form a run. In a group message the first bubble of a run shows the sender's name and face. An agent's bubble has a thin violet edge. Each bubble shows its time in the bottom corner. Hover the time to see the full date. Dates between days show as **Today**, **Yesterday** or the date, such as **Mon 10 Nov**. Channels use compact rows by default. To use bubbles in channels too, go to **Settings → Profile → Chat** and set **Message style in channels** to **Bubbles**. The choice is saved in that browser only. Direct messages always use bubbles. ## Ticks, typing and last seen Like a phone messenger, chat shows how far your messages got: - **One light grey tick**: sent. Yomenie has it. - **Two light grey ticks**: delivered. It reached a device of everyone it was for: an open Yomenie tab, the phone app, or a notification that arrived. - **Two dark grey ticks**: read by everyone it was for. In a group message or a channel, ticks turn dark only once everyone has read. People who joined a channel after a message don't count for it. Agents count like anyone else. Channels with more than 50 members show no ticks. To see who read one of your messages, hover it, press **⋯** and choose **Message info**. It lists **Read by** and **Delivered to**, with times. It works in big channels too. A conversation only counts as read while it's open in a tab you can see. A message that arrives while the tab is in the background stays unread until you come back to it. Opening a thread reads its new replies only when nothing above is still unread. While someone writes to you, "Priya is typing…" shows under the conversation, or in the thread when they're replying there. With several people it says "Priya and Marcus are typing…" or "Several people are typing…". In the people panel, their row says "typing…". Typing is never stored. When someone isn't in Yomenie right now, their DM header and their row in the people panel say when they were last seen: "Last seen 10 min ago", "today at 14:05", "yesterday" or a date. That's when they last closed Yomenie on every device. Two switches in **Settings → Profile → Chat**, both on by default, work both ways: - **Read receipts**: off, others don't see when you read their messages, and you don't see when they read yours. Delivered ticks still show. - **Show when I was last seen**: off, others don't see when you were last seen, and you don't see theirs. Yomenie applies both on the server, so a switched-off read or last seen never reaches anyone's device. ## Threads Hover a message and press **Reply in thread** (the speech icon in its toolbar; in the small form of the toolbar it's under **⋯**) to start a side discussion. On a touchscreen, press and hold the message instead. The thread opens on the right, with its own reply box, so the main conversation stays tidy. ## Links to messages Share a message like you would in Slack. Hover it (or press and hold on a phone), open **⋯** and choose **Copy link**. Thread replies have links too. **Copy link** in the side drawer's header (under **⋯** in a direct message) copies the conversation's link, or the thread's while a thread is open. Paste the link anywhere in Yomenie, such as a message or a ticket, and it shows a small preview under it: who wrote the message, where, when, and how it starts. People who can't read that conversation see only "Message in a private conversation", nothing about what's in it. For a public channel someone isn't in, the preview says so, and opening it lets them read and join. Opening a link takes you to the message, even if it's far back in the history. It stays highlighted until you open another link or leave the conversation. Thread replies open in their thread. Notifications for direct messages, mentions and thread replies open at the message too. Your AI tool can read a message from its link, and every message it reads or sends comes with its link (see [From your coding tool](#from-your-coding-tool)). ## Mentions Type **@** in any message box (a channel, a direct message, a thread, or the message box in the side drawer) to mention someone. A list opens with people (in amber), AI teammates (in violet) and teams (with how many are on them). Keep typing to narrow it: any word of a name works, accents don't matter ("tom" finds Tomás). The arrow keys move, **Enter** or **Tab** inserts, **Esc** closes it. - **@Priya** mentions a person. They get a notification, if they can read the conversation. - **@Iris** mentions an AI teammate. The person it reports to gets the notification. - **@platform** mentions a whole team, like a group email: its address is its channel's name. Everyone on the team who can read the conversation gets one notification. People who are on the team and mentioned by name get one, not two. Mentions show as chips in the message, with the current name (renaming someone never breaks a mention). Click a person's chip for their card and **Message**; a team's chip opens its channel. Messages that mention you or a team you're on have a soft amber background, and the people panel shows a small **@** beside a conversation's unread count while it has unread mentions for you. In a private channel or a direct message, mentioning someone who isn't in it shows "Priya isn't in #design, so they won't be notified" above the message box, with **Add Priya** when you're allowed to add people. A public channel reaches everyone in the workspace. You're never notified about your own mentions. `@here` and `@channel` aren't there yet. ## Channels and tickets Type **#** in any message box for a list of channels you can read, then, once you type a ticket's key or a couple of letters of its title, tickets ("#login" finds "Fix the login redirect"; "#YOM-1" finds YOM-12). The keys work the same as for mentions. Picking a channel inserts `#platform`; picking a ticket inserts its key, `YOM-12`. You can also just type them. `#platform` links the channel, and any ticket key (`YOM-12`, `ISS-4`, or an older id a ticket had, like `TKT-13`) links the ticket, like in Jira. Code (`` `YOM-12` ``) and links stay as you wrote them. - A **channel link** opens the channel. A private channel you aren't in shows as "private channel", without its name. - A **ticket chip** shows the key, the title and a dot in its column's colour; hover it for the board, status and assignee. Click it to open the ticket on its board. A ticket you can't see shows only its key. - Links follow renames: a renamed channel, or a ticket that moved to another board (YOM-12 → SA-4), shows its new name or key in old messages too. - The ticket gets a line in its activity, "Mentioned in #platform by Priya" with a link to the message. Only people who can read that conversation see the line, and each message adds it once. ## Notifications per conversation DMs, group messages and threads you're in notify you about every message; channels only when you're mentioned. Change it per conversation from the **⋯** at the top right of the conversation, the bell on its row in the left panel, or **Channel details → Notifications**: **All messages**, **Mentions only**, or **Mute** for an hour, until tomorrow or until you unmute. A muted conversation shows a muted bell, no bold and no unread count, and sits below the others; a mention there doesn't notify you either. New messages play a short chime and, while you're elsewhere in Yomenie, show a small card. More in [Notifications](https://yomenie.us/docs/account/notifications#each-conversation). ## Reactions React to a message instead of replying "ok", like Slack. Most of the time that's **✅** for done or seen, or **👍** for agreed; any emoji works. - Hover a message (or tab to it) and a small toolbar appears, without covering the message: beside a bubble, in the empty space next to it, and in a channel at the top right of the row. It holds **✅ 👍 👀**, the smiley for any other emoji, **Reply in thread**, and **⋯** for **Copy text**. The arrow keys move between its buttons. When there isn't room for all of it (a narrow window, a wide bubble), it shrinks to the smiley and **⋯**: the smiley then offers **✅ 👍 👀 🎉 ❤️** and **+** for any emoji, and **⋯** holds **Reply in thread** and **Copy text**. - The smiley (or **+**) opens a picker: type to find an emoji by name ("thumbs", "done", "ship"), **Enter** picks the first, the arrow keys move through the grid. You can paste any single emoji into it too. - On a touchscreen, press and hold a message: a sheet opens from the bottom with **✅ 👍 👀 🎉 ❤️**, **+** for any emoji, **Reply in thread** and **Copy text**. - Reactions show as chips under the message, each with its emoji and count, in channels, direct messages and threads. The ones you added are highlighted in blue. Press a chip to add yours or take it back. Hover it to see who reacted. - A message can carry up to 20 different emoji. Any member of the conversation can react, also in a channel where only owners and admins post: reacting isn't posting. An archived channel can't be reacted to, and neither can a public channel you're only previewing (join it first). Reactions don't notify anyone, don't count as unread and don't mark anything as read. They aren't in the audit log. On the phone app you see reactions but can't add them yet. ## Writing messages - Type in the rounded box: the paperclip on its left attaches files, the round button on its right sends. **Enter** also sends, and **Shift+Enter** adds a new line. - Messages are markdown: bold, italic, strikethrough, inline code, quotes, lists, tables and links. The toolbar has buttons for the common ones, with **⌘B** for bold and **⌘I** for italic. - Code blocks (three backticks) are highlighted, with the language shown in the corner. - Messages can be up to 8,000 characters. - Raw HTML is never rendered, so a message can't run anything in your browser. New messages arrive live. A red **New** line marks where you left off, and red badges in the people panel count unread messages. ## Editing a message Fix a typo or add what you forgot, like Slack. Hover one of your own messages, open **⋯** and choose **Edit message** (on a phone, press and hold the message). The message turns into a box with your text: - **Enter** saves, **Shift+Enter** adds a new line, **Esc** cancels. - Everyone sees the new text at once, with a small "(edited)" beside it. It doesn't count as a new message, so nothing goes unread again. - Mention someone new and they're told, as if you had just sent it. People you had already mentioned aren't told again. - You can only edit your own messages, and not in an archived channel. A message with files can lose its text; one without needs some. ## Deleting a message Sent something by mistake? Hover one of your own messages, open **⋯** and choose **Delete message** (on a phone in the browser, press and hold the message). Yomenie asks once, then: - The message stays where it was and reads "Message deleted" for everyone, like WhatsApp or Slack. - Its text, files and reactions are gone for good. The files are deleted from storage, and notifications about it are removed. - A thread keeps its replies under the deleted message. - You can only delete your own messages, and not in an archived channel. There's no undo. ## Sharing files Share files in channels, direct and group messages, threads, and the side drawer beside the floor. - **Attach** with the paperclip beside the message box, drag files onto the conversation (or the thread), or paste a screenshot. - Files start uploading as soon as you attach them, each with a progress bar. Press **×** on one to take it off. A message can be files alone, or text with files: up to 10 files, each up to 25 MB. - Press **Enter** while files are still uploading and the message waits for them, with a progress bar and **Cancel**. - Images (PNG, JPEG, GIF and WebP) show as a preview. Click one for the large view, with **Download**. Every other file shows as a card with its name, size and type, and a download button. Who can see a file: exactly who can read the conversation. A file in a private channel or a direct message never reaches anyone outside it, and a file you attached but didn't send is only yours (it's deleted after a day). Kept private by default: - Location and camera details (EXIF and GPS) are removed from JPEG photos, and text notes from PNG images, before the file is stored. The image itself isn't changed. - Files are downloaded, never opened as web pages: anything that isn't one of the four image types (SVG and HTML included) is served as a download. - Links aren't unfurled and previews are never made by anyone else. Yomenie doesn't log file names or contents. Each workspace can store up to 5 GB of files. A tool you [connected over MCP](https://yomenie.us/docs/mcp) sees a message's file names, types and sizes, never the contents. On the phone app, a message shows its file names; previews and downloads are in the browser. ## From your coding tool A tool you [connected over MCP](https://yomenie.us/docs/mcp), such as Claude Code or Codex, can read your chat, send messages, edit or delete your messages and react as you, if you allowed it. Its messages are yours, with a quiet "via Claude Code" (or the tool's name) beside your name, so everyone can tell. It reads and posts only where you can yourself. See [what a connected tool can do](https://yomenie.us/docs/mcp/tools#chat). A quiet line under the conversation's header points the way. Until your tool can read chat it says what it could do here, with **Connect Claude Code or Codex →** for the setup (a tool connected only for tickets needs connecting again with **Read your chat** ticked). Once it can, it names the tool and suggests something to ask, such as "Catch me up on #eng and tell me what needs me", with **More prompts →**. **×** hides it in that browser. ## The people panel The panel beside every page lists: - **Channels** and your group messages. - **Humans**, online first, with a presence dot and status note. - **Agents**, with what they're working on, or Idle or Paused. Clicking a person opens your conversation with them in a drawer on the right, on any page except Chat, so you can keep doing what you were doing. The cursor is in the message box, so you can type at once. It is the same chat as the Chat page: reply to a message, open a thread, react, edit or delete your own, copy a message's link, and scroll up for older messages. Channels and group messages open in the same drawer, and so does everything else that opens a conversation: a notification in the bell, **Open** on a message toast, a desktop notification you click while Yomenie is open, **Message** on someone's card, a missed ring or a visit, a **#channel** chip, a team's chip, and a link to a conversation in a message or a ticket. The page underneath stays as it was, and so does your call. A thread reply opens its thread in the drawer. ⌘-click (Ctrl-click on Windows and Linux) or a middle click on a link still opens it in a new tab. On the Chat page itself, these open the conversation right there. The drawer works like Chat: - **What it shows:** messages as rows, or as bubbles if you chose that style. Reactions, mentions, links to channels and tickets, files and read ticks all show. - **Writing:** the message box has files and the **@** and **#** pickers. If you can't post there, a line says why instead, and a public channel you're not in offers **Join channel**. - **Threads:** **N replies** opens the thread inside the drawer. Reply there, then use the back arrow to return. - **Header:** **#name** and its topic, the members, your notification setting (the bell) and **Open in Chat** for the full page, with members, settings and details. A direct message shows the person's face and name, with when they were last seen (or their status) under it, the bell, and **⋯** for **Copy link to conversation**, their **AI work** and **Challenge to chess**. **Esc** goes back from a thread, then closes the drawer. Keys you type in the drawer never move you on the floor. **Open in Chat** in its header, or Chat in the left rail, takes you to the full Chat page. Hover a person for **Find on floor**. Press **⌘K** (Ctrl+K on Windows and Linux) on any page to open the panel's search: it filters channels, group messages, people (by name or status) and agents (by name, task or manager). Enter opens the first match. On a phone, the panel is a drawer. ## What's not there yet Chat today doesn't have message search, deleting messages (or files), or `@here` and `@channel`. Mentions in ticket comments don't notify anyone yet. To post into a channel from CI, monitoring or your own scripts, use an [incoming webhook](https://yomenie.us/docs/chat/incoming-webhooks). --- # Incoming webhooks URL: https://yomenie.us/docs/chat/incoming-webhooks Section: Chat · Updated 2026-11-14 > Post into a Yomenie channel from CI, monitoring or scripts. Slack-compatible: paste the Yomenie URL where a tool asks for a Slack webhook. An incoming webhook lets a tool post into a Yomenie channel: deploys from CI, errors from Sentry, releases from GitHub, anything that can send an HTTP request. It speaks Slack's format, so a tool that posts to a Slack incoming webhook works here when you paste the Yomenie URL instead. Messages show in the channel under the webhook's name with a small **App** tag, live, like any other message. ## Add one Owners and admins can add webhooks. 1. Open the channel in **Chat**, click its name in the header to open **Channel details**, and go to the **Apps** tab. 2. Choose **Add incoming webhook**, give it a name ("GitHub", "CI", "Sentry") and, if you like, an icon: an emoji, a shortcode like `:rocket:`, or an `https://` image URL. 3. Confirm it's you if asked (a passkey, or an email link). 4. Copy the URL. It looks like `https://yomenie.us/hooks/ym_wh_…` and is shown **only once**. Treat the URL like a password: anyone who has it can post in that channel. Keep it in your CI's secrets, not in a repository. If it leaks, regenerate it (below). Everyone who can read the channel sees which webhooks post into it, who added them, when they were last used and how many messages they sent. Webhooks belong to the workspace: they keep working when the person who added them leaves. ## Post a message ```sh curl -X POST -H 'Content-type: application/json' \ --data '{"text":"Deploy of *succeeded*"}' \ https://yomenie.us/hooks/ym_wh_... ``` A successful post answers `200` with the body `ok`. Slack's form encoding works too: ```sh curl -X POST --data-urlencode 'payload={"text":"Nightly build passed"}' https://yomenie.us/hooks/ym_wh_... ``` ### What you can send | Field | | | --- | --- | | `text` | The message, in Slack's mrkdwn (below). Required unless `blocks` or `attachments` carry text. | | `username` | Shows instead of the webhook's name for this message (one line, up to 40 characters). | | `icon_emoji` | An emoji or a shortcode like `:tada:` for this message. | | `icon_url` | Accepted and ignored: only the icon set on the webhook shows, so a sender can't make every reader's browser load an image from their server. | | `blocks`, `attachments` | When there's no `text`, their text is shown as plain lines: section text and fields, headers and context; an attachment's `fallback`, or its pretext, title and text. Buttons, images and layout aren't shown yet. | Other fields are ignored, so payloads written for Slack don't fail. ### Formatting Slack's mrkdwn is turned into Yomenie's markdown: | You send | You see | | --- | --- | | `*bold*`, `_italic_`, `~strike~` | **bold**, *italic*, ~~strike~~ | | ``, `` | a link (http, https and mailto only) | | `` `code` `` and ```` ```blocks``` ```` | code, left exactly as sent | | `&`, `<`, `>` | `&`, `<`, `>` | | ``, ``, `<@U123>` | plain text: nobody is pinged | Raw HTML is never rendered. Text longer than a chat message (8,000 characters) is cut with "…". ### Errors Errors are short plain-text codes, like Slack's: | Status | Body | Meaning | | --- | --- | --- | | 400 | `invalid_payload` | The body isn't JSON (or a form with `payload=`) in Slack's shape. | | 400 | `no_text` | Nothing to show: no `text`, and no text in `blocks` or `attachments`. | | 404 | `no_service` | The URL is wrong, was regenerated, or the webhook was revoked. | | 404 | `channel_not_found` | The channel is gone. | | 410 | `channel_archived` | The channel is archived. The webhook works again once it's unarchived (unless it was revoked). | | 413 | `payload_too_large` | The body is over 64 KB. | | 429 | `rate_limited` | Too fast: about one message a second, bursts of 20. Wait for `Retry-After` seconds. | | 405 | `method_not_allowed` | Only `POST` works. | ## GitHub Actions Store the URL as a repository secret named `YOMENIE_WEBHOOK_URL`, then post with curl: ```yaml - name: Tell #deploys if: always() env: YOMENIE_WEBHOOK_URL: ${{ secrets.YOMENIE_WEBHOOK_URL }} run: | curl -sf -X POST -H 'Content-type: application/json' \ --data "{\"text\":\"${{ github.workflow }} on <${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}|${{ github.ref_name }}>: *${{ job.status }}*\"}" \ "$YOMENIE_WEBHOOK_URL" ``` Or keep using Slack's action, pointed at the Yomenie URL: ```yaml - uses: slackapi/slack-github-action@v2 with: webhook: ${{ secrets.YOMENIE_WEBHOOK_URL }} webhook-type: incoming-webhook payload: | text: "Release ${{ github.ref_name }} is out" ``` Sentry, Vercel, Zapier, n8n and other tools with a "Slack incoming webhook" option work the same way: paste the Yomenie URL where they ask for the Slack one. ## Regenerate or revoke In **Channel details → Apps**, owners and admins can: - **Regenerate URL**: a new URL, shown once. The old one stops working at once. Use it when a URL may have leaked. - **Revoke**: the webhook stops working for good and leaves the list. Messages it already posted stay. Archiving a channel pauses its webhooks: they answer `410 channel_archived` until the channel is unarchived, and the Apps tab says so. Adding, regenerating and revoking are in the workspace's audit log. The messages themselves are ordinary chat. ## Self-hosting and local development With `pnpm dev` there's no edge Worker, so the API takes webhooks itself at `http://localhost:8787/hooks/` (only in `AUTH_MODE=dev`). In production the Worker answers `/hooks/`. --- # Board and tickets URL: https://yomenie.us/docs/board Section: Board and tickets · Updated 2026-11-18 > A ticket is a brief an agent can pick up and a record of what happened. Create it through MCP from Claude Code; comment, assign and move it on the board. The board is where work lives, for people and agents alike. Open **Board** in the left rail. A ticket is two things: a **brief** someone (often an agent) can pick up, and a **record** of what happened to it. People decide and review; agents do the work. **Tickets are created through the [MCP server](https://yomenie.us/docs/mcp)**: ask Claude Code, Codex, Cursor or another connected tool, or let an agent add them. The board has no Add ticket button. It's where you comment on tickets, assign, move and edit them; your connected tool can do all of that too, with the same rules. ## Boards and teams A workspace has **teams** (people and agents; someone can be on several) and **boards**. Each board belongs to a team, or to the whole workspace. No team or board is special. A new workspace starts with one team named after the workspace (say, "Acme") with only you on it, and one board called "Board", so the board menu lists "Board" under "Acme". People who join later aren't put on a team: they join the ones they work with. **Board** opens the first board of a team you're on, then a workspace-wide board. If there's neither, it says so, with **Create a board** for owners and admins. The board's title is also the switcher: click it ("Sprint 16 ▾") for a menu of the workspace's boards, grouped by team with workspace-wide boards last and a check on the one you're on. Type in **Find a board** to narrow it down (a board's name or its team) and press Enter to open the first match; **Manage boards in Settings** at the bottom opens Settings → Team. With only one board the title is plain text. Beside the title are the board's team and how many tickets are open, then the search box and, at the right, the person filter (**Everyone**, **Mine**, faces, **Unclaimed**). Under it, one line holds the board's description. ## Managing teams and boards Everything is in **Settings → Team**, below the people: - **Teams** lists each team with who is on it, its channel and its boards. Anyone can **Join** or **Leave** a team. Owners and admins also get a **⋯** menu: **Rename**, **People and agents** (who is on the team), **New board for this team**, **Create team channel** or **Link a channel…** (or **Unlink channel**) and **Delete team**. Deleting a team asks first; nobody leaves the workspace, no tickets are deleted, its boards become workspace-wide and its channel is archived. - **Boards** lists the active boards with their keys. Owners and admins create one with **New board** (for a team, or workspace-wide; the **Key** fills in from the name as you type, and you can change it) and use **⋯** to **Rename or move** (name, key, a one-line description, and its team) or **Archive** it. - An **archived** board is left out of the board menu and from connected tools' board list. Its tickets are kept, and the board stays readable at its address. **Unarchive** brings it back (under **Archived** in the Boards list). Names are 1 to 40 characters on one line, and unique in the workspace (ignoring case). Members see the lists read-only, apart from joining and leaving teams. Every change by an owner or admin is written to the [audit log](https://yomenie.us/docs/connections/audit-log) (a board's description by its length only); joining or leaving a team yourself isn't. Open boards pick up renames and moves at once. ## Ticket ids and board keys Every board has a **key**, and its tickets are numbered on it: on a board with the key YOM they're YOM-1, YOM-2 and so on, like Jira. A key is 2 to 6 letters or digits, starting with a letter, and unique in the workspace. **New board** suggests one from the name as you type (Issues → ISS, ScreenApp → SA, Sprint 16 → S16), with a digit added if it's taken, and shows what the tickets will be called ("Tickets will be ISS-1, ISS-2…"). Type your own and it stays. A new workspace's first board, "Board", takes its key from the workspace's name (Acme → ACM). - **Moving a ticket to another board** gives it the next number there (YOM-12 → SA-4). - **Changing a board's key** (⋯ → **Rename or move**) keeps every ticket's number under the new key (SCR-4 → SA-4). - **Old ids keep working, forever.** Links, `?ticket=` addresses, notifications, blockers and your connected tool all find a ticket by any id it has had. Opening an old link shows the ticket under its current id and puts that in the address; the ticket's header says **Previously YOM-12**. Before board keys, ids were workspace-wide (TKT-13). Every ticket kept its number and took its board's key (TKT-13 on the Yomenie board is now YOM-13), and TKT-13 still works. `TKT` itself can't be a board's key. Key changes are in the audit log. ## A team's channel Every team can have its own channel, so you can talk to the team without making one by hand. **New team** has **Also create #platform** (the team's name as a channel name), ticked. The channel is public, and its topic says whose it is. - **The name is the team's address.** The channel is always named after the team: renaming the team renames the channel, and renaming the channel (in its settings) renames the team. Only owners and admins can rename a team's channel, since it renames the team too. If another channel already has the name (archived ones count), the team isn't created or renamed: link that channel instead (**Link #platform instead** in the dialog), or pick another name. - **People follow the team.** Joining a team, or being added to it, puts you in its channel; leaving it, or being taken off, takes you out. Agents on the team too. Leaving the channel doesn't take you off the team. The last person in the channel stays in it. - **Existing channels.** **Link a channel…** makes an existing public channel the team's channel and adds the team's people and agents to it. If its name isn't the team's, the dialog says it will be renamed. #general and private channels can't be linked, and a team's channel can't be made private. - **Archiving and unlinking.** Archiving a team's channel unlinks it (unarchiving doesn't link it again). **Unlink channel** keeps the channel and everyone in it. Deleting the team archives its channel, never deletes it. The channel's **About** says "Team channel for Platform". Links, unlinks and the membership changes an owner or admin makes are in the audit log; joining or leaving a team yourself isn't, and neither is the channel change it brings. ## Columns and order A board starts with four columns: **Backlog**, **In progress**, **Review** and **Done**. There's no priority field: **the top of a column goes first**. Drag cards up and down to order them, or across to move them. Lists over the API and MCP come back in the same order. **Each board can have its own columns.** There's no settings screen for them: ask your AI tool, as an owner or admin. "Add a QA column before Review on the Platform board, and make it a review column", "Rename In progress to Building", "Remove the Review column, move its cards to Done". The board shows whatever columns it has, scrolling sideways when there are many (up to 12). A few rules hold whatever the columns are called: - **New tickets go to the bottom of the first column**, unless the tool names a column (or to the backlog list, when the board has it on: below). - **The last column is Done**: tickets there count as done (metrics, unblocking, newest first). Move a column to the end and it's Done from then on. - **A review column** (marked with a small **review** tag) asks a person to look when a card lands there ([below](#review-goes-to-a-person)). Any number of columns can be review columns. - **Removing a column** moves its cards to the column on its left (the new first column, for the first), unless you say where. Nobody is notified for those moves. - **Taking a ticket** puts it in the working column: the first column after the first that isn't review or Done (In progress on a new board). Column changes are in the [audit log](https://yomenie.us/docs/connections/audit-log) and show on open boards at once. Boards from before custom columns are exactly as they were. A ticket moved to another column without a place (from the detail, a card's menu or `update_ticket`) lands at the top, except in Backlog, where it goes to the bottom. **Done is newest first**: the ticket that got there last is on top. Its order is the time each ticket moved to Done, so cards in Done can't be dragged up or down, and a card dropped anywhere in Done goes to the top. ## The backlog list and its line A board can trade its Backlog column for a **ranked backlog list** with a line for what's next. It's off until an owner or admin asks their AI tool ("Turn on the backlog list for the Platform board"), and comes on by itself with sprints. Turning it on makes the Backlog column's cards the list, in their order, and the column goes; turning it off puts them back in a first column called Backlog. Turning sprints off leaves it on. The list sits at the left of the board, a little wider, with dashed cards: the top is what's next. New tickets land at its bottom. The arrow in its heading folds it into a narrow strip, and the board remembers that in your browser. When a sprint ends, or one starts empty, it opens once by itself; fold it again and it stays folded. A **dashed amber line** splits what's next from what's later. With cards above it, its pill says how much: **Up next · 3 cards · 8 pts**, or **Next sprint · …** with sprints on, and cards below it are lighter. With nothing above it, it just says "Drag cards above this line for what's next". Drag cards up and down, across the line, or drag the line itself. Under the line, **Move these 3 to In progress** (the board's first column, by name) moves everything above it there, in order, in one go (into the sprint, with sprints on). Grooming is ticket work: any member can do it, and so can their AI tool: "Groom the Platform backlog: put the most urgent first and about 20 points above the line", then "Move what's above the line onto the board". ## Sprints Boards are plain Kanban by default. **Sprints** are turned on, off and sized through your AI tool, as an owner or admin: "Turn on two-week sprints for the Platform board". Sprints turn the backlog list on (above). With sprints on: - A sprint is either **running** or not. At the right of the board's title it reads **Sprint 17 · ends Fri · 12 of 20 pts** (points in Done, of the sprint's total; no points part while it has none) with **End sprint**, or **No sprint running** with **Start sprint**. On a phone it wraps under the title. - **Start sprint** opens a small dialog: "Start Sprint 4", its length (the board's, changeable for this sprint) and end day, and who joins: the cards above the backlog line plus any carried over ("5 cards, 18.5 pts will join"). With nothing to join it warns "Sprint 4 will start empty", and starts anyway if you go ahead. - The columns show the running sprint's cards. With no sprint running they show the cards waiting for the next one (carried over, or put on the board meanwhile), the backlog opens by itself, and the button under its line reads **Start Sprint 4 with these** (it opens Start sprint). An empty running sprint says so in its first column ("Sprint 4 is empty. Drag cards from the backlog."). - Dragging a card out of the backlog onto a column puts it in the sprint (or, between sprints, in the next one); dragging one back takes it out. - **End sprint** asks one question: put the cards that aren't done **back in the backlog** (just below the line) or **keep them on the board** for the next sprint, and previews it ("4 unfinished cards go back to the backlog."). It doesn't start the next sprint: the board says **No sprint running** until someone starts it. Done cards stay with the sprint that ended. - Turning sprints on doesn't start one either: the open cards on the board wait for Sprint 1. Any member can start and end sprints and move cards in and out (from the board or their tool: "Start the sprint", "End the sprint, unfinished to the backlog", "Put YOM-12 and YOM-14 in the sprint"). Turning sprints off ends the running sprint, and the board shows every card again. Sprint settings and every ended sprint are in the audit log. There's no planning screen, sprint goal or velocity chart. ## Big boards Boards can hold thousands of tickets, most of them in Done, and the board never loads them all at once. The board fills the screen under its title, search and filter, and each column scrolls on its own with its name and count staying in view. Each column shows its first 30 cards and loads the next 30 as you scroll near its end; there's no button, just a "Loading more…" placeholder while they come. The number beside each column's name is always the full count (1,284), not just what's loaded. Dragging, quick assign and live changes work on loaded cards as usual: a card that moves into a part of a column you've already scrolled through shows up in its place, and one that lands further down appears when you scroll to it. ## Search The search box beside the board's title (**Find a ticket: key, title or label**) finds any ticket on this board, however old, Done included. Type a ticket's id (`YOM-12`, or any id it had before, like `TKT-12`) to find exactly that ticket, or words from its title or label. The matches replace the columns as a short list (id, title, column and who has it); click one, or press Enter on it, to open it. More load as you scroll. The search is in the address (`?q=login`), so you can share it. **Esc** or **×** clears it and brings the columns back. Your connected tool searches the same way, with `search_tickets` (see [Through MCP](#through-mcp)). ## On the card A card shows the id, label, title, who has it, a red **Blocked** mark while it waits on an unfinished ticket, a small link count, and points if it has any (shown as typed: 0.5, 1.5, 3). Standups go through the board together, so the common changes work on the card itself: - **Assign:** press the face (or "Unclaimed"). Type to filter; **Me** comes first, then the people in your conversation on the floor, then everyone, and **Unassign** at the end. One press saves. - **Card menu** (⋯): **Open**, **Assign…**, **Comment…**, **Move up**, **Move down** (not in Done, which keeps its own order) and **Move to** each other column (and the backlog list, when it's on). It works from the keyboard: Tab to the ⋯ button, Enter, arrows. - **Comment…** opens a small box. Enter posts; Shift+Enter is a new line. - **Drag:** with the pointer or touch, or Tab to a card's grip and use the keyboard. ## Filter by person The faces above the columns show whoever has a card on this board. Press one (or several) to see only their tickets, **Mine** for yours, **Unclaimed** for nobody's, **Everyone** to clear. The column counts follow the filter, and the columns load only the matching tickets. The filter is in the address (`?who=priya`), so you can share it, and this browser remembers it. ## The ticket Open a ticket by clicking its card (or Enter). The address gets `?ticket=YOM-142`, so you can link to it. In it: | Part | Notes | | --- | --- | | Title | Up to 200 characters | | Description | The brief, in markdown, up to 20,000 characters. Write what and why, then **Done when** as a checklist (`- [ ] …`). Tick a box to mark it done; the description says "2 of 4 done". Edit and Preview while writing | | Column, assignee | A person, an agent, or nobody. **Take it** assigns it to you and moves it to In progress | | Label | Optional, up to 24 characters | | Points | Optional: 0 to 100 in steps of 0.1, so 0.5 and 1.5 work (0 means not sized). Type a number or pick 0.5, 1, 2, 3, 5, 8 or 13 from the menu beside the field. The board doesn't ask for it | | Blocked by | Tickets this one waits on, by id or words from the title. Lists what it **blocks** too | | Links | The MR / PR, the branch and, once it ships, the release | | Activity | Comments and what happened, newest at the bottom | Changes made by anyone else show up in an open ticket at once. ### Following a chain of tickets A ticket mentioned inside a ticket opens in place: a ticket in the description or a comment, one under **Blocked by** or **Blocks**, or a "Mentioned in" line. Each one you open is a step on a trail, so you can always get back: - **← YOM-204** in the ticket's header goes back to the ticket you came from. - Your browser's Back, a trackpad swipe and Alt+← (or ⌘+[ on a Mac) do the same, one ticket at a time. - From the third ticket on, the arrow beside the back button lists the whole trail, newest first. Pick one to jump straight back to it. Hover it, click it, or press ↓ on the back button. - Each ticket opens where you left it scrolled. Opening a ticket from the board starts a new trail. Closing the ticket (×, Esc or a click outside) takes you back to the plain board and clears the trail, so Back then leaves the board as usual. A ticket on another board opens on its own board; Back brings you to the ticket you came from. A reload keeps the trail. ### Blocked by A ticket can wait on others in the same workspace, on any board. It can't wait on itself, and no loops: if YOM-9 waits on YOM-12, YOM-12 can't wait on YOM-9 (or on anything that waits on YOM-9). Up to 20 per ticket. While any of them isn't done, the card shows **Blocked**. Taking a blocked ticket still works: the app asks you to confirm first, and over MCP `claim_ticket` claims it and returns a warning naming the open blockers. When the last blocker moves to Done, the person the ticket is assigned to gets a notification ("YOM-139 is unblocked"). ### Links Each link has a kind: **MR / PR** (GitLab and GitHub alike), **Branch**, **Release**, **Doc** or **Other**, an `https://` address and an optional short title like `!412` or `v1.4.0`. Up to 20 per ticket. Yomenie never opens or fetches them; they're shown as you gave them. ### Activity One timeline per ticket: comments from people and agents (markdown, like chat) and events in between: created, moved, assigned, title or description edited, blocker added or removed, link added or removed, and where the ticket was mentioned. Events never repeat the text that changed. Comments and changes made through a connected app say so: "Priya · via Claude Code". **Show older** pages back. ## Refer to tickets, channels and people In a description or a comment, write another ticket's key (`YOM-12`, or any id it had before) and it becomes a chip with its title and a dot in its column's colour; hover for the board, status and assignee, click to open it. `#platform` links a channel and `@Priya` mentions someone, as in [chat](https://yomenie.us/docs/chat#channels-and-tickets). Type **#** for a list of channels and tickets, and **@** for people, AI teammates and teams. In **Edit**, references show as you'd type them; they're saved as links that follow renames and new keys. Mentions in ticket comments don't notify anyone yet. When a ticket is mentioned somewhere else, its activity says so: "Mentioned in YOM-14 by Priya", or "Mentioned in #platform by Priya (see message)". One line per message or ticket, however often it's edited. A line from a conversation shows only to people who can read that conversation. A ticket you can't see shows only its key, unlinked. ## Review goes to a person There's no reviewer field. When a ticket assigned to an agent moves into a review column (**Review** on a new board), the agent's manager gets a notification ("YOM-142 is ready for review"), unless they moved it themselves. When a connected app moves a ticket assigned to you into Review (Claude Code finishing work for you), you get one too. Both kinds can be turned off under [notifications](https://yomenie.us/docs/account/notifications). ## Through MCP Connect Claude Code with the [plugin](https://yomenie.us/docs/mcp/claude-code-plugin) (`/plugin marketplace add https://yomenie.us/claude-code/marketplace.json`, `/plugin install yo@yomenie`, then `/mcp` → **plugin:yo:yomenie** → **Authenticate**), or [another tool](https://yomenie.us/docs/mcp) with the MCP server, and ask in plain words: "Create a ticket on the Platform board: fix the flaky login test", "What should I work on next?", "Claim it", "Comment on YOM-142 that the fix is in !412", "Attach the MR https://gitlab.com/…/merge_requests/412", "Move it to review". "Find the ticket about invoice reminders" or "What did we finish this week?" use `search_tickets`, which pages through any number of tickets. Behind those it uses `create_ticket`, `next_ticket`, `get_ticket`, `claim_ticket`, `comment_on_ticket`, `add_link`, `set_blocked_by` and `update_ticket`; for the board itself `get_board`, `update_board` (columns, sprints), `set_backlog_line`, `move_above_line`, `end_sprint`, `move_to_sprint` and `move_to_backlog` ([all the tools](https://yomenie.us/docs/mcp/tools)). A new ticket goes on the board you name; your tool can leave the board out only when the workspace has exactly one active board, otherwise it's told which boards to pick from. Codex, Cursor and other MCP clients connect too: see [Connect your tool](https://yomenie.us/docs/mcp). The board has the steps too, with **Copy** buttons and a few things to ask. Until you've connected a tool to the workspace, the line under the board's title (after its description) says "Tickets come from your AI agent. Ask it to create one, then comment, assign and move it here." with a **Connect Claude Code or Codex →** link that opens it. Once you have, it names your tool and suggests something to ask, such as "Take the next ticket, do it and move it to Review", with **More prompts →** linking to [Work through your AI agent](https://yomenie.us/docs/getting-started/work-through-your-agent). **×** hides the line in that browser (closing the "connect" line doesn't hide the tip you get once connected). Once it's hidden, the same setup is at the top of **Settings → Connected apps**. Every member can change tickets (the `tickets:write` action). Changes to tickets are written to the [audit log](https://yomenie.us/docs/connections/audit-log); comments live on the ticket. ## Agents and leases When an agent takes a ticket, it holds a **lease** for a set time (30 minutes by default, up to 4 hours). While the lease is live, nobody else, person or agent, can claim that ticket, so two never work on the same one. Claiming assigns the ticket to the agent and moves it from the backlog or the first column to the working column (In progress). A paused agent, or one without the "Claim a ticket on a lease" scope, can't claim. [Agent permissions](https://yomenie.us/docs/agents/permissions). ## Live updates When a ticket changes, in the app, from a connected tool or by an agent, every open board updates for everyone at once (the changed cards and the counts), and so does an open ticket and an open search. Nobody needs to reload. --- # Git webhooks URL: https://yomenie.us/docs/board/git-webhooks Section: Board and tickets · Updated 2026-11-16 > Point a GitHub or GitLab webhook at Yomenie and tickets follow their pull and merge requests: a draft to In progress, opened to Review, merged to Done. A git webhook lets GitHub or GitLab move tickets for you. Put a ticket's key in a branch name or a pull request title, and the ticket follows the pull request across the board. Nobody drags cards after the fact, and nobody has to remember to. It works with GitHub, GitHub Enterprise, GitLab.com and self-hosted GitLab. There's no app to install, and Yomenie keeps no GitHub or GitLab token. ## Add one Owners and admins can add git webhooks. 1. Open **Settings → Git** and choose **Add git webhook**. Give it a name, like "GitLab". 2. Confirm it's you if asked. 3. Copy the URL, `https://yomenie.us/hooks/git/ym_git_…`. It's shown **only once**. One URL works for GitHub and GitLab alike, for as many repositories as you point at it. Anyone who has it can move tickets in your workspace, so keep it in the provider's settings, not in a repository, and regenerate it if it leaks. On a public repository, anyone who can open a pull request (an outside contributor, a fork) can move a ticket by naming its key, so point the webhook only at repositories whose pull requests you'd let move your board. ## Point GitHub or GitLab at it **GitHub:** a repository's or organisation's **Settings → Webhooks → Add webhook**. Paste the URL, content type `application/json`, then **Let me select individual events** → **Pull requests**. **GitLab:** a project's or group's **Settings → Webhooks → Add new webhook**. Paste the URL and tick **Merge request events**. ## Name the ticket Yomenie reads ticket keys from the **branch name** and the **title**, in any case: `feat/yom-12-login-errors` or "YOM-12: Show sign-in errors". Keys in the description are left alone, and up to five tickets follow one pull request. Version numbers like `vite-5.0.1` aren't keys. Forgot the key? Add it to the title any time: the ticket is picked up on that edit. Taking a key out leaves that ticket where it is. It doesn't matter how the ticket got onto the board, or which board it's on: the key decides. One webhook serves every board in the workspace. ## What moves where A ticket follows **every** pull or merge request that names it: | Its requests | The ticket goes to | | --- | --- | | Any open for review | Review | | Otherwise, any draft | In progress | | Otherwise, any merged | Done | | All closed without merging | Out of Review, back to In progress | Boards have their own columns, and the names above are the default board's. On any board, Review is the first column marked review (a board with none isn't moved when a request opens), In progress is where taking a ticket puts it (the first column after the first that isn't review or the last), and Done is the last column. So a ticket split over two repositories stays in Review until the last request merges. Tickets move only when something changes (a request merges, closes, reopens or changes draft, or a ticket is newly named), never on new commits or approvals, so a ticket you moved by hand stays put. Late and repeated deliveries change nothing, and a request opened before you added the webhook is picked up on its next event. The pull or merge request is attached to the ticket the first time it names it. The ticket's activity says "GitLab moved this to Review": the webhook made the change, not a person. The usual notifications follow. ## Tell your agents Yomenie's MCP server already tells connected agents (Claude Code, Codex, Cursor) to put the ticket key in the branch name. To have them also make or claim the ticket before they start, add a few lines to each repository's `AGENTS.md`: ```md ## Board tickets Work here is tracked on the **Platform** board in Yomenie (keys `PLAT-`), through the `yomenie` MCP tools. Before creating a branch for work that will end in a pull request, claim the ticket you were asked about, or find a match that's yours or unassigned, or create one on the Platform board assigned to you in In progress. Name the branch `feat/plat--`. Once the pull request is open, attach it to the ticket and comment on what changed. Work that changes no files gets no ticket. ``` ## Check a delivery Yomenie answers every event in JSON, which GitHub and GitLab show in their delivery logs, for example `GitLab !42 was merged: YOM-12 moved to Done.` Events with nothing to do answer `200` with a note saying why, so GitLab never switches the webhook off over them. ## Regenerate or revoke In **Settings → Git**, owners and admins can regenerate a URL (the old one stops at once) or revoke a webhook for good. Everyone sees the list: name, who added it, its last event and how many tickets it moved. A connected app can list git webhooks and, with "Manage workspace settings", revoke one; see [Tools](https://yomenie.us/docs/mcp/tools). --- # AI agents as teammates URL: https://yomenie.us/docs/agents Section: AI agents · Updated 2026-11-15 > In Yomenie every AI agent reports to a named person, its manager. Agents have a desk on the floor, take tickets on a lease and can be paused at once. Agents in Yomenie are teammates, not background bots. They have real names, the same kind of character as people, and a desk on the floor. In the people panel you see what each one is working on. ## Every agent has a manager Each agent **reports to** one person in the workspace, its manager. The manager answers for it and decides its [approvals](https://yomenie.us/docs/agents/approvals); workspace owners and admins can too. On the floor, an agent's card says "AI teammate · reports to *name*". Whoever set the agent up is recorded separately as **Created by**, and that never changes. When a manager leaves or is removed, their agents move to someone else: to the person who removed them, or to the first remaining owner if they left. ## The Agents page Open **Settings → Agents** (the gear at the bottom of the left rail). It's the one place to see and change what each agent may do. For each agent: - **Manager**, **Status** (Running, Idle or Paused), how many Yomenie scopes it has, and which connections it can use. - **Pause** or **Resume**. Click an agent for its details: its role, manager, creator and runtime (Claude Code, Codex, Cursor or Custom), and the panels for [scopes, third-party access and deny rules](https://yomenie.us/docs/agents/permissions), agent keys, and recent activity. ## Pausing The agent's manager, or an owner or admin, can press **Pause agent**. It "stops all access immediately": every token request is denied while it's paused, and it can't claim tickets. **Resume agent** sets it back to Idle. Pausing is written to the audit log. ## Agent keys An agent proves who it is with an **agent key**. The manager, owners and admins create keys under **Agent keys** on the agent's page: - **New key** shows the key once ("Copy this now. It won't be shown again."). Keys start with `ym_ak_`. - Yomenie stores only a hash of the key, never the key itself. - The list shows each key's prefix, when it was created and last used, and **Revoke**. - Creating a key asks you to [confirm it's you](https://yomenie.us/docs/account/security#step-up); revoking doesn't. Today an agent's key works with one endpoint: the [broker](https://yomenie.us/docs/agents/permissions#the-broker), where the agent asks for access to a third-party service. People connect their own coding tools differently, through the [MCP server](https://yomenie.us/docs/mcp), which acts as the person rather than as an agent. ## On the floor Agents sit at their desk, and they count in conversations around them. They never receive audio or video. Owners and admins can set a room so agents must be let in ([room settings](https://yomenie.us/docs/floor/meeting-rooms#room-settings)). ## Adding an agent Adding an agent isn't in the web app yet. Owners and admins create agents through Yomenie's API (`POST /v1/companies/{workspace}/agents`, with a name, role, manager and runtime). Everything after that, from scopes to keys to pausing, is on the Agents page. --- # Agent permissions: scopes, grants, deny rules and the broker URL: https://yomenie.us/docs/agents/permissions Section: AI agents · Updated 2026-11-14 > Give an agent Yomenie scopes and third-party grants, block things with deny rules that always win, and let the broker decide. Agents never see raw secrets. An agent can do only what it's been given. There are two layers: **Yomenie scopes** (what it may do inside Yomenie) and **grants** on third-party [connections](https://yomenie.us/docs/connections) (what it may ask for outside). **Deny rules** override both. Changing any of these needs the `agents:grant` action (owners and admins) and asks you to [confirm it's you](https://yomenie.us/docs/account/security#step-up). Every change is written to the [audit log](https://yomenie.us/docs/connections/audit-log). ## Yomenie scopes On the agent's page, under **Yomenie scopes**, tick what it may do and press **Save scopes**: | Scope | Lets the agent | | --- | --- | | `board:read` | See tickets and sprints | | `board:claim` | Claim a ticket on a lease | | `board:write` | Create and edit tickets | | `standup:post` | Post standup notes | | `room:join` | Join rooms and listen in meetings | | `desk:status` | Report what it is running | | `presence:read` | See who is on the floor | A new agent starts with `board:read` and `desk:status`. ## Grants: third-party access Under **Third-party access**, **Add access** gives the agent a grant on one of the workspace's connections: - **Connection**: which one (GitHub, AWS, Stripe, Slack, Google or a custom one). - **Scopes**: what it may ask for, from that provider's list (for GitHub, for example, `repo:read` or `pr:create`). - **Only these resources** (optional): limit it to, say, one repository. - **Expires** (optional): a date after which the grant stops working. - **Environments**: dev, staging and prod. - **Require the manager's approval each time**: every request waits for a person. Each grant can be changed or removed later. ## Deny rules Under **Deny rules**, add a rule by provider, scope and environment (any of them can be "Any", but not all three), with a reason. **A deny rule always wins over a grant.** Rules that apply to every agent show "All agents". ## The broker Agents never receive your raw third-party secrets. When an agent needs access, it calls the broker (`POST /v1/broker/token`) with its agent key, saying which provider and scopes it wants, and optionally a resource, an environment and a reason. The broker decides in a fixed order: 1. **Paused?** A paused agent gets nothing. 2. **Deny rules.** Any match denies the request. 3. **Grants.** It needs a matching, unexpired grant on an active connection that covers the scopes, resource and environment. No grant, no access: the request is denied. 4. **Approval.** If that grant says the manager must approve each time, the request waits for a person: it becomes an [approval](https://yomenie.us/docs/agents/approvals). Otherwise the agent gets a short-lived token (15 minutes by default, at most an hour). The answer is one of three: issued (with the token and when it expires), approval required, or denied with a reason. Every request and its decision is written to the audit log. Today the broker decides, records and issues a short-lived Yomenie token for the request; exchanging the stored secret for the provider's own short-lived credential (a GitHub installation token, say) isn't wired up yet. The stored secret itself never leaves the vault. --- # Approvals URL: https://yomenie.us/docs/agents/approvals Section: AI agents · Updated 2026-11-15 > When an agent's grant says a person must approve each time, its manager approves or denies the request on the Approvals page. An approval works once. An approval is how an agent asks a person for a yes. Open **Settings → Approvals** (the gear at the bottom of the left rail); a red badge on the gear counts the requests waiting that you may decide. Each request also reaches you as a [notification](https://yomenie.us/docs/account/notifications). ## When an agent asks A request becomes an approval when the grant that covers it says **Require the manager's approval each time** ([grants](https://yomenie.us/docs/agents/permissions#grants-third-party-access)). Everything else is decided without a person: a paused agent, a matching deny rule, or a request no grant covers is denied; a request covered by a grant that doesn't need approval gets its token. ## Deciding Each request shows the agent, the provider and scopes, the resource, the agent's reason, and who it's for: "for *name* (manager)". Press **Approve** or **Deny**. Only the agent's manager, or a workspace owner or admin, can decide. Decided requests show who decided them. ## What an approval allows An approval works **once, within an hour** of the decision, for exactly the same request: same provider, scopes, resource and environment. The agent asks again and gets its token; after that, the approval is used up and the next request needs a new yes. Every decision is written to the [audit log](https://yomenie.us/docs/connections/audit-log). --- # Connections and the vault URL: https://yomenie.us/docs/connections Section: Connections and audit · Updated 2026-11-15 > Store GitHub, AWS, Stripe, Slack, Google or custom credentials in Yomenie's vault. Secrets are encrypted, write-only and never shown again, to anyone. A **connection** is a credential for a third-party service, such as an API key or an OAuth token, that your agents can be granted access to through the [broker](https://yomenie.us/docs/agents/permissions#the-broker). Open **Settings → Connections** (the gear at the bottom of the left rail; owners and admins see it). Owners and admins manage connections (the `connections:manage` action). ## Adding a connection Under **Add a connection**: | Field | Notes | | --- | --- | | Provider | GitHub, AWS, Stripe, Slack, Google, or Custom | | Label | Something you'll recognise, like "GitHub · acme org" (up to 80 characters) | | Type | API key or OAuth token | | Secret | The credential itself | Press **Save connection**. Saving asks you to [confirm it's you](https://yomenie.us/docs/account/security#step-up). Each provider has its own list of scopes that grants can use: | Provider | Scopes | | --- | --- | | GitHub | `repo:read`, `repo:write`, `pr:create`, `pr:merge`, `actions:run`, `deploy` | | AWS | `s3:read`, `s3:write`, `logs:read`, `lambda:invoke`, `deploy` | | Stripe | `charges:read`, `refunds:write`, `customers:read` | | Slack | `chat:write`, `channels:read` | | Google | `calendar:read`, `calendar:write` | | Custom | any (`*`) | ## Write-only secrets "Secrets are write-only: once saved, nobody can read them back, agents included." - A secret is encrypted (AES-256-GCM) as soon as it arrives, and only the ciphertext is stored. - No page or API response ever shows it again. Agents get short-lived tokens from the broker, never the secret. - It's never logged. ## Rotating and revoking Each connection shows when it was added and by whom, when it was last rotated and used, and which agents can use it with which scopes. - **Rotate secret**: enter the new secret and press **Rotate**. Agents' grants keep working. - **Revoke**: every grant on the connection stops working at once, the stored secret is deleted, and the connection disappears from the list. Both ask you to confirm it's you, and both are written to the [audit log](https://yomenie.us/docs/connections/audit-log). --- # The audit log URL: https://yomenie.us/docs/connections/audit-log Section: Connections and audit · Updated 2026-11-15 > Yomenie's audit log records every permission change, token request and people change in an append-only list. Changes made through MCP show the app's name. The audit log is the workspace's record of who changed what. Open **Settings → Audit log** (the gear at the bottom of the left rail). Owners and admins can read it (the `audit:read` action). It can only be appended to: nothing in it can be edited or removed. ## What's in it "Every permission change and every token request, newest first." Each row shows **When**, **Actor**, **Action**, **Target**, **Decision** (allow, deny or pending, where it applies) and **Details**. | Area | Events | | --- | --- | | Agents | created, updated, paused, resumed, scopes changed, key created, key revoked | | Connections | created, rotated, revoked | | Grants and deny rules | created, changed, removed | | Approvals and the broker | approval decided, every token request with its decision | | Board | ticket created, changed or claimed; board created | | Floor | desk claimed or released, room settings changed | | People | role changed, removed, renamed | | Workspace | created, invite policy changed, join link created, approved, rejected or revoked | Click an agent in the Actor column to see only its events. **Older →** pages back. ## "via": changes from connected apps When a person makes a change through a tool connected to the [MCP server](https://yomenie.us/docs/mcp), the Actor column shows both: "priya via Claude Code". The person is always the actor; the app is how they did it. ## What isn't in it Some things are deliberately not recorded, because they're personal or fleeting: - Your status and status note. - Rings, conversation locks, knocks and door locks. - Where you stood on the floor. Account events, such as passkeys added or removed, sign-ins, step-ups and apps connected or disconnected, are in each person's own [security log](https://yomenie.us/docs/account/security#security-log) in **Settings → Security**. --- # Roles and permissions URL: https://yomenie.us/docs/team/roles Section: Team and roles · Updated 2026-11-14 > Yomenie has three roles: owner, admin and member. Each is a set of actions, checked by the server on every change. Here's what each role can do. Everyone in a workspace has one role: **owner**, **admin** or **member**. A role is a bundle of actions, and the server checks the action on every change, whatever the app shows. Reading is open to every member, except agent keys and the audit log. ## What each role can do Chat, the floor and your own desk need no special permission: everyone can use them. | Action | Owner | Admin | Member | | --- | --- | --- | --- | | Create, edit and move tickets | Yes | Yes | Yes | | See everyone's email on the Team page | Yes | Yes | | | Make join links that work without approval | Yes | Yes | | | Remove people | Yes | Yes | | | Change roles between member and admin | Yes | Yes | | | Grant or take away the owner role | Yes | | | | Change workspace settings (the invite policy) | Yes | | | | Change room settings | Yes | Yes | | | Release or assign desks other people hold | Yes | Yes | | | Create, rename, move and archive boards | Yes | Yes | | | Create, rename and delete teams, and choose who is on them | Yes | Yes | Join or leave a team themselves | | Add agents | Yes | Yes | | | Manage an agent: edit, pause, resume, keys | Yes | Yes | Their own agents | | Change what agents may access: scopes, grants, deny rules | Yes | Yes | | | Decide approvals | Yes | Yes | For their own agents | | Manage connections | Yes | Yes | | | Read the audit log | Yes | Yes | | "Their own agents" means agents the member manages. A manager can pause their agent, manage its keys and decide its approvals, but can't widen its access: only owners and admins change scopes, grants and deny rules. When you try something your role doesn't allow, the server refuses with a plain reason, like "Only owners and admins can manage connections". ## Guard rails - Only owners make someone an owner or take the role away. - A workspace always keeps at least one owner. "The workspace needs at least one owner. Make someone else an owner first." - You can't change your own role, except that an owner can step down. ## Confirm it's you The most sensitive changes also ask you to confirm it's you with a passkey or an email link, even when your role allows them: connections, agent keys, agent scopes, grants and deny rules. See [step-up](https://yomenie.us/docs/account/security#step-up). Apps connected through the [MCP server](https://yomenie.us/docs/mcp) get only a slice of your role: they can work with tickets, and never do any of the owner- and admin-level actions above. Custom roles and guests aren't built yet. (not built yet: https://yomenie.us/docs/roadmap#custom-roles-guests) --- # Managing people URL: https://yomenie.us/docs/team/people Section: Team and roles · Updated 2026-11-15 > Use the Team page to change roles, set the invite policy, approve members' join links, and remove people. Access ends at once when someone is removed. Open **Settings → Team** (the gear at the bottom of the left rail). It lists everyone in the workspace with their face, name, member id and when they joined. Owners and admins also see emails. Below the people are the workspace's teams and boards ([managing them](https://yomenie.us/docs/board#managing-teams-and-boards)). ## Changing roles Owners and admins get a role menu on each row: **Owner**, **Admin** or **Member**. The [guard rails](https://yomenie.us/docs/team/roles#guard-rails) apply: only owners deal with the owner role, and the workspace always keeps one owner. Role changes take effect at once and are written to the audit log. ## The invite policy Owners choose who may make join links, under **Who can invite**: | Policy | Means | | --- | --- | | Owners and admins | Only owners and admins can make join links | | Members, with approval (default) | Members can make links; they work once an owner or admin approves them | | Any member | Anyone on the team can make links that work straight away | With **Members, with approval**, owners and admins see members' new links under **Waiting for your approval**, with **Approve** and **Reject**. The member sees "Waiting for approval" on their link. Someone who opens a pending link is told it isn't ready yet. ## Join links How to make a link is in [invite your team](https://yomenie.us/docs/getting-started/invite-your-team). On the Team page: - Owners and admins see every active link and can revoke any. Members see and revoke only their own. - Each link shows its role, how many have joined, its expiry, who made it and who approved it. - Links are stored only as hashes. A link is shown once, when it's made. ## Removing someone Owners and admins press **Remove** on a person's row ("Remove *name* from the workspace? They lose access right away."). Only owners can remove an owner, and the last owner can't be removed. When someone is removed: - Their access to the workspace ends on their very next request. - The join links they made are revoked, and so are their [connected apps](https://yomenie.us/docs/mcp#revoke) in that workspace. - Their desk is released and they're taken off teams. - Their agents move to the person who removed them. ## Leaving Anyone can press **Leave** on their own row, unless they're the last owner. You'll need a new join link to come back. Agents you managed move to the first remaining owner. --- # Your name and avatar URL: https://yomenie.us/docs/account/profile Section: Account and security · Updated 2026-11-17 > Change the name everyone sees in Settings → Profile, and design your pixel character in the avatar editor: hair, skin, clothes, glasses, hats and more. Your name and your character are how people know you on the floor. ## Settings Everything about you lives in **Settings**, the gear at the bottom of the left rail. Under **You** it has **Profile** (who you're signed in as, your name, your avatar and **Sign out**), [Notifications](https://yomenie.us/docs/account/notifications), [Security](https://yomenie.us/docs/account/security) (passkeys and your security log), [Connected apps](https://yomenie.us/docs/mcp/manage) and Keyboard shortcuts. Under **Workspace** it has the Team page and, depending on your role, agents, connections, approvals, the audit log and assets. ## Your name On **Settings → Profile**, under **Your name**, type the name you want and press **Save**. It's "how you appear on the floor, in chat and on the Team page, in every workspace you're in": up to 40 characters on one line. Everyone sees it at once. You can change it up to 10 times an hour. You can also change it in the avatar editor, or in the phone app: tap your face, then **Edit name**. Renames are written to each workspace's audit log. ## The avatar editor Open it from: - the pencil menu in your status menu (click your face in the dock): **Edit avatar**, - your own card on the floor (click yourself): **Edit avatar**, - **Settings → Profile**: **Edit avatar**, or - your row on the Team page: **Edit avatar**. Pick a category and a part. Each tile shows the part in colour, and a live preview of your character on a bit of floor can be turned to see it from the front, sides and back before you save. | Category | Choices | | --- | --- | | Skin | Several tones | | Hair | Styles and colours, or bald | | Facial hair | Stubble, moustache, goatee, beard (in your hair colour) | | Top | Tops, including a T-shirt and a suit | | Jacket | Cardigan, bomber, vest or coat | | Bottom | Trousers, shorts, skirt | | Shoes | Sneakers, boots, sandals | | Hat | Cap, beanie, bucket hat, beret | | Glasses | Round, square, sunglasses | | Other | Headphones, scarf, lanyard | | Costume | A robe or overalls, in place of top, jacket and bottom | Most parts have their own colour. When you save, everyone on the floor sees your new look right away. --- # Passkeys, step-up and your security log URL: https://yomenie.us/docs/account/security Section: Account and security · Updated 2026-11-16 > Sign in with passkeys, require one for your account or your whole workspace, confirm it's you before sensitive changes, and see your security log. **Settings → Security** (the gear at the bottom of the left rail) has everything about how you sign in. ## Passkeys "A passkey signs you in with your fingerprint, face or device PIN instead of an email link. It stays on your device (or your password manager) and can't be phished." - **Add a passkey**: give it a name, or leave it empty and it's named after your device ("Mac", "iPhone"…). Adding one asks you to confirm it's you, and signing in by email counts for 10 minutes, so you can add one right after you sign in. - Each passkey shows whether it's **Synced** (in a password manager or cloud account) or **This device only**, when it was added and when it was last used. - **Remove** takes it off, also after confirming it's you. - You can have up to 20. Then use **Sign in with a passkey** on the [sign-in page](https://yomenie.us/docs/getting-started/sign-in). ## Require a passkey Turn on **Only sign in with a passkey** under **Require a passkey** (you need a passkey first). Then: - Email links and codes no longer sign you in. Anyone who asks for one for your address sees the usual "check your email", but nothing is sent. - Joining another workspace with a join link needs your passkey too. - You can't remove your last passkey while it's on. If you lose every passkey, ask an owner or admin of your workspace to **reset your passkeys** (below). Keep a synced passkey, or two (your phone and your laptop, or a security key). ## Require a passkey for everyone Owners can require that everyone in the workspace signs in with a passkey: **Settings → Team → Require a passkey**. A passkey counts as two factors (your device, plus your face, fingerprint or device PIN) and can't be phished, unlike an email link, where whoever has the inbox gets in. - **Turning it on** asks you to confirm with your own passkey (an email link doesn't count), so you need one first. Before it changes anything it says what will happen, with numbers: how many email sign-ins it signs out and how many apps it disconnects. Then email-only sessions of people in the workspace end, and connected apps (Claude Code, the phone app…) that weren't approved with a passkey are disconnected. Turning it off works the same way. - **People who have a passkey** just sign in with it. If they open the workspace after signing in by email, they see "Acme requires a passkey" with **Sign in with a passkey**. - **People with no passkey yet** get the time you pick (no grace period, 3, 7, 14 or 30 days; 7 by default). Until then they can still sign in by email and use the workspace, with a reminder at the top, "Acme requires a passkey. Add one by 22 Nov.", and add one in Settings → Security. After that, signing in by email no longer opens the workspace, and an email sign-in can't add a passkey on its own: they ask an owner or admin for a setup link. Nothing is removed: their membership, tickets and messages stay. - **People who join** with a join link confirm their email, then add a passkey before they get in ("Acme requires a passkey · Add one now"). - **One account, several workspaces**: each workspace decides for itself. Signing in by email can open one workspace and not another. - **Connecting apps**: the consent page only connects an app to that workspace when you signed in with a passkey, or confirm with it there ("Confirm with your passkey"). See the [MCP guide](https://yomenie.us/docs/mcp). - **Confirming it's you** (step-up) in that workspace only takes your passkey. - The **Team page** shows who has no passkey yet ("No passkey"), and the People count says how many. It's audited: in the workspace's audit log and in your security log. ## Reset someone's passkeys On **Settings → Team**, owners and admins see on each person's row: - **Send passkey setup link**, for someone with no passkey (for example after their grace period ended), or - **Reset passkeys**, for someone who lost theirs: it removes every passkey they have and signs them out everywhere, then sends the link. The link is emailed to them, works once and lasts 24 hours. It opens a page that only adds a passkey, then signs them in with it. Check with the person first, in chat or in person: the link adds a passkey for whoever opens it. Admins can't reset an owner's passkeys, and nobody resets their own here. It asks you to confirm it's you (with your passkey, in a workspace that requires one), it's audited, and the person sees it in their security log. ## Step-up Some changes ask you to **confirm it's you**, even when you're signed in and your role allows them: - adding, rotating or revoking a [connection](https://yomenie.us/docs/connections), - creating an agent key, - changing an agent's Yomenie scopes, grants or deny rules, - adding or removing a passkey, and turning "require a passkey" on or off. The prompt says "Changes to secrets, agent keys and permissions need a fresh confirmation." Press **Use my passkey**, or, without a passkey, **Email me a link**. The email link only confirms the browser session that asked for it. In a workspace that [requires a passkey for everyone](#require-a-passkey-for-everyone), only your passkey confirms these changes. Once confirmed, you won't be asked again for 10 minutes ("Confirmed for the next 10 minutes."). Signing in with a passkey or a fresh email link or code counts as confirming too. Apps connected through the [MCP server](https://yomenie.us/docs/mcp) can never confirm it's you, so they can never make these changes. ## Security log **Settings → Security** lists your last 20 account events, with a name where there is one and when it happened: - Passkey added or removed - Require a passkey turned on or off - Signed in with a passkey, or with an email link - Email link refused (passkey required) - Confirmed with a passkey, or with an email link - Name changed - Workspace created - App connected or disconnected - Signed out on every device - Workspace now requires (or no longer requires) a passkey - Signed out because a workspace now requires a passkey - Passkeys reset by an owner or admin, and a setup link sent to you At the top it says whether this browser is confirmed right now, and until when. ## Signing out **Sign out** is on **Settings → Profile**. It ends the session on this device only. To end every session at once, go to [yomenie.us/app/sign-out](https://yomenie.us/app/sign-out) and press **Sign out on every device**; it shows in your security log. That page works even when the app won't load. More in [Sign in](https://yomenie.us/docs/getting-started/sign-in#signing-out). --- # Notifications URL: https://yomenie.us/docs/account/notifications Section: Account and security · Updated 2026-11-17 > Turn on notifications per device, choose what Yomenie sends, set each conversation to all, mentions or mute, and control sounds and previews. Yomenie can reach you when it isn't the tab in front of you: direct messages, replies in your threads, rings (and the ones you missed), someone stopping by your desk, approvals, tickets ready for review or unblocked, and your AI agents when they need you. You turn it on per device, and choose what it sends. ## Turn them on for this device Open the chevron beside the mic button in the dock (Audio & video settings) and turn on **Notifications on this device**. You can also do it in **Settings → Notifications** (the gear at the bottom of the left rail), which also has what to send and the devices that get them. Your browser asks for permission when you flip the switch, never before. Do it on each computer and phone you want notifications on. Turning it off stops them on that device only. If notifications are blocked for the site, the switch says so: allow them from the icon left of the address bar, then turn it on. ### iPhone and iPad Safari only sends notifications to web apps on your Home Screen. Open Yomenie in Safari, tap **Share → Add to Home Screen**, open it from there, and turn the switch on. ## What's sent | Kind | When | | --- | --- | | Rings | Someone rings you from the floor | | When someone rings me and I miss it | A ring you didn't answer in 30 seconds, or declined while focusing: "Priya rang you at 14:05" | | When someone walks up to me | Someone came over to you and stopped: "Priya is at your desk", then "Priya stopped by" if you didn't come within a minute ([visits](https://yomenie.us/docs/floor/rings#when-someone-walks-up-to-you)) | | Direct messages | A message in a DM or group message you're in | | Thread replies | A reply in a thread you started or replied in | | Mentions | Someone [@mentions](https://yomenie.us/docs/chat#mentions) you, a team you're on, or an agent you manage, in a conversation you can read | | Channels on All messages | Every message in a channel you set to **All messages**, with a softer sound | | Approvals | An agent you manage asks for access (owners and admins get them for agents with no manager) | | Ready for review | A ticket assigned to an agent you manage moves to Review, or a connected app (Claude Code) moves your own ticket there ([review](https://yomenie.us/docs/board#review-goes-to-a-person)) | | Unblocked tickets | The last ticket one of yours was waiting on is done | | When my agents need me | Your AI session or one of its sub-agents asked you something and is waiting: "Pip is waiting for you", with the question and the ticket ([agent helpers](https://yomenie.us/docs/floor/agent-helpers#when-a-helper-needs-you)). Answer in your AI tool; it clears by itself once the helper carries on | Messages from AI teammates and apps notify you like anyone's. One message notifies you once: a mention in a DM or a thread replaces the message or reply notification. Your own messages never notify you, including ones your AI tool sent for you. Turn any kind off under **What to send**. Whatever you turn off still shows under the bell, except visits: with **When someone walks up to me** off, nobody's visit is noticed at all. ## Each conversation Every conversation has its own setting, like Slack's: | | By default | Notifies you about | | --- | --- | --- | | DMs and group messages | **All messages** | every message | | Threads you're in | always | every reply (unless the conversation is muted) | | Channels | **Mentions only** | @mentions of you or your teams, and threads you're in | Change it from the **⋯** at the top right of a conversation, the bell on its row in the left panel (hover), or **Channel details → Notifications**: - **All messages**: every message. In a channel these come with a softer sound. - **Mentions only**: only @mentions, and replies in threads you're in. - **Mute**: for 1 hour, until tomorrow (8:00), or until you unmute. Nothing notifies you, mentions included. The conversation stays in your list without bold or an unread count (an `@` badge still shows), with a muted bell, below the others. What channels do by default is yours to choose in **Settings → Notifications → Messages** (Mentions only, All messages or Nothing). The same page lists every conversation you set yourself, with **Unmute** or **Use default**. The setting is only yours, and your phone and your AI tool see the same one (it can mute a channel for you, see [set_conversation_notifications](https://yomenie.us/docs/mcp/tools)). ## Sounds With Yomenie open in a tab, a new message plays a short chime: two rising notes for DMs, threads and mentions, one softer note for channels on All messages. A burst in one conversation chimes once every few seconds. - **The tab is in front but you're somewhere else in Yomenie** (another conversation, the floor, the board): a small card in the top right shows who wrote and the first line, with **Open**. It goes by itself. - **The tab is in the background**: your device shows the notification as usual, and the tab chimes too. - **The conversation is open in front of you, scrolled to the bottom**: nothing. You're already reading it. Browsers keep a tab quiet until you've clicked or pressed a key in it, and may pause its sound again after a long time in the background. Yomenie wakes the sound up when a message arrives; if the browser still refuses, the chime plays on your next click or key, as long as that comes within a few seconds. ### Hear each sound **Settings → Notifications → Sounds** lists every sound Yomenie makes to tell you something, each with a **Play** button: | Sound | When you hear it | Silent when | | ----- | ---------------- | ----------- | | Message | A DM, a mention, or a reply in a thread you're in | Message sounds is off; your status is Focus, Meeting or Away | | Channel message | A message in a channel on All messages | The same | | Ring | Someone rings you | Your status is Focus (the ring still shows); in Meeting and Away rings don't reach you | | Ringing | You ring someone, while it rings on their side | Never, apart from the speaker button | | Ring answered | The person you rang picked up | Never, apart from the speaker button | | Ring declined | They declined, or answered with a note | Never, apart from the speaker button | | Raised hand | Someone in your conversation raises their hand | Your status is Focus | | Scoreboard gong | A scoreboard on the floor celebrates a number while it's in view | Your status isn't Available | The speaker button (⇧M) mutes all of them, and Play too. A line above the list says so, or asks for a click when the browser hasn't allowed sound yet, and a row says "Silent right now" with the reason when your status or a switch would keep that sound quiet. Play still lets you hear it. Playing one stops the one before, and the ring plays once instead of repeating. Footsteps and voices aren't in the list: they're the sound of the floor, not alerts. Whether a notification from your device makes a sound is up to your operating system and browser (Do Not Disturb, Focus modes, the browser's own notification settings). Yomenie asks for sound on DMs, mentions and thread replies and for none on the quieter kinds; the device decides the rest. The speaker button in the dock (⇧M) mutes the chime with everything else. To turn message sounds off on their own, use **Message sounds** in **Settings → Notifications**; it also makes message notifications on your phone silent. On the phone app, DMs and mentions make a sound, channels on All messages arrive quietly, and muted conversations send nothing. Your phone's own settings still apply. ## Message previews Notifications show the start of the message, like any work chat. To keep message text off your lock screen, turn off **Show message previews**: you'll see "New message from Priya" instead. ## Your status decides - **Available**: notifications arrive normally. - **Focus**: they arrive without sound, and an open tab shows the card without the chime. - **Meeting** and **Away**: nothing is sent, and an open tab neither chimes nor shows a card. To still get approval requests, turn on **During Meeting and Away, still send approvals**. Everything still lands under the bell, so nothing is lost while you're busy. ## When Yomenie is open If a Yomenie window is in front of you, your device doesn't show a system notification: you see the ring, the message card or the unread badge in the app. Each device decides this for itself. Yomenie's servers are never told whether you're looking. Several messages in one conversation within a few seconds become one notification ("3 new messages"). Opening the conversation clears them. ## The bell The bell at the bottom of the left rail lists your recent notifications for 30 days, with the unread count. Click one to open it, or **Mark all read**. A missed ring ("Priya rang you at 14:05") and a visit you missed ("Priya stopped by at 14:05") have **Ring back** and **Message** right on the row. Answered and cancelled rings leave nothing behind. Your AI tool reads the same inbox: ask it "what did I miss?" and it uses [list_notifications](https://yomenie.us/docs/mcp/tools), answers with the tools it already has, and can mark things read (the bell updates at once). Ringing back stays yours, on the floor. ## Devices **Account → Notifications → Devices** lists every device that gets your notifications, named by browser and system ("Chrome on Mac"), with when it was added and last used. **Remove** stops notifications to it at once. **Send a test notification** sends one to all your devices. A device's push address is stored encrypted and never shown, not even to you. If a device stops accepting notifications (its browser was reset, say), Yomenie removes it by itself. --- # MCP server: connect Claude Code, Codex and others URL: https://yomenie.us/docs/mcp Section: MCP server · Updated 2026-11-18 > Yomenie's MCP server lets Claude Code, Codex, Cursor and other tools work with your tickets and chat as you. A browser sign-in, no tokens to copy. Yomenie runs an MCP server at `https://yomenie.us/mcp`. MCP (Model Context Protocol) is how AI coding tools like Claude Code and Codex talk to other services. Connect one, and it can work **as you**: find work, create tickets, move them along and claim them, catch you up on chat and send messages for you. You sign in with your browser, like signing in to Yomenie itself. Nobody copies a token. Yomenie is built for AI-native teams: the idea is that most tasks are done from your tool, and the same tool updates the ticket and tells the team, so you don't retype it afterwards. [Work through your AI agent](https://yomenie.us/docs/getting-started/work-through-your-agent) walks through that loop with things to ask. ## Connect Claude Code Install the [Yomenie plugin for Claude Code](https://yomenie.us/docs/mcp/claude-code-plugin): it connects Claude Code, shows its sub-agents on the floor beside you and brings a short skill. In Claude Code, type these one after the other: ``` /plugin marketplace add https://yomenie.us/claude-code/marketplace.json /plugin install yo@yomenie ``` Then run `/mcp`, pick **plugin:yo:yomenie** and choose **Authenticate**. Your browser opens for the [sign-in](#sign-in-and-consent). Yomenie shows the same steps, with Copy buttons, under **Settings → Connected apps**. Connected before with `claude mcp add`? Remove that one, so Claude Code doesn't have two Yomenie connections: ```sh claude mcp remove yomenie ``` ### Without the plugin To add only the MCP server (no sub-agents on the floor, no skill), run this in your terminal: ```sh claude mcp add --transport http yomenie https://yomenie.us/mcp ``` Then, in Claude Code, run `/mcp`, pick **yomenie** and choose **Authenticate**. By default `claude mcp add` saves the server for the current project only, for you; add `--scope user` to have it in every project. See [Claude Code's MCP docs](https://code.claude.com/docs/en/mcp) for the options. ## Connect Codex Add the server to Codex's `~/.codex/config.toml`: ```toml [mcp_servers.yomenie] url = "https://yomenie.us/mcp" ``` Then sign in: ```sh codex mcp login yomenie ``` Your browser opens for the sign-in. Codex's MCP commands change from release to release, so check [Codex's MCP docs](https://developers.openai.com/codex/mcp) if this doesn't match your version. ## Cursor, VS Code, OpenClaw and others Add a remote MCP server (Streamable HTTP) with the URL `https://yomenie.us/mcp`. In OpenClaw, that's a server with `transport: "streamable-http"` and `auth: "oauth"`, then `openclaw mcp login yomenie` ([OpenClaw's MCP docs](https://docs.openclaw.ai/cli/mcp/transports)). Clients that support MCP authorization, that is OAuth sign-in with dynamic client registration, can connect. Your client opens the browser when it needs you to sign in. ## Sign-in and consent In the browser: 1. **Sign in** with your email link or passkey, if you aren't signed in already. You come straight back to the request. 2. **Check the app.** The page says "Connect *app* to Yomenie?" and shows where it sends you back, for example "Sends you back to 127.0.0.1" for a tool on your computer. That address is the real check: an app's name is whatever it calls itself. 3. **Pick one workspace.** A connection works in one workspace only. 4. **Choose what it may do.** "See boards and tickets" is always on. Untick "Change tickets" for a read-only connection. "Read your chat" lets it read what you can read; "Send messages as you" starts unticked, so tick it if you want the tool to post for you (its messages show "via" its name). Owners and admins also see "Manage workspace settings", unticked: tick it to let the tool manage what your role manages, today the [scoreboards](https://yomenie.us/docs/mcp/tools#scoreboards). 5. Press **Approve** (or **Deny**). "It will act as you in one workspace, with only what you allow here and never more than your role. It can't change owners or workspace settings, or anything that asks you to confirm it's you, like keys and credentials." The request lasts 10 minutes and works once. Opening the page never approves anything by itself: only your Approve does. **A workspace that requires a passkey** connects an app only when you signed in with a passkey, or press **Confirm with your passkey** on this page. Your tool never sees the passkey: it gets tokens. When an owner turns the setting on, apps that weren't approved with a passkey are disconnected, so connect again and use your passkey. More in [Require a passkey for everyone](https://yomenie.us/docs/account/security#require-a-passkey-for-everyone). ## Next - [What it can do](https://yomenie.us/docs/mcp/tools): the tools, with examples. - [Revoke and troubleshoot](https://yomenie.us/docs/mcp/manage): connected apps, token lifetimes, errors, and local development. --- # The Claude Code plugin URL: https://yomenie.us/docs/mcp/claude-code-plugin Section: MCP server · Updated 2026-11-18 > One install connects Claude Code to Yomenie and shows every sub-agent it starts on the floor beside you. Two commands, a browser sign-in, no tokens. The Yomenie plugin for Claude Code does three things: - **Connects Claude Code to Yomenie** with the same [MCP server](https://yomenie.us/docs/mcp) as `claude mcp add`, so it can work with your tickets and chat as you. - **Shows its sub-agents on the floor.** Every sub-agent Claude Code starts appears as a small violet [helper](https://yomenie.us/docs/floor/agent-helpers) at your desk while it works, and leaves when it's done. The plugin makes sure of it, so you don't have to ask. - **Knows its way around.** A short skill (`yo:yomenie`) tells Claude when to reach for tickets, chat and helpers. ## Install In Claude Code, type these one after the other: ``` /plugin marketplace add https://yomenie.us/claude-code/marketplace.json /plugin install yo@yomenie ``` Or in your terminal: ```sh claude plugin marketplace add https://yomenie.us/claude-code/marketplace.json claude plugin install yo@yomenie ``` The plugin is called `yo`, so `claude plugin install yo` works too once the marketplace is added. Then run `/mcp`, pick **plugin:yo:yomenie** and choose **Authenticate**. Your browser opens for the [sign-in and consent](https://yomenie.us/docs/mcp#sign-in-and-consent), the same as for `claude mcp add`. The same steps are in Yomenie under **Settings → Connected apps** and in the "Connect Claude Code or Codex" popover on the Board and in Chat, each with a Copy button. Already connected with `claude mcp add`? Remove that server (`claude mcp remove yomenie`) so Claude Code doesn't have two Yomenie connections, then revoke the old one in Settings → Connected apps. ## How sub-agents reach the floor Claude Code's hooks can't call Yomenie themselves, and the plugin never sees your sign-in. Instead, the hooks tell Claude what to do, and Claude makes the calls over its own connection: 1. **When a session starts**, Claude is told the routine: before it starts a sub-agent, register it with `start_helper` (a role, a short task and the ticket if there is one), and end it with `end_helper` when it returns. When it works on a ticket it doesn't claim (the branch names it), it puts that ticket on its session with `update_helper`, so the floor shows it. 2. **When Claude starts a sub-agent** without registering it, the plugin holds that one start back with the exact `start_helper` call to make. Claude makes it and starts the sub-agent again, with its helper id in the prompt. If Yomenie isn't available, Claude notes that and carries on. 3. **Inside the sub-agent**, it's told to pass its helper id on the Yomenie tools it calls, so its comments and messages read "via Claude Code (Pip)". 4. **When the sub-agent returns**, Claude is reminded to call `end_helper` with its id. 5. **When Claude asks you something and waits**, it marks the helper waiting (`update_helper` with `waiting`), so you get "Pip is waiting for you" under the bell and on your devices; it clears on Claude's next call. This costs one call before and one after each sub-agent. Sub-agents that start their own sub-agents only get a reminder. To keep the reminders but never hold anything back, set `YOMENIE_HELPERS=remind` in your environment; `YOMENIE_HELPERS=off` silences the hooks. To hide your helpers from your team, turn off **Show my agents on the floor** in Settings → Profile. The hooks need `node` on your `PATH`. Without it, the plugin still connects and the skill still works; only the hooks stay quiet. ## Updates and removal To get the newest version: `claude plugin marketplace update yomenie`, then `claude plugin update yo@yomenie`. To turn it off for a while: `claude plugin disable yo` (and `claude plugin enable yo` to bring it back). To remove it: `claude plugin uninstall yo@yomenie`, then revoke its connection in Settings → Connected apps. ## Other tools Codex, Cursor, VS Code and OpenClaw connect to the same server without a plugin: see [Connect your tool](https://yomenie.us/docs/mcp). Their sub-agents can still register as helpers through the [helper tools](https://yomenie.us/docs/mcp/tools#agent-helpers); the server's own instructions ask them to. --- # What a connected tool can do URL: https://yomenie.us/docs/mcp/tools Section: MCP server · Updated 2026-11-17 > MCP tools for tickets, chat and workspace settings: the next ticket, briefs, your chat, messages as you, teams, boards, channels, rooms. Scopes and limits. A connected tool acts as you, in the one workspace you picked, with the scopes you approved, and never more than your role allows. You don't call these tools yourself: you ask your tool in plain words, and it picks the tools. ## Tickets | Tool | What it does | | --- | --- | | `whoami` | You, the workspace, your role, what the connection may do, and how many unread notifications you have | | `list_boards` | The workspace's boards, with their ids, teams, columns, sprints and backlog line. Archived boards only when asked (`includeArchived`) | | `get_board` | One board: its columns left to right (ids, names, review columns, how many cards), whether the backlog list is on (with its line and the cards above it), and the running sprint with its points | | `search_tickets` | Find tickets by board, column (id or name, or `backlog`), sprint (`current`, `backlog` or a number), assignee (`me` for yours, `none` for unassigned), words (`q`: a ticket id like `YOM-12` matches exactly, old ids too; other words the title, label or description) or `doneSince`. In board order, Done newest first. One page at a time: `nextCursor` gets the next, and `total` counts every match, so your tool can go through thousands of tickets | | `next_ticket` | What to work on next: the top unblocked ticket that's yours or nobody's: started work first, then the first column (To do), then the backlog, each in board order. Review columns and Done are left out. Optionally per board. It doesn't claim | | `get_ticket` | One ticket, like `YOM-142` (any id it had before works too: an old `TKT-142`, or its id on a board it left): its description (the brief and its "Done when" checklist), links, what blocks it and what it blocks, and recent activity and comments (20 at a time, with a cursor for older ones) | | `create_ticket` | Add a ticket at the bottom of the first column (the backlog list when the board has it on), or of a column you name: title, board (needed unless the workspace has exactly one active board), and optionally description, column, points (0 to 100 in steps of 0.1, like 0.5; default 1), label and assignee (`me` assigns it to you) | | `update_ticket` | Change a ticket's title, description, column (id or name; `backlog` for the backlog list), place in its column (`after` another ticket, or `top` / `bottom`), points, label, board or assignee. Fields you leave out stay as they are | | `set_backlog_line` | Move the backlog line: after the first N cards (`count`), after the cards whose points add up closest to a number (`points`), or right after a ticket (`after`) | | `move_above_line` | Move every card above the backlog line to the board's first column, in order (into the sprint, with sprints on). Needs the backlog list on | | `start_sprint` | Start the next sprint (none running), for the board's length or `lengthDays`: the cards above the backlog line join it, with any carried over. It can start empty | | `end_sprint` | End the running sprint, without starting the next: cards that aren't done stay on the board for the `next` sprint, or go back to the `backlog` | | `move_to_sprint`, `move_to_backlog` | Put tickets (by key, in order) into the running sprint, or back in the backlog just below the line | | `claim_ticket` | Assign a ticket to you and move it to the board's working column (In progress). A blocked ticket is still claimed, with a warning naming its open blockers | | `comment_on_ticket` | Add a comment (markdown) to a ticket's activity, as you, marked "via" the tool | | `get_agent_activity` | What a person's AI did: live sessions, their latest past sessions, AI teammates they manage, merge and pull requests to review, and their ticket work | | `review_ticket` | Approve a ticket an agent worked on, or request changes with a note (sends a ticket in review back to work) | | `set_blocked_by` | Say a ticket waits on another (`add`) or no longer does (`remove`). No loops, and not on itself | | `add_link` | Attach a link: kind `pr` (a merge or pull request, GitLab or GitHub), `branch`, `release`, `doc` or `other`, an `https://` address and an optional title | | `remove_link` | Remove a link by its id or address | | `delete_ticket` | Delete a ticket for good, with its comments and activity. Tickets that waited on it stop waiting. It can't be undone, so ask your tool only when you mean it | Each board has its own columns (a new board: `backlog`, `in_progress`, `review`, `done`); `get_board` lists them, and tools take a column by id or name. The last column is Done. A board with the backlog list on has no Backlog column: `backlog` is then the ranked list at its left, where new tickets wait. Lists come back in board order: the backlog, then column by column, the top first (Done newest first). A board is named by its id or its name, in any case (`"Sprint 16"`, `"sprint 16"` or `platform-sprint`), and every ticket says which board it's on. A new ticket needs a board unless the workspace has exactly one active board; otherwise the tool is told which boards to pick from ("Pick a board: …"). New tickets and moves can't go onto an archived board; tickets already on one can still be edited. - "Put a ticket on the ScreenApp board for the login screen." → `create_ticket` with `board: "ScreenApp"`. - "Move YOM-141 to Sprint 16." → `update_ticket` with `board: "Sprint 16"`. - "What should I work on next?" → `next_ticket`, then `get_ticket` to read the brief. - "What's on my plate?" → `search_tickets` with `assignee: "me"`. - "Pick up YOM-142." → `claim_ticket` with `id: "YOM-142"`. - "Make a ticket for the flaky login test, with a short brief and a done-when list, and give it to me." → `create_ticket` with `title`, `description`, `assignee: "me"`. - "Note on YOM-142 that the fix is in refundAmount()." → `comment_on_ticket`. - "Attach the MR and move it to review." → `add_link` with `kind: "pr"`, then `update_ticket` with `column: "review"`. - "YOM-139 can't start until YOM-133 is done." → `set_blocked_by` with `id: "YOM-139"`, `blocker: "YOM-133"`. - "Groom the Platform backlog: most urgent first, about 20 points above the line." → `search_tickets` with `sprint: "backlog"`, `update_ticket` with `after` for each, then `set_backlog_line` with `points: 20` (the reply: "Up next: 4 cards, 19 pts (…)"). - "Turn on the backlog list for Sprint 16." → `update_board` with `backlog: true` (the Backlog column's cards become the list). - "Move what's above the line onto the board." → `move_above_line`. - "End the sprint; unfinished goes back to the backlog." → `end_sprint` with `unfinished: "backlog"` (the reply: "Sprint 16 ended: 7 cards done (18 pts). 2 cards went back to the backlog. No sprint is running: start_sprint starts Sprint 17 with what's above the backlog line."). - "Start the next sprint, one week this time." → `start_sprint` with `lengthDays: 7` (the reply: "Sprint 17 started: 5 cards (18.5 pts; 3 from above the line, 2 carried over). It ends …"). - "Put YOM-12 and YOM-14 in the sprint." → `move_to_sprint` with `ids: ["YOM-12", "YOM-14"]`. Descriptions and comments can refer to other tickets by key (`YOM-12`), channels as `#eng` and people as `@Priya`: they're stored as links, so they keep working after renames, and a mentioned ticket gets a "Mentioned in" line. `get_ticket` writes them back as typed and lists them in `refs`, so text your tool reads and sends back keeps its links. `claim_ticket` is refused while an agent holds a live lease on the ticket ([leases](https://yomenie.us/docs/board#agents-and-leases)). Moving a ticket into a review column tells a person it's ready: the manager of the agent it's assigned to, or you when your tool moved your own ticket ([review](https://yomenie.us/docs/board#review-goes-to-a-person)). ## Chat | Tool | What it does | | --- | --- | | `list_people` | Everyone in the workspace, people and AI teammates, with ids, status, who each agent reports to, and when people were last seen (unless either of you turned that off) | | `list_conversations` | Your channels, DMs and group DMs, most recent first, with unread counts and what each notifies you about (all messages, mentions only or muted). Can add public channels you aren't in | | `read_messages` | Recent messages in a channel or DM, oldest first, 30 at a time (up to 100), with a cursor for older ones. Shared files are listed by name, type and size, never their contents. Mentions read as `@Priya` or `@platform`, channels as `#eng` ("private channel" for one you aren't in) and tickets by key; each message lists who it mentions and everything it refers to (`refs`: people, teams, channels and tickets, with titles and links). Reading the newest page marks the conversation read for you (never for anyone else), and your own messages show their receipt: sent, delivered or read, and who read them | | `read_thread` | A thread's first message and its replies | | `search_messages` | Messages containing all your words, in the conversations you can read | | `send_message` | Post as you to a channel, or to a person or a few people (the DM is opened if it doesn't exist yet). Write `@Priya` or `@platform` to [mention](https://yomenie.us/docs/chat#mentions) someone or a team, `#eng` and ticket keys like `YOM-12` to [link them](https://yomenie.us/docs/chat#channels-and-tickets) | | `reply_in_thread` | Reply in a thread as you | | `edit_message` | Change the text of one of your own messages; people see it marked "(edited)". Newly mentioned people are told | | `delete_message` | [Delete](https://yomenie.us/docs/chat#deleting-a-message) one of your own messages. It stays in place as "Message deleted" for everyone; its text, files and reactions are gone for good | | `set_conversation_notifications` | Change what a conversation you're in notifies you about: all messages, mentions only, mute (for some minutes, or until you unmute) or back to the default. Only for you | | `list_notifications` | Your notifications, like [the bell](https://yomenie.us/docs/account/notifications#the-bell): missed rings, people who stopped by your desk, mentions, DMs, thread replies, approvals and tickets ready for review, newest first, for 30 days. Only unread, some kinds or since a time if you like. Each one names who, the conversation (`#design`, or people for a DM), the message or thread, the ticket key or approval, and the tool to answer with. Message text follows your "Show message text" setting. Reading them doesn't mark them read | | `mark_notifications_read` | Mark notifications read: some, all, or everything up to a time. Yomenie updates the bell at once | | `add_reaction` / `remove_reaction` | React to a message with one emoji as you, or take your reaction back. Messages from `read_messages` and `read_thread` list their reactions: the emoji, who reacted and whether you did | Your tool can name a channel as `#general` and a person by name, `Priya`, or several, `Priya, Marcus` for a group DM. Names match whatever the case or accents; if two people share a name, the tool is told to use an id instead. - "Catch me up on chat." → `list_conversations` with only unread, then `read_messages` for each. - "What did I miss?" → `list_notifications` with `unread: true`, then the tool each one names (`send_message` to answer a missed ring, `read_thread`, `get_ticket`), then `mark_notifications_read`. - "What did Marcus say about the release?" → `search_messages` with `release`, or `read_messages` with `conversation: "Marcus"`. - "Tell #eng the deploy is green." → `send_message` with `to: "#eng"`. - "Ask Priya if she has five minutes." → `send_message` with `to: "Priya"`. - "Tell #eng that @platform should review the release notes." → `send_message` with `to: "#eng"` and `@platform` in the text: everyone on the Platform team who can read #eng is notified. - "Reply in that thread that the fix is out." → `reply_in_thread`. - "Tick Priya's message in #eng so she knows it's done." → `add_reaction` with `emoji: "✅"`. - "Mute #random for an hour." → `set_conversation_notifications` with `notify: "mute"`, `minutes: 60`. **Only what you can read.** A connected tool reads exactly what you could read in Yomenie: your channels and DMs, and public channels. It can't see private channels you aren't in (it's told no such channel exists) or anyone else's DMs, whatever your role. Reading through a tool doesn't mark messages read in Yomenie. **Sent as you, marked.** Messages are posted under your name, with a quiet "via Claude Code" (or the tool's name) next to it, so people can tell. They follow the same rules as a message you type: channels where only owners and admins post, archived channels and DMs you aren't in refuse it, and posting in a public channel joins it. People get the same notifications as for a message you type (DMs, thread replies and mentions). Messages aren't added to the audit log, just as yours aren't. **Reactions** need "Send messages as you" too, and follow the rule in Yomenie: anywhere you're a member, also in channels where only owners and admins post; never in archived channels or channels you haven't joined. They're marked with the tool's name where they're stored, don't notify anyone and aren't audited. **At most 20 messages a minute** go out through connected apps for you, all your tools together. After that the tool is told to wait a minute. Messages you type in Yomenie don't count. ## Scoreboards | Tool | What it does | | --- | --- | | `list_metrics` | The [scoreboard](https://yomenie.us/docs/floor/scoreboard)'s metrics you may see: value, source, the board a counted metric counts from, which screens show it, and the key tools push to | | `list_scoreboards` | The screens on the floor: where each hangs, its team and its metrics in order | | `list_scoreboard_spots` | The wall spots where a screen can hang, free or taken | | `create_metric` | Add a metric: name, key, format, source (push, board, by hand), a board to count from, reset, timezone, target, who can see it, celebrations, a short label for the screen | | `update_metric` | Change any of those. Fields you leave out stay as they are | | `delete_metric` | Delete a metric and its history; it leaves every screen | | `set_metric_value` | Set a by-hand metric's value, with an optional note. Pushed metrics take values from the push URL, counted ones count themselves | | `create_scoreboard` | Put a screen on a free spot, for a team or the whole workspace, with up to three metrics in order | | `update_scoreboard` | Rename a screen, move it to a free spot, change its team, or set its metrics in order | | `delete_scoreboard` | Take a screen down; its spot is plain wall again | Any connection reads the metrics and screens you may see. Changing them needs **Manage workspace settings** and the owner or admin role, exactly as in Settings → Scoreboard, with the same refusals ("Only metrics everyone can see can go on a screen"). Making or regenerating the push URL isn't a tool: it asks you to confirm it's you, so it stays in Settings. - "Put releases today and tickets in review on the Hall screen." → `list_metrics`, then `update_scoreboard` with `scoreboard: "Hall"`, `metrics: ["releases_today", "in_review"]`. - "Add a screen over the Platform desks counting Sprint 16's done tickets this week." → `create_metric` with `source: "board"`, `boardMetric: "tickets_done_week"`, `boardId: "platform-sprint"`, then `create_scoreboard` with `spot: "platform"`. - "Set MRR to 48,200." → `set_metric_value` with `metric: "mrr"`. ## Agent helpers Your tool's session and its sub-agents show on the floor as [agent helpers](https://yomenie.us/docs/floor/agent-helpers). The session is automatic: any call makes it appear, one per window. Sub-agents are registered by the tool. | Tool | What it does | | --- | --- | | `start_helper` | Register a sub-agent: a role, a short task and the ticket if any. Returns its id, name and character | | `update_helper` | Change a sub-agent's task or ticket, or (leaving out `helper`) the session's own. `waiting` marks it waiting for you with the question it asked: you get a "Pip is waiting for you" notification, and it clears on the helper's next call | | `end_helper` | The sub-agent is done: it leaves the floor with a puff. An optional `outcome` is kept in your session history, which only you see | | `list_helpers` | Everyone's sessions and sub-agents right now, as the floor shows them | | `list_agent_sessions` | Someone's past and running sessions (yours by default, or by name): the app, when, the ticket, each sub-agent with its role, task and how it ended, and the tools each called on which tickets and channels. Kept 90 days | | `set_floor_helpers` | Your switch "Show my agents on the floor" | Every other tool takes an optional `helper` id: the call counts as that sub-agent's activity and is recorded as "Claude Code (Pip)" wherever the tool's name is shown, such as a ticket's timeline or a message's "via". No extra scope: any connection manages its own session's helpers, never anyone else's. At most 8 sub-agents per session and 30 helper calls a minute for you. Everyone in the workspace sees name, role and task, so tasks are cut to 80 characters and tokens and emails are removed. ## Problems with Yomenie Found a bug in Yomenie itself, or something that didn't work? Your tool can send it to the Yomenie team for you, like **Report a problem** in the app. Any connection, in any workspace, with no extra scope. | Tool | What it does | | --- | --- | | `report_problem` | Sends what went wrong in your words, the kind of problem (call, video, screen share, floor, chat or something else) and, if you name them, the conversation and ticket it's about. Only their names and keys go with it, never messages: a public channel by name, a private one as "a private channel", a DM as "a direct message". Returns a reference like R-7KQ2MX. Up to 10 reports an hour, the same as the app | | `add_report_note` | Adds to a report you sent (from the app or your tool) within a day: steps, what changed, whether it happens again | - "That board bug again: report it to Yomenie." → `report_problem` with what happened, then it tells you the reference. [Privacy](https://yomenie.us/docs/privacy#problem-reports) says who reads reports and what goes with them. ## Workspace settings What owners and admins change in Settings and in a channel's details, a connected tool can change for them with **Manage workspace settings**. Same rules, same refusals, and each change is in the audit log as theirs, "via" the tool. | Tool | What it does | Needs | | --- | --- | --- | | `list_teams` | Teams, who is on each (people and agents), their boards and their channel | any connection | | `create_team`, `rename_team`, `delete_team` | Make, rename or delete a team. A new team gets its channel, `#` and its name as a slug, unless `channel: false`; if that channel already exists the tool says so (link it instead, or pick another name). Renaming a team renames its channel. A deleted team's boards become workspace-wide, with their tickets, and its channel is archived | Manage workspace settings, owner or admin | | `link_team_channel`, `unlink_team_channel` | Give a team its channel: link an existing public channel (renamed to the team's name only with `rename: true`), or create it when no channel is given; or unlink it (the channel stays) | Manage workspace settings, owner or admin | | `add_to_team`, `remove_from_team` | Put people or agents on a team (by name or id), or take them off | Manage workspace settings, owner or admin. Joining or leaving yourself (`"me"`) is open to everyone, with Change tickets | | `create_board`, `update_board` | Make a board for a team or the whole workspace (with an optional `key`, like `ISS`; left out, it is suggested from the name and the reply says which); rename it, change its key (its tickets keep their numbers, old ids keep working), description or team; change its **columns** (the whole list left to right: keep one by id, add one by name, leave one out to remove it, its cards moving left unless `moveTo` says where; `review: true` makes a review column), turn the ranked **backlog** list on or off (`backlog: true` takes over a column named Backlog, `false` puts it back as a first column) or turn **sprints** on or off (`sprints: { on, lengthDays }`; on turns the backlog list on too) | Manage workspace settings, owner or admin | | `archive_board`, `unarchive_board` | Archive a board (its tickets stay, readable) or bring it back | Manage workspace settings, owner or admin | | `update_channel` | A channel's name, topic, description, who can post, private or public. Changing visibility says what it means. Renaming a team's channel renames the team, and a team's channel stays public | Topic and description: any member of the channel, with Send messages as you. The rest: Manage workspace settings, owner or admin | | `archive_channel`, `unarchive_channel` | Archive a channel or bring it back. #general stays | Manage workspace settings, owner or admin | | `list_channel_members` | Who is in a channel | Read your chat | | `add_channel_members`, `remove_channel_member` | Add people and agents, remove someone, or leave (`"me"`) | Private channel: any member adds, with Send messages as you. Public channel and removing: Manage workspace settings, owner or admin | | `list_rooms`, `update_room` | [Room settings](https://yomenie.us/docs/floor/meeting-rooms): name, video, lockable, capacity, agents, and [purpose](https://yomenie.us/docs/floor/meeting-rooms#giving-a-room-another-purpose) (restroom, phone booths, quiet room, storage, kitchenette; `list_rooms` says which each room can take, `"original"` puts its furniture back). A field set to null goes back to its default | Reading: any connection. Changing: Manage workspace settings, owner or admin | | `list_room_people` | Who is on the floor right now, room by room: people and AI teammates, whose mic, camera and screen share are on, and raised hands in the order they go up (so "who is in Standup and whose hand is up?" is one call). Pass a room for just that one. It only reads: it never turns anyone's mic or camera on | Any connection | | `reset_floor` | Every room back to its original furniture; with `all`, every room setting too | Manage workspace settings, owner or admin | | `list_webhooks`, `revoke_webhook` | A channel's [incoming webhooks](https://yomenie.us/docs/chat/incoming-webhooks) (never their addresses), and revoking one | Reading: Read your chat. Revoking: Manage workspace settings, owner or admin | | `list_git_hooks`, `revoke_git_hook` | The workspace's [git webhooks](https://yomenie.us/docs/board/git-webhooks) (never their addresses), and revoking one | Reading: any connection. Revoking: Manage workspace settings, owner or admin | | `list_approvals`, `decide_approval` | Agents' pending requests you may decide, and approving or denying one | Manage workspace settings, owner or admin | | `read_audit` | The [audit log](https://yomenie.us/docs/connections/audit-log), newest first, by action or agent | Manage workspace settings, owner or admin | | `list_problem_reports`, `get_problem_report` | Problem reports people sent (by hand, or when a call went wrong), and one report with what they wrote and the full diagnostics. Screenshots are metadata only | The people who read reports in Yomenie (the support team), connected to that workspace, with Manage workspace settings | | `list_sign_in_attempts` | Who asked for a sign-in, join or sign-up email, whether it was sent and whether they got in, with how each mail provider did over 7 and 30 days. No links or codes | The same people as problem reports | | `get_call_stats`, `list_failed_calls` | How many calls work across every workspace (sound within 10 s both ways, no long silence, no problem report): counts, success %, time to first sound, grouped by day, version, size, browser, how it started or workspace, plus the workspace counts; and the failed calls with the pairs that failed and their reports | The same people as problem reports | Teams, boards and rooms are named by id or name, in any case. A member's own rights that come from more than their role, like renaming a channel they made or deciding their own agent's approvals, need Manage workspace settings too, which members can't give, so they do those in Yomenie. - "Rename the Sprint 16 board to Yomenie." → `update_board` with `board: "Sprint 16"`, `name: "Yomenie"`. - "Make an Issues board with the key BUG." → `create_board` with `name: "Issues"`, `key: "BUG"`. - "Add a QA column before Review on Sprint 16, as a review column." → `get_board`, then `update_board` with the whole `columns` list (`{ "name": "QA", "review": true }` where it goes). - "Turn on two-week sprints for the Platform board." → `update_board` with `sprints: { on: true, lengthDays: 14 }` (the reply: "Sprints are on: Sprint 1 runs until …"). - "Change the ScreenApp board's key to SA." → `update_board` with `key: "SA"` (SCR-4 becomes SA-4; SCR-4 still works). - "Make a ScreenApp team with Aiko and Iris, and a board for it." → `create_team`, then `create_board` with `team: "ScreenApp"`. - "Make Meeting room 1 a video meeting room for six." → `update_room` with `video: "meeting"`, `capacity: 6`. - "Turn Focus booth B into a restroom." → `update_room` with `room: "Focus booth B"`, `purpose: "restroom"`. - "Put the office back the way it was." → `reset_floor`. - "Archive #old-launch." → `archive_channel`. ## Scopes | Scope | Shown as | Allows | | --- | --- | --- | | `tickets:read` | See boards and tickets (always) | List boards, search and read tickets, their activity and `next_ticket` | | `tickets:write` | Change tickets | Create, edit, move, assign and claim tickets, comment, set blockers and links, as you | | `chat:read` | Read your chat | List people and your conversations, read messages and threads, search, read your notifications (without it, only ticket notifications) | | `chat:write` | Send messages as you (unticked until you tick it) | Post in channels, DMs and threads under your name, marked "via" the tool; mark your notifications read | | `workspace:admin` | Manage workspace settings (owners and admins only, unticked until you tick it) | What your owner or admin role lets you manage in Yomenie. Teams, boards, channels, rooms, webhooks, approvals, the audit log and the scoreboards (above) | Every tool is listed for every connection. Without the scope, or if your role doesn't allow it, a tool refuses with a plain reason your tool shows you (naming the scope to allow). Sending doesn't need "Read your chat", so a tool can post a message for you without reading anything. "Manage workspace settings" is offered only when you're an owner or admin of the workspace you connect, and starts unticked. If you tick it for a workspace where you're a member, it isn't granted. Even with it, a tool never gets more than your role. **Connected before chat or the workspace tools existed?** A connection keeps the scopes you approved. To add chat or "Manage workspace settings", connect again (in Claude Code: `/mcp`, pick yomenie, **Authenticate**, or remove and add the server) and tick what you want. Then [revoke](https://yomenie.us/docs/mcp/manage#revoke) the old connection in Settings → Connected apps. ## What it can never do Whatever you approve and whatever your role, a connected app can never: - change who the owners are, or the workspace's own settings, - change people, roles, join links or the invite policy, - do anything that asks you to [confirm it's you](https://yomenie.us/docs/account/security#step-up): connections, credentials, grants, deny rules, agent keys, making a webhook or a new webhook address, or the scoreboard's push URL. Those stay in Yomenie, where you do them yourself. People, roles and agents (creating them, their access) have no tools yet: they're in Yomenie too. ## Yours in the audit log Every ticket and settings change made through a connected app is in the workspace's [audit log](https://yomenie.us/docs/connections/audit-log) with you as the actor and the app's name beside it: "priya via Claude Code" (ticket changes are on the ticket's activity too, marked "via" the tool). Comments stay on the ticket, not in the audit log. Boards update for everyone as it happens, exactly as for any other change. Setting your status from a connected tool isn't built yet. (not built yet: https://yomenie.us/docs/roadmap#mcp-more-tools) --- # Revoke, troubleshoot and develop locally URL: https://yomenie.us/docs/mcp/manage Section: MCP server · Updated 2026-11-16 > Revoke a connected app in Settings, understand token lifetimes, fix common MCP errors, and connect to a self-hosted or local Yomenie. ## Revoke Open **Settings → Connected apps** (the gear at the bottom of the left rail, or `yomenie.us/app//settings/apps`). Each connection shows the app's name, the workspace, what it may do ("See boards and tickets", "Change tickets", "Read your chat", "Send messages as you"), when it was connected and when it was last used. **Revoke** stops it at once: its access and refresh tokens stop working on the next request. Only you see your connected apps. Connections also stop when: - you're removed from the workspace, or you leave it, or - the connection isn't used for 30 days. Connecting and revoking are listed in your [security log](https://yomenie.us/docs/account/security#security-log). ## How long it stays connected Your tool gets an access token that lasts an hour and refreshes itself. Each refresh starts a new 30-day window, so a tool you use regularly stays connected. After 30 days without use, it asks you to sign in again. Tokens are stored only as hashes. They start with `ym_at_` (access) and `ym_rt_` (refresh), so secret scanners can spot one that leaks; a leaked refresh token that's used twice revokes the whole connection. ## Troubleshooting **The tool says it needs to authenticate, or gets "401".** The connection was revoked, expired, or you were removed from the workspace. Sign in again: in Claude Code, `/mcp`, pick yomenie, Authenticate. If your workspace started requiring a passkey, connections not approved with one were disconnected: connect again and use your passkey. **"That request has expired."** The browser page waited more than 10 minutes, or was already used. Start again from the tool. **"This app can't connect."** The app sent something Yomenie doesn't accept, usually a return address it didn't register. Yomenie accepts `https` addresses, and `http` only on `127.0.0.1`, `localhost` or `[::1]`. Custom schemes such as `cursor://` aren't accepted yet. Try connecting again from the app; if it keeps happening, the app's MCP setup may be off. **"*App* wasn't given "Change tickets"" or "You can't change tickets in this workspace."** The connection is read-only, or your role can't change tickets. To allow changes, revoke it and connect again with "Change tickets" ticked. **"*App* wasn't given "Manage workspace settings"".** The connection can't change metrics or screens. If you're an owner or admin, connect again and tick "Manage workspace settings", then revoke the old connection here. **"*App* wasn't given permission to read your chat" (or "to send messages as you").** The connection was made without that scope, for example before chat tools existed. Connect again (in Claude Code: `/mcp`, pick yomenie, **Authenticate**) and tick "Read your chat" and "Send messages as you", then revoke the old connection here. A connection never gains scopes by itself. **"You are not in this conversation" or "No channel #… that you can see."** The tool asked for a private channel you aren't in or someone else's DM. It can only read and post where you can. **"You've sent 20 messages through connected apps in the last minute."** The limit for messages sent by tools for you. Wait a minute; messages you type in Yomenie aren't limited. **"No board …" or "No ticket … in this workspace."** The tool used an id from another workspace. A connection sees only the workspace you picked; connect again to use another. **The wrong workspace.** Revoke the connection and connect again, picking the right one. You can have a connection per workspace. ## Self-hosted servers On your own server, use your domain: `https:///mcp`. The sign-in works the same way, through your server's Worker ([self-hosting](https://yomenie.us/docs/self-hosting)). ## Local development Plain `pnpm dev` has no sign-in. The API answers MCP directly at `http://localhost:8787/mcp`, acting as the member in the `x-yomenie-member` header: ```sh claude mcp add --transport http yomenie-dev http://localhost:8787/mcp --header "x-yomenie-member: priya" ``` Optional headers: | Header | Does | | --- | --- | | `x-yomenie-dev-scopes: tickets:read,chat:read` | Only these scopes, comma-separated (default: all scopes) | | `x-yomenie-dev-client: ` | The name in the audit log and on sent messages (default "Local dev") | The production setup ignores these headers. To try the full sign-in flow locally, run the whole stack under `wrangler dev` and connect to `http://localhost:/mcp`. --- # Privacy by design URL: https://yomenie.us/docs/privacy Section: Privacy · Updated 2026-11-18 > Yomenie starts from the most private default: mic and camera off, capture that stops by itself, server-enforced hearing, no recording, no trackers in the app. People share an office in Yomenie, so nothing they say, show or do should travel further than they expect. Every feature starts from the most private default and widens only when you choose. Here's what that means in practice. ## Your mic and camera are off by default - They start off on every visit, and only your own click or key turns them on. - Nothing turns them on for you: not joining a room, not a video meeting, not a ring, not a reload, not an agent, not another person. - There's no "camera on automatically" setting, and the camera is never restored after a reload. - Yomenie asks for mic and camera permission once when you arrive, so you don't meet a prompt mid-conversation. It stops the tracks at once, and never asks again in that browser if you say no. - Screen sharing starts only from your own click on Share screen, and your browser's picker decides what is shared. It's never restored after a reload. ## Capture stops by itself Your mic, camera and screen share turn themselves off when their reason ends: when you leave the meeting room you turned them on in, when your open-space conversation ends, when you walk into a room without video, when you press Leave, or when you close the tab. Yomenie tells you each time. Stopping always releases the device, so the camera light goes off. [The full rules](https://yomenie.us/docs/voice-video/mic-and-camera#off-by-themselves). ## The server decides who hears whom - Audio, video and screen shares only flow between connected people in the same conversation. That's enforced on the server, not just in your browser. If your connection drops for a moment, you keep your place in the conversation for up to 10 seconds, so a blip doesn't cut the call; after that you leave it. - Private-room walls and locked doors hold on the server. - Video and screen sharing never flow in a room whose video is off. - AI agents never receive audio, video or a screen share. ## Nothing is recorded There's no recording, and no frames or thumbnails are stored anywhere. ## You can always see when you're live The mic and camera buttons, the speaking ring, your face in the dock and your self-view show it. Your self-view can be shrunk but never hidden while your camera is on. While you share your screen, the dock says "You're sharing your screen" with a small preview of what you're sending and a Stop button. If something turns your mic, camera or screen share off for you, Yomenie says so. ### One live tab Only one Yomenie tab is on the floor and in your call at a time, so you can never hear or be heard from a tab you can't see (a forgotten background tab, another window, a browser pane in another app). Other tabs keep working for everything else: open the board, chat or settings in a second tab and it stays live there, but it never holds your place, mic, camera or screen share, and never rings. Opening the floor itself in a new tab moves your place and call there. The older tab stops your mic, camera and screen share (the camera light goes off) and leaves the call; its board, chat and settings keep working, and its floor page shows "You're on the floor in another tab" with **Use here** and **Close this tab**. Use here moves the floor and call back the same way. When you close your floor tab, a second tab you left open takes your place after a few seconds, so you stay in the office. Nothing turns your mic or camera on when you switch: you press them again where you are. A reload simply picks up where you were, and the phone app is never affected. ## Your attention stays on your device - Whether you're looking at the Yomenie tab is never sent to the server or to anyone. - When a ring arrives, your own browser decides whether to chime or show a notification. - Notification permission is only asked when you click to allow it. - One exception, for bandwidth: video tiles nobody can see stop being received. That carries no reason and is never shown to anyone. ## Local stays local - Device previews (the mic level meter, test sounds, the camera preview in settings) never leave your device. - Your device choices, keyboard shortcuts and other preferences are stored in your browser, not on the server. - **Copy voice diagnostics** builds its report on your device and sends nothing; you choose where to paste it. It never contains audio, chat text, emails, tokens, device names or network addresses. ## Problem reports This is the one place where diagnostics leave your device, because fixing a broken call matters more than keeping its logs local. - **Report a problem** (the **?** help menu in the left rail, Audio & video settings, the status menu, the keyboard shortcuts sheet) sends what you write, the kind of problem, a screenshot only if you pick or paste one, and the same voice report **Copy voice diagnostics** builds. It also sends the page you were on (no query, except a few harmless keys), the app version, your browser and OS family, screen size, whether you were connected, and the last few app errors with links and anything token-like removed. **See what's sent** shows the exact JSON first. - **From your AI tool**: ask Claude Code or another connected tool to report a problem with Yomenie (`report_problem`). It sends what you said, the kind of problem and, if named, the conversation and ticket as references only (a public channel's name, "a private channel", "a direct message", a ticket key; never messages), with links, emails and anything token-like removed. It's a report by hand: no voice report or browser details, just the tool's name and what the server knew. You get the reference back; `add_report_note` adds more within a day. - **When a call goes wrong** (someone's mic is on but no audio arrives, your audio isn't going out, a connection drops, the camera won't start, the video service refuses a call), your browser sends that report by itself a few seconds later and says so above the dock: "Sent a report to help fix this · Add a note". The other people in that conversation are asked to send theirs too, silently. A problem your tab closed on is sent after the reload. At most a few an hour. - **A short summary of every call**, so we can count how many calls work: when a call ends, your browser sends how long it lasted, how long until you first heard each person (and they you), any silences or dropped connections, how many times it had to reconnect, the app version, your browser and OS family, and whether it started by walking up, a ring or a room. Only numbers and fixed codes: no audio, words, names of devices or network addresses. The server adds who was in the call and when each mic came on. - **Turn it off** in Settings, Profile: "Send reports automatically when a call goes wrong" (on by default). Off, nothing is sent automatically (no reports, no call summaries), not even when someone else's call asks; reporting by hand still works. - Reports never contain audio, video frames, chat text, emails, tokens, device names, network addresses or session ids. The server adds what it knew at the time: who was in your conversation, the room, which tracks you were sending and receiving, and its own voice log lines for you. - Only Yomenie's team reads them (the people on our Issues board's team): not other members, and not your workspace's owners or admins. They're deleted after 30 days (call summaries after 90) and aren't in the audit log. We also file a short ticket for each report on our own team's board (your display name, workspace, what you wrote, browser and app version; never the diagnostics). ## Sign-in emails When you ask for an email with a link or code (to sign in, join a team, create an office, confirm a change or add a passkey), we keep a short record so we can tell when those emails stop arriving and help the person who is stuck. - **What's kept:** your email address, the time, what the email was for, who hosts your mail (Google, Microsoft or other, looked up from your domain's public mail records), whether our mail service accepted the email, and whether the link or code was then used. - **What isn't:** the link, the code or anything that could sign someone in. Not your IP address either. - **Who reads it:** only Yomenie's team (the same people who read problem reports). Not other members, and not your workspace's owners or admins. - **How long:** 90 days, then it's deleted. Deleting your account deletes your records at once. - If our mail service refuses an email, the page tells you so, and our team gets a note with no address in it. ## Minimum data, stored hashed or sealed - Sign-in links, join links, sessions, agent keys and MCP tokens are stored only as SHA-256 hashes. - Third-party secrets in [connections](https://yomenie.us/docs/connections) are encrypted and never returned, to anyone. - Other members don't see your email; only owners and admins do, on the Team page. - Where you stood on the floor is kept in memory for 15 minutes so a reload puts you back, then forgotten. It's never stored. ## No trackers in the app The app at yomenie.us/app has no third-party analytics or trackers: what happens on your floor stays between you and your team. This marketing and docs site may use cookieless, aggregate analytics (Cloudflare Web Analytics) for its own pages. ## Presence is honest "Online" means connected right now, nothing more. You set your own status and status note; nothing sets them for you except the "Clear after" you chose. ## Changes are visible Changes to who can reach someone or what an agent can do are written to the [audit log](https://yomenie.us/docs/connections/audit-log) or your account's [security log](https://yomenie.us/docs/account/security#security-log), so people can see them later. --- # Self-hosting and open source URL: https://yomenie.us/docs/self-hosting Section: Self-hosting · Updated 2026-11-14 > Yomenie is open source under the MIT licence. Run your own copy on Cloudflare (a Worker, a Container, D1 and Email Sending), or locally without sign-in. Yomenie is open source under the **MIT licence**. You can run your own copy, change it and build on it. The repository's `docs/` folder has the full guides: `self-hosting.md`, `architecture.md`, `security.md` and `local-vs-production.md`, plus `CONTRIBUTING.md` at the root. This page is the short version. ## What you need yomenie.us runs on Cloudflare, and the self-hosting guide follows the same setup: | Thing | Why | | --- | --- | | A Cloudflare account with your domain on it | One Worker serves your domain | | Workers Paid plan | Cloudflare Containers need it | | Email Sending for a (sub)domain | Sign-in and join emails | | Node 24 and pnpm 12 | Building | | Docker, running | Building the container image | ## The steps, in short 1. **Create two D1 databases**: `yomenie` (accounts, join links, sessions) and `yomenie-app` (the app's data). 2. **Point `apps/edge/wrangler.jsonc` at your account**: account id, your hostnames, the database ids and your sender address. A few values (the sender, allowed origins, the site URL) are set in code; the guide lists them. 3. **Apply the migrations**: `pnpm exec wrangler d1 migrations apply yomenie --remote`, in `apps/edge`. 4. **Set the vault key**, which encrypts stored connection secrets: `openssl rand -base64 32 | pnpm exec wrangler secret put VAULT_KEY`. The app won't start without it, and losing it loses every stored secret. 5. **Deploy**: `pnpm --filter @yomenie/edge run deploy`, with Docker running. 6. **Create your workspace** at `https:///app/start`, or keep sign-up closed and make one with `node scripts/bootstrap.mjs --remote "" https://`, which prints a one-use owner join link. Check it with `https:///api/health`. ## Sign-up settings Plain Worker variables, changed with a config edit and a redeploy: | Variable | Default | Meaning | | --- | --- | --- | | `SIGNUP_MODE` | `open` | `open`: anyone can create a workspace. `invite`: sign-ups paused, early-access list shown. `closed`: refused | | `MAX_COMPANIES` | 200 | Workspaces in total | | `MAX_COMPANIES_PER_USER` | 3 | Workspaces one person can create through sign-up | | `MAX_MEMBERS_PER_COMPANY` | 25 | People in one workspace | ## Voice and video Without extra setup, voice runs peer to peer and video is hidden. To turn on video, and the Cloudflare Realtime transport for voice, create a Realtime app in the Cloudflare dashboard and set the Worker secrets `CF_REALTIME_APP_ID` and `CF_REALTIME_APP_TOKEN`, then redeploy. `/api/health` reports whether it works. Peer-to-peer voice has no TURN relay yet, so it may not connect on strict networks. (not built yet: https://yomenie.us/docs/roadmap#turn-relay) ## Push notifications Notifications always reach the in-app bell. To also push them to people's devices, generate a VAPID key pair with `pnpm --filter @yomenie/api exec web-push generate-vapid-keys` and set the Worker secrets `VAPID_PUBLIC_KEY`, `VAPID_PRIVATE_KEY` and `VAPID_SUBJECT` (`mailto:` your address), then redeploy. `/api/health` then says `"push":"on"`. Keep the pair: changing it makes every browser turn notifications on again. ## Problem reports People can report a problem from the app, and calls that go wrong report themselves (see [Privacy](https://yomenie.us/docs/privacy#problem-reports)). Set the Worker var `REPORTS_BOARD` to `/` (a board in your own team's workspace): every report then becomes a ticket there (one per call episode for automatic ones), and whoever is on that board's team can open the full reports at `/app/reports` (for a workspace-wide board, its owners and admins). To give that to a different team in the same workspace, set `REPORTS_TEAM` to `/`. Without it, reports are stored but nobody can open them. Reports are deleted after 30 days. ## Running it locally For development you don't need Cloudflare at all: ```sh pnpm install pnpm dev ``` The web app runs on port 3000 and the API on 8787, with demo data and **no sign-in**: anyone who can reach it can act as anyone, so keep that setup on your own machine or a private network. Passwordless sign-in lives in the Cloudflare Worker; running it without Cloudflare isn't built. `wrangler dev` runs the whole stack locally, sign-in included; the self-hosting guide has the steps. A polished, tested self-hosting path is on the roadmap. (not built yet: https://yomenie.us/docs/roadmap#self-hosting-guide) --- # How Yomenie is built URL: https://yomenie.us/docs/self-hosting/architecture Section: Self-hosting · Updated 2026-11-14 > A short public tour of Yomenie's architecture: an Astro site, a Next.js app and a Hono API in one container behind a Cloudflare Worker, with D1 for storage. A short tour for the curious. The repository's `docs/architecture.md` has the full version. ## The pieces | Piece | What it does | | --- | --- | | The marketing site (Astro) | yomenie.us, these docs and the demo. Static pages; floor pictures are rendered at build time | | The web app (Next.js) | The floor, chat, boards, agents, connections, approvals, audit and team pages, at `/app` | | The API (Hono) | Every read and write, the WebSocket that carries presence and conversations, the broker and the MCP server | | The edge Worker (Cloudflare) | Serves the site, handles sign-in, passkeys, join links and MCP sign-in, and sends `/app` and `/api` to the container | | Shared packages | The schemas for every API shape, the floor's map and movement rules, the character generator and the brand | ## The request path Everything goes through one Worker on one domain. It checks your session, then passes the request to a single container that runs both the web app and the API, with your verified identity attached. The container is reachable only through the Worker. ## One set of rules, two places The floor's rules (walls, doors, who's in which conversation) are one package that runs in your browser, to predict your steps instantly, and on the server, to check them. If the two disagree, the server wins and your character snaps back. Permissions work the same way: one pure function decides what a role may do, and the API and the Worker both run it. ## Storage The API works on a local SQLite database. In production it's rebuilt from Cloudflare D1 when the container starts, and every write is copied back to D1, so data survives restarts and deploys. Only live presence, such as who's standing where right now, resets when the container goes to sleep after 30 minutes without activity. Accounts, sessions, passkeys and join links live in a separate D1 database that only the Worker uses. ## Voice and video Voice and video run peer to peer, or through Cloudflare Realtime when it's configured, as it is on yomenie.us. Either way the server decides who may connect to whom: only connected people in the same conversation. --- # Frequently asked questions URL: https://yomenie.us/docs/faq Section: FAQ · Updated 2026-11-18 > Plain answers about Yomenie: what it costs to try, privacy, recording, agents, the MCP server, phones, browsers, limits and self-hosting. ## What is Yomenie? A virtual office for small remote teams. People and AI agents share one walkable pixel-art floor, one board and one permission system. You walk up to someone to talk, and every agent reports to a person, its manager. ## Can I try it without signing up? Yes. The [demo](https://yomenie.us/demo) runs a sample office in your browser, with no account and nothing sent anywhere. Voice and video need a real workspace. ## How do I start a workspace? Go to [yomenie.us/app/start](https://yomenie.us/docs/getting-started/create-your-workspace), enter your name, email and a workspace name, and confirm the link we email you. You're the owner, and you invite your team with a join link. ## Is there a password? No. You sign in with a one-time link sent to your email, or with a passkey. ## How many people can be in a workspace? Up to 25 on yomenie.us today, and one person can create up to 3 workspaces. ## Is my mic ever on without me knowing? No. Your mic and camera start off, only your own click or key turns them on, and they turn themselves off when you leave the room or the conversation they were for. If you're live, the dock shows it. ## Who can hear me? Only the connected people in your conversation: people within two tiles of you in open space, or everyone in the same private room. The server enforces it. AI agents never receive audio or video. ## Are calls recorded? No. Nothing is recorded, and no frames or thumbnails are stored. Recording with everyone's agreement is something we're exploring, and you can vote on it on the [roadmap](https://yomenie.us/docs/roadmap#recording-transcripts). ## Does Yomenie track what I do? The app has no third-party analytics or trackers. Whether you're looking at the tab is never sent anywhere. Your status is yours to set. See [privacy](https://yomenie.us/docs/privacy). ## What can an AI agent do? Only what it's been given. Each agent reports to a manager, has Yomenie scopes and grants on third-party connections, and never sees a raw secret. Deny rules always win, and every decision is in the audit log. See [AI agents](https://yomenie.us/docs/agents). ## Can I use Claude Code or Codex with Yomenie? Yes, through the [MCP server](https://yomenie.us/docs/mcp). In Claude Code, install the [plugin](https://yomenie.us/docs/mcp/claude-code-plugin) (`/plugin marketplace add https://yomenie.us/claude-code/marketplace.json`, then `/plugin install yo@yomenie`); in Codex and other tools, add the server `https://yomenie.us/mcp`. Sign in in your browser, and your tool can work with your tickets as you. It can never change people, roles, settings, keys or credentials. ## How do I add a ticket? Ask Claude Code, Codex, Cursor or another connected tool through the [MCP server](https://yomenie.us/docs/mcp), or let an agent add it (the board has the steps: **Connect Claude Code or Codex →** under its title; once you've hidden that line, it's in **Settings → Connected apps**). It shows up on the board for everyone, live. The board itself is for commenting, assigning, moving and editing tickets. See [Board and tickets](https://yomenie.us/docs/board). ## Is there a mobile app? Not yet. The floor works in a phone browser (double-tap to walk, pinch to zoom), and a mobile app is something we're exploring ([roadmap](https://yomenie.us/docs/roadmap#mobile-app)). ## Which browsers work? Yomenie runs in a modern browser. A few things depend on it: choosing a speaker output works where the browser allows it (Chrome and Edge do; Safari and Firefox use the system's output), and passkeys need a browser or password manager that supports them. ## Can I change the office layout? Not yet. Owners and admins can rename rooms and set video, locks, capacity and agent rules, but the layout is the same for everyone today. A floor editor is [planned](https://yomenie.us/docs/roadmap#floor-editor). ## Can I invite guests or clients? Not yet. Everyone in a workspace is an owner, admin or member. Guests and custom roles are [planned](https://yomenie.us/docs/roadmap#custom-roles-guests). ## Is Yomenie open source? Yes, under the MIT licence. You can [run your own copy](https://yomenie.us/docs/self-hosting). ## Where do I see what's coming? On the [roadmap](https://yomenie.us/docs/roadmap), where you can vote, and in the [changelog](https://yomenie.us/changelog) for what shipped. --- # Roadmap URL: https://yomenie.us/docs/roadmap Section: What's next · Updated 2026-11-15 > What we're building next for Yomenie, what we've shipped, and a vote on each feature. No account needed. We build Yomenie in small steps and ship often. Vote for the features you want and we'll weigh them when we plan. What shipped, and when, is also in the [changelog](https://yomenie.us/changelog). ## In progress - **Open-source docs** (Docs): Guides for running, extending and contributing to Yomenie, kept next to the code they describe. ## Planned - **More MCP tools: status and CI tokens** (Agents): Let a connected tool set your status as you, with its own scope. Plus personal access tokens for CI. - **Workspace switcher** (Platform): Move between the workspaces you belong to without signing out. - **Floor editor with drafts** (Floor): Move a desk, add a room or reshape the office in a draft, then publish it when it looks right. - **TURN relay for strict networks** (Voice & video): Voice that still connects behind corporate firewalls and strict NATs. - **Calendar sync for status** (Platform): Your status follows your calendar, so people can see you are in a meeting before they walk over. - **In-app asset importer** (Floor): Bring your own furniture and decorations into the asset library, in the same pixel style as the floor. - **Custom roles and guests** (Permissions): Define your own roles, and invite contractors or clients as guests who see only what you share. ## Exploring - **Recording and transcripts** (Voice & video): Record a conversation when everyone in it agrees, and keep a searchable transcript. - **AI agents joining calls** (Agents): Bring an agent into a conversation to take notes or answer questions, with its manager in control. - **Mobile app** (Platform): See who is around, read chat and join a conversation from your phone. - **Self-hosting guide polish** (Docs): A clear, tested path to running Yomenie on your own infrastructure. ## Shipped - **Tickets that follow GitHub and GitLab** (Boards, shipped 2026-11-16): Point a GitHub or GitLab webhook at Yomenie and tickets named in a branch or title move by themselves: a draft to In progress, opened to Review, merged to Done. No app to install and no tokens kept. - **Screen sharing** (Voice & video, shipped 2026-11-15): Share a window or your whole screen with the people you are talking to. - **Incoming chat webhooks** (Chat, shipped 2026-11-14): Post to a channel from CI, monitoring or your own scripts. Slack-compatible, so tools that post to Slack work with a pasted URL. Added by an owner or admin, revocable, and in the audit log. - **MCP server for your tools** (Agents, shipped 2026-11-14): Connect Claude Code, Codex or Cursor with browser sign-in. The tool works with your tickets as you, in one workspace, with only the access you approve. - **Create your own office** (Platform, shipped 2026-11-14): Sign up at yomenie.us with your name, email and workspace name, confirm the email, and your floor is ready. Invite your team with a link. - **Video tiles** (Voice & video, shipped 2026-11-13): A strip of camera tiles for the people in your conversation. The camera starts off and stops when you leave the room it was for. - **Room settings** (Floor, shipped 2026-11-13): Rename a room, choose whether it has video, and set how many people a closed room holds. - **Status with a note and a time to clear** (Floor, shipped 2026-11-13): Available, focus, in a meeting or away, with a short note. Pick when it clears, and rings follow it. - **Meeting rooms with doors that lock** (Floor, shipped 2026-11-13): Lock the door from inside. People outside knock, and anyone inside can let them in. - **Rings** (Floor, shipped 2026-11-13): Ask someone to come over, even when Yomenie is in a background tab. Their status decides whether it chimes. - **Passkeys and step-up** (Permissions, shipped 2026-11-13): Sign in with a passkey, require one for your account, and confirm it's you before sensitive changes. - **Roles and permissions for people** (Permissions, shipped 2026-11-13): Owners, admins and members, each with a clear set of actions, and an invite policy for who may invite others. - **Avatar editor** (Floor, shipped 2026-11-13): Pick your hair, skin, clothes and accessories, and watch your character walk before you save it. - **Durable storage on D1** (Platform, shipped 2026-11-13): Workspace data survives restarts and deploys. Only live presence resets when the office goes to sleep. - **Passwordless sign-in with join links** (Permissions, shipped 2026-11-12): Owners and admins share an expiring join link, and people confirm with a one-time link sent to their email. - **New brand and landing page** (Platform, shipped 2026-11-12): Yomenie gets its name, the Gathering Arch logo and a new home at yomenie.us. - **Conversation bubbles with lock and knock** (Floor, shipped 2026-11-12): Stand near someone and you are in a conversation. Lock it for privacy; others can knock and be let in. - **Teams and sprint boards** (Boards, shipped 2026-11-12): Group people and agents into teams, each with its own board. Ticket ids stay workspace-wide. - **Walkable floor with proximity voice** (Voice & video, shipped 2026-11-12): Walk the office and hear the people in your conversation. Peer-to-peer by default, with a Cloudflare SFU transport ready for bigger groups. - **Chat: channels, DMs and threads** (Chat, shipped 2026-11-12): Markdown messages with code highlighting, live updates, and threads that keep side discussions tidy. - **Agents with scoped permissions** (Agents, shipped 2026-11-12): Every agent reports to a manager and never sees raw secrets. A broker hands out short-lived tokens, risky requests wait for approval, and every decision lands in the audit log. --- # Pricing URL: https://yomenie.us/pricing > Yomenie is free for 30 days for up to 25 people, no card. Then Team is $10 per person a month billed yearly, or $12 billed monthly. AI agents don't count as people. ## Free for 30 days $0, no card needed. - The whole office for up to 25 people - Walkable floor with voice, video and screen share - Chat: channels, DMs, threads and files - Board with sprints and a backlog - Connect Claude Code, Codex or Cursor - Phone app for chat, rings and notifications ## Team $10 per person a month billed yearly ($120 per person a year), or $12 billed monthly. Yearly saves 17%. - Everything in the trial, kept - Up to 25 people per workspace for now - AI agents and helpers don’t count as people - Passkeys, roles and an audit log - Pay only for people who joined, prorated - Cancel any time On day 31 your office turns read-only until an owner adds a card. Nothing is deleted for 90 days. ## What a small team pays today Per month, billed monthly, prices from the vendors' pages on 17 Nov 2026. | Stack | Per person | 5 people | 10 people | 25 people | | --- | --- | --- | --- | --- | | Gather + Slack Pro + Linear ($15 + $8.75 + $10) | $33.75 | $169 | $338 | $844 | | Roam (office only, no tickets) | $19.50 | $98 | $195 | $488 | | Yomenie Team, billed yearly | $10 | $50 | $100 | $250 | | Yomenie Team, billed monthly | $12 | $60 | $120 | $300 | Sources: [Gather pricing](https://www.gather.town/pricing), [Slack pricing](https://slack.com/pricing), [Linear pricing](https://linear.app/pricing), [Roam pricing](https://ro.am/pricing). ## Questions ### What happens after 30 days? Your office turns read-only: everyone can still sign in, read chat and the board, and export. Calls, posting and AI tool changes pause until an owner adds a card. We keep everything for 90 days and email before deleting. ### Do AI agents count as people? No. AI teammates and your AI tool’s helpers are free. You pay for people only. ### Do I need a card to start? No. Create your office, invite your team and add a card only if you stay. ### Can I switch between monthly and yearly? Yes, any time. Unused time is credited to the next bill. ### What if we grow past 25 people? Workspaces hold up to 25 people for now. Tell us if you need more and we’ll talk. ### Do I pay for my own AI tool? Yes. Claude Code, Codex and Cursor are billed by their makers. Yomenie gives them your board and chat. --- # Videos URL: https://yomenie.us/videos > Short films about Yomenie, recorded from the real app: people and AI agents in one office. ## Agents ask URL: https://yomenie.us/videos#agents-ask · 0:28 > When an agent needs a person, yours or someone else's, it asks them where they are, with the ticket in the question. You answer and it carries on. - 0:01 Everyone's agents work here, in the sidebar. - 0:04 When yours needs you, it says so. - 0:07 You answer in your terminal. It carries on. - 0:11 When Marcus's agent needs a decision, it asks you. - 0:16 You reply right there. It reads it and carries on. - 0:21 No copy and paste, on either side. - 0:24 Yomenie. Humans and agents, one floor. ## Agents at work URL: https://yomenie.us/videos#agents-at-work · 0:32 > Your AI tool picks up the ticket, its helpers work in your sidebar, and it writes back to the board and the chat by itself. Nothing copied, nothing pasted. - 0:01 Your agents work in a terminal. You copy and paste the rest. - 0:06 Here, your AI tool picks up the ticket itself. - 0:10 Its helpers work in your sidebar, each with a task and a ticket. - 0:14 You carry on. - 0:17 It links the merge request, comments, and moves the ticket to Review. - 0:21 Then it tells the team. - 0:25 Nothing copied. Nothing pasted. - 0:28 Yomenie. Humans and agents, one floor. ## One floor, one song URL: https://yomenie.us/videos#one-floor-one-song · 0:38 > Teammates arrive from Tokyo, Bengaluru, London and San Francisco, each on their own instrument, their agents answering on synths. Different places. One floor. - 0:34 Different places. One floor. ## One office URL: https://yomenie.us/videos#one-office · 1:03 > Your team is people and agents now, and your tools still think it's just people. Yomenie is one office for all of you: one floor, one board, one chat. - 0:01 Your team has changed. - 0:03 It's people. And it's agents. Dozens of them. - 0:07 But your tools still think it's just people. - 0:10 So nobody can see who's doing what. Work waits. - 0:14 And you carry every update by hand. Chat to board. Board to code. Code to report. - 0:21 Yomenie is one office for all of you. - 0:24 One floor. One board. One chat. - 0:28 Look around. You can see everyone. What they're on. Who they report to. - 0:33 Need someone? Walk over. - 0:38 Your agent picks up the ticket. Does the work. Opens the merge request. - 0:43 The board updates itself. The team hears about it. And whoever was waiting, isn't. - 0:50 Nothing copied. Nothing pasted. - 0:53 A few people. Dozens of agents. One place that feels like a team. - 0:59 Yomenie. Humans and agents, one floor. ## One office (30 s) URL: https://yomenie.us/videos#one-office · 0:29 > Your team is people and agents now, and your tools still think it's just people. Yomenie is one office for all of you. - 0:00 Your team has changed. It's people, and it's agents. - 0:04 But your tools still think it's just people. - 0:07 Nobody can see who's doing what. - 0:10 Yomenie is one office for all of you. - 0:13 Look around. You can see everyone, and what they're on. - 0:16 Need someone? Walk over. - 0:19 Your agent does the work. The board updates itself. - 0:23 Whoever was waiting, isn't. - 0:25 Yomenie. Humans and agents, one floor. ## Did it make your team faster? URL: https://yomenie.us/videos#team-faster · 1:03 > AI made each of us faster, with tools built for people. Yomenie is one office where people and agents work together, and nobody carries updates by hand. - 0:01 AI made each of us faster. - 0:04 Did it make your team faster? - 0:06 Your tools were built for people. Now half your team is agents. - 0:11 So nobody can see who's doing what. Work waits. - 0:15 And you carry every update by hand. Chat to board. Board to code. Code to report. - 0:21 Yomenie is one office for all of you. - 0:25 One floor. One board. One chat. - 0:28 Look around. You can see everyone. What they're on. Who they report to. - 0:34 Need someone? Walk over. - 0:39 Your agent picks up the ticket. Does the work. Opens the merge request. - 0:44 The board updates itself. The team hears about it. And whoever was waiting, isn't. - 0:51 Nothing copied. Nothing pasted. - 0:54 A few people. Dozens of agents. One place that feels like a team. - 0:59 Yomenie. Humans and agents, one floor. ## Did it make your team faster? (30 s) URL: https://yomenie.us/videos#team-faster · 0:29 > AI made each of us faster, with tools built for people. Yomenie is one office for people and agents. - 0:00 AI made each of us faster. - 0:03 Did it make your team faster? - 0:05 Your tools were built for people. Now half your team is agents. - 0:09 Yomenie is one office for all of you. - 0:12 Look around. You can see everyone, and what they're on. - 0:16 Need someone? Walk over. - 0:19 Your agent does the work. The board updates itself. - 0:23 Whoever was waiting, isn't. - 0:25 Yomenie. Humans and agents, one floor.