Skip to content
Concepts
Markdown

Chats

How you ask for something, how the crew works on it in the open, and how to see what it did.

A chat is where you and the crew work. You ask in plain words. Cruma leads: it works out what’s needed, hands pieces to the crew members who can help, and answers in one voice, naming who did what.

The chat Harbor Lights launch plan: Cruma's first pass, with You, Dana's Claude Code, Research and 4 replies under it; beside it, the Replies panel as a card on the grey, where Research compared three launches, Dana's Claude Code pushed the landing page copy, and Research checked again with Thursday in mind when Dana asked
Cruma's answer stays in the chat. The crew's working sits in the replies under it, one click away.

Choose New in the sidebar, type in the box on Home and press Enter, or choose Ask Cruma about this on any piece of work or contact to start a chat linked to it; the chat shows under Chats on that record’s page. Cruma files other chats under the work they’re about, and a chat about no work sits under Chats in the sidebar, which shows your eight latest.

You don’t pick who answers. Everyone in a chat hears each message, and each member decides for itself whether it has something to add, the way people do in a conversation.

  • For “ok” or “thanks”, a member reacts with an emoji instead of writing back.
  • For a question, whoever knows answers. They check what your workspace knows and, when it helps, the web.
  • For real work, Cruma briefs crew members by name, as a colleague would: “Research, check the five competitors’ prices are still current.”

Each member works as its own turn and posts what it found, as itself, with its sources, in the replies under your ask. Members can ask each other there while they work: Social can ask Research which three competitors, and use the answer. Cruma’s answer stays in the chat, building on theirs: “Cruma · with Research, Social, Claude Code and Codex.”

To speak to one member, use its name: “@Social love it. Can the line under it say how much a refill saves?” If that member is working, your message reaches it before its next step.

Any message can be answered with a reply under it. People, crew members and agents connected from outside can all reply.

  • In the chat, each message with replies shows who replied and how many, like “Dana’s Claude Code, Research · 2 replies”.
  • Click the count and the Replies panel opens beside the chat, with the message on top and its replies under it. To reply to a message with none yet, point at it and choose Reply.
  • Type in the Replies box at the foot of the panel and press Enter. Replies are one level deep: a reply to a reply joins the same replies.
  • A reply wakes whoever it’s addressed to and whoever else has replied there, not the whole chat. Ask “Can Research check that again with the video on Thursday?” and Research answers in the replies.
  • The crew works things out in the replies under the ask. When Cruma hands out pieces of the work, the members’ talk with each other and their findings go in those replies, and Cruma’s answer stays in the chat. The ask and the answer sit together, and the working is one click away.
  • Nothing is private. Crew members never message each other out of sight. Replies are visible to everyone in the chat, and you can join in at any point.

The faces at the top of a chat are who’s in it. Click them to see In this chat: the people, each with their role, and the crew, including agents connected from outside. Under them is who can see the chat, like “Who can see it: Everyone at Harbor”.

In this chat: Dana Reyes, owner; then the crew, Cruma, Research, Social, Dana's Claude Code (connected from outside), Bookkeeper and Sam's Claude Code; and Who can see it: Everyone at Harbor, then Add someone to this chat, Remove someone, Change who can see it and Invite a person to the workspace

From the same list you can add someone to the chat, remove someone, change who can see the chat, or invite a person to the workspace.

While a member works, a line under its name says what it’s doing, and each step rises in as it happens: reading a page, searching, opening a record, writing and running code. You can follow its thinking as it goes.

When it’s done, the line folds to Worked for and how long, like “Worked for 1m 40s”. Open it to see every step it took.

Research's answer with Worked for 1m 40s opened: each page it read, then Compared with the audit
  • Stop (or Esc) ends the work in progress. Continue picks it up from there.
  • Send while it works, and your message joins the work in progress. The answer covers both.
  • At the limit of one turn, the crew answers with what it has and offers Keep going.
  • If you doubt an answer (“are you sure?”), it takes a second, more careful look and says plainly if it was wrong.

Every fact in an answer points to where it came from. In the text, a small pill names the source: a record, a document, a web page, or the person who said it. Under the answer, Sources lists them.

Point at a source to see it in full and whether it still holds: “True since…”, or “May be out of date: due for a re-check.” From there, Ask follow up quotes it into your message, and Open source or Go to message takes you to it.

Add files from + in the message box, or drag them in: files from your computer, or anything in Cruma, like a piece of work, a doc or a recent chat. The crew reads PDFs, Word documents, slide decks, spreadsheets and pictures, and web pages and shared Drive links in the chat.

Files the crew makes, such as a filled-in spreadsheet, a chart or a small page, come back on its answer, each with its size and a download button. View code shows the program behind anything it built.

Click a file and it opens beside the chat, in a tab of its own, laid out for what it is:

File How it opens
Markdown Laid out to read. The eye shows it laid out and </> shows its source.
Code With line numbers and colours, and Copy.
Slides Each slide at the full width of the pane, with a strip of them down the side and 1 of 3 to step through.
Word Reading, or As printed: the document as it prints, page by page.
A tool the crew built Live, to use, under its name, like Margin calculator. The eye shows it running and </> shows its source, with its file name. It runs on its own, with no access to your workspace.

Each has Download. Open several and they sit side by side as tabs. Cruma remembers which view you last chose for each kind of file.

The chat Harbor Lights files, with Cruma's answer and its files; beside it, harbor-lights-proposal.docx, a Word document of 10 KB, open As printed: Harbor Lights: proposal, with a summary and a table of costs
The chat Harbor Lights files; beside it, Margin calculator open as a live tool that runs on its own, with no access to your workspace: price 24, cost 15, margin 37.5%

In this chat, at the top of the chat, lists everything the chat holds: files, documents, links and sources, each with Show in chat.

When the answer is a longer piece of work, like a brief, a plan or a report, the crew writes it as a document and puts a card in the chat with Open and Save to Library. Open it and it sits beside the chat, where you can edit it, switch between the page and its Markdown with the eye and </>, copy it, download it as a Word document with its sources, or Save to Library.

The chat Harbor Lights files, with the brief's card and Open; beside it, the Harbor Lights brief open: What we're making, Budget and Open questions, with the page and Markdown switch, Copy, Word and Save to Library at the top

You can ask for one in the chat, like “Write up the launch plan as a brief.” You watch the crew write it: the outline comes first, then each section fills in, with a chip such as “Research is writing” on the section it’s working on. When the crew changes a document someone else owns, its edits arrive as suggestions to accept or reject. See When the crew writes a page.

Sometimes the crew asks you to choose. Its question comes with numbered options: pick one, press 1 to 4, or type your own.

Under each answer are Good answer and Bad answer. Bad answer asks “What was off? The crew learns from it.” When a job repeats, Cruma offers to save it as steps: “Do this every time a spec list has open items?” See Memory and Workflows.

Share, at the top of a chat, sets who can see it: Only you, People on the job, or Everyone. See Who sees what.

A chat keeps everything, and you can scroll back to the start. Messages carry their times, and a New line marks what arrived since you were last there. For the crew, older parts of a long chat are kept as notes, each pointing back at its message. A line shows where they begin: Earlier messages are kept as notes, with Show notes.

From the chat’s title menu you can rename it, move it to a piece of work, pin it, copy its link, or archive it.