Orkestia
Blog
Cockpit app

App chats and shared chats

Read your apps' chat spaces inside Orkestia Cockpit — add a chat by link or from your organization, notifications and unread counts, taking your member seat — and share assistant chats with the people in your organization

Cockpit has two kinds of chat, and they live in different places:

App chatsAssistant chats
WhatThe chat space of an Orkestia app (a team chat, support, customers): the same chat your app's people useYour conversations with the Orkestia assistant, including coding sessions
SidebarChats sectionThe assistant history (New chat, ⌘N)
Who is in itThe app's membersYou, and anyone you share it with
NotificationsPer chat, set by youOnly when something is shared with you

App chats

Add one

Add a Chat (the + next to Chats, or Add an app chat… when you have none) opens a sheet with two ways in:

  • Your organization. The app lists the organization's published chat spaces (data.buzz.space.list). Each shows its name with Add, or Added when you already have it. This opens it with your member seat in that app. When there are none the sheet says No published chat spaces in this organization. This list needs you to be signed in as an operator.
  • Chat link. Paste the address of an app's chat page (https://yourapp.app.orkestia.dev). The app resolves it and adds the chat with its name and logo.
MessageMeaning
That doesn't look like a web address.The link is not a URL
Couldn't reach that address.The app could not load it
That address isn't an Orkestia app chat.The page is not a chat page

There is one chat per app; adding an app you already have opens it.

If you are not an operator of an organization, Not an operator? Use app chats only on the sign-in screen opens the app with just your chats. There you can add a chat only by link, and each chat signs you in with your Orkestia account for that app.

Open and use

Selecting a chat in the sidebar opens it in the main area. The first open can take up to a minute (Opening … the first time can take up to a minute.). The toolbar shows Connected, Connecting… or Not connected; when it fails, Try again reconnects. The chat itself is the same component the web uses, so channels, DMs, threads, mentions and commands work as they do there. Every connected chat stays loaded while hidden, so it keeps its connection, unread count and notifications.

The sidebar row shows the app's logo or initial, a dot for its connection (connected, connecting, not connected), and a badge: red for unread mentions and DMs, plain for other unread messages.

Couldn't open it

CauseWhat you see
You have an Orkestia role in the organization that owns the app but no seat in it yetTake My Seat… appears next to Try Again
Anything elseThe platform's reason, and Try Again

Take My Seat… asks first: Take your member seat in ? It uses one end-user seat from your organization's pool. You can release it later in the Console. Then it reopens the chat. It appears for these refusals: the seat was not taken, it is suspended, or you are not seated.

Right-click a chat

ItemDoes
OpenOpens it
Open in BrowserOpens the chat page on the web
NotificationsAll Messages, Mentions & DMs, Off
Move Up / Move DownReorders the list
Connect / DisconnectLoads or unloads it
Remove Chat…Removes it from your list. You can add it again later

Chat settings

The sliders button next to Chats opens Chat Settings.

SettingMeaning
Keep connectedHow many of your most recently used chats stay connected, from 1 to 20 (default 5). Only connected chats notify
Per chat: loadThe checkbox loads or unloads that chat
Per chat: notificationsAll messages, Mentions & DMs (default for choosing it from the sheet), Off

Notifications

A message notifies only when all of these hold:

  1. It is not your own and not a status message.
  2. The chat's level allows it: All messages, or Mentions & DMs for a message that mentions you or is a DM.
  3. The chat is not on screen with the window focused.

The notification reads in # · (or · for a DM) with the message text shortened to 160 characters. Clicking it opens that chat on that channel.

Mentions and DMs that arrive while the chat is not on screen count toward attention. Switching to the chat while the window is focused counts as reading them. The app's dock or taskbar badge follows these counts and the pending decisions.

Chat credentials are never stored on disk. Each chat holds a token for that app only, in memory, and exchanges again near expiry. Signing out of Cockpit closes every chat.

Assistant chats

The assistant's chats are grouped in the sidebar: Coding Sessions first, Shared with Me, then your own by day (Today, Yesterday, Previous 7 days, Older), then Living Surfaces folded apart. A search box filters by title and preview.

Share a chat

The owner of a chat can share it with people in the same organization, up to 10 people.

RoleCan
Can viewRead the chat and its work as it happens
Can post and approveWrite to the assistant and answer its approvals, like you. Planner actions also need the operator role on the software-planner
OwnerEverything, including sharing and archiving
  1. Open the chat's Share this chat sheet.
  2. Search Name or email (only people in the organization who are not already in the chat).
  3. Pick the person, choose What they can do, and press Share.

In the same sheet the owner changes a person's role from a selector or removes them (a toast offers Undo: " no longer has this chat"). Only you, for now. is shown until you share. A person who has the chat sees People in this chat, the owner, the note about what they can do, and Leave This Chat (they stop seeing it; the owner can share it again).

Someone you share with gets a notification, Shared with you; clicking it opens the chat. A chat shared with you shows Shared by in its header, and a viewer sees View only — ask for edit access.

What a shared chat shows

  • Each message says who wrote it. A message a person sent through the assistant is attributed to them.
  • While someone else's request is being answered, your composer says 's question is being answered; yours sends when it lands, and your message is sent after theirs.
  • The chat records what people did outside a turn: asking for a plan, the planner starting, a plan approved, denied or revised, a session stopped, coding mode changed, someone added or removed, an action confirmed, notes. These appear in the chat for everyone and keep its history honest.

A viewer of a coding chat does not see plan buttons. See Agents and Coding.