Skip to content
CSuite
GuideChat

Chatting with CSuite.

Every control, tool and rule in the chat workspace, with a figure for each, followed by recipes that get real work out of one thread. The short version lives on the main guide; this page is for when you want to know exactly what happens when you press Send.

Part 1

Get around

1.1

The workspace

A conversation that has just generated an image. The numbers match the legend below.

Open Chat from the rail, the middle entry of the second group. It is one conversational workspace where you talk to a model and make media in the same thread: ask a question, search the web, read a document you attach, generate or edit an image, a clip or a voice, or run a saved workflow. Everything it makes lands in your project folder as a real file.

1 · Conversations
Your project folder pill, the + for a new conversation, and every conversation with its message count. Rename or delete from a row’s More actions.
2 · Title
Names itself after the first exchange; edit it in place and your name wins.
3 · Models
The chat model by name, opening the picker and the More models slots the assistant generates with. Beside it, copy the whole conversation as Markdown.
4 · Thread
Your messages in bubbles on the right, replies as plain text on the left, with a step list and the media each turn produced. A Jump to latest pill floats when you have scrolled up.
5 · Composer
Message…, with Enter to send and Shift+Enter for a new line. Stays editable while a reply runs; Send becomes Stop.
6 · Attach and Web
Add image, Add document, and the Web toggle that lets the model search and read pages from your machine.
7 · Send
Or Resend when you are editing your last message.
1.2

Starting a conversation

The first-ever conversation opens the model picker before anything is created; Start conversation waits for a tool-calling model.
1
Pick a chat model
Chat works by letting the model call tools, so the picker lists only tool-calling models: a local Ollama tag flagged for it, a cloud model on Runware or OpenRouter whose API does tools, or a model on a vendor key (OpenAI, Anthropic, Google, xAI, DeepSeek, ByteDance). Replicate models, Hugging Face models and a few Runware tiers cannot and do not appear. Leave it on Auto and CSuite picks a chat-capable model per turn.
2
Start it
On your very first conversation the picker opens before any row is created and Start conversation waits (“Pick a tool-calling chat model to continue”); later ones start at once from the +. The pick is global: the same one as Models → Defaults and the composition editor.
3
Let it name itself
The first send gives the conversation a short name from your words; after the first plain reply the chat model proposes a three-to-six-word title. A title you set yourself always wins.

Deleting a conversation stops anything it is still doing and removes it from your disk; there is no archive. History is stored locally in the app’s database and never leaves the machine on its own.

1.3

Models

The Models popover from the thread header: the chat slot, then one slot per kind of media the assistant can make.

The Models pill in the header opens the chat slot and, under More models, the slots the assistant reaches for: Image, Video, Speech, Music, Sound effects and Transcribe. The chat model also writes the replies and the prompts it sends to those models, so there is no separate text slot. Any slot can be Auto. Ask for a kind of media whose slot is empty and the assistant stops, says so (“No image model is selected yet. I’ve opened Models for you…”) and opens the picker on that slot.

Rules you write under Account → Instructions (Global, plus the Chat section) are appended to the assistant’s system prompt on every turn.

Part 2

Talk

2.1

Replies, reasoning and steps

A thinking model mid-reply: the Reasoning block open while it streams, the step list, and a saved reply’s footer with its tokens and time.
  • Streaming: cloud and local replies arrive token by token. The composer stays editable meanwhile.
  • Reasoning: a thinking model’s thoughts show in a collapsible block, open while it streams and kept on the saved reply.
  • Steps: a list ticks off each model round (“Thinking”) and each tool call (“Generating image”, “Searching the web for …”, “Cropping image to 1:1”) with a done or failed mark, so a long turn is never a blank spinner. A turn chains up to six tool rounds, then stops and says so.
  • Footer: every reply names the model that wrote it; hover for the tool it used, the tokens in and out, and how long it took. Notices (“Stopped.”, a pick-a-model note) render muted and are not replayed to the model later.
  • Context: history is budgeted from the model’s real window, oldest messages dropped first; your new message always goes in full. A reply that runs out of window says so.
2.2

Regenerate, edit, stop

The actions under a message, and the composer while editing the last message for a resend.
  • Regenerate the newest reply: the whole turn re-runs, tool rounds included, reusing the images you had attached.
  • Edit and resend your newest message: the composer shows “Editing last message — Esc to cancel”, and on Resend everything after it is removed and the corrected version runs fresh, with its attachments.
  • Stop genuinely cancels: the provider call is aborted and a running edit is killed. What earlier rounds produced stays in the thread, and a later round failing never takes an earlier image with it.
  • Copy any message, or the whole conversation as Markdown from the header. Delete removes one message after a confirm.
  • Keep up: the thread follows the reply until you scroll up; Jump to latest brings you back.
2.3

Read aloud

A reply voiced with the Speech slot’s model, playing under the message.

The speaker button under a reply (Read aloud) voices it with your Speech model, the markdown stripped to plain text, and plays it in a small player under the reply. Afterwards the button plays and pauses the saved clip. The clip is kept with the conversation rather than in your project folder. With no speech model set the button says so with an Open Models shortcut.

Part 3

Make and edit media

3.1

Generating in the thread

A video request mid-turn: the step list, the model’s reasoning, and the parameters read from the message.

Ask in plain language and name the kind of thing you want: “make me a hero image of…”, “a 5-second clip of…”, “say this in a warm voice”, “a 30-second lo-fi bed”, “a door creak”. Before each turn the chat model reads your message, in any language, and decides which tools to offer: a kind is offered when you ask for it, follow up on it (“make it blue” after an image) or say yes to a reply that suggested it. A request naming no kind (“generate a cat”) gets one short question back instead of a paid guess.

  • Images go to the Image slot; video to the Video slot; speech, music and sound effects each to their own audio slot, so a voice-over never runs your music model. Speech is only offered when you ask for it in words (say, speak, narrate, read aloud, voice).
  • Settings ride in the sentence: “16:9”, “square”, “portrait”; for video “8 seconds”, “1080p”, “with audio” or “silent”; for music a length and a format. They are lifted out before the prompt is sent and checked against the model.
  • Under Auto on a slot, a hint such as logo, icon, vector, photo or cinematic steers which model is picked for that call.
  • Results appear in the thread with a caption (“Generated image”, “Generated video”) and the model’s own narration, and are saved into your project folder. Generated speech is kept with the chat instead.
TipOne message can carry a whole deliverable: “make a product image, then a 5-second clip from it, then a two-sentence voice-over for the clip”. The assistant chains the tools, up to six steps.
3.2

Follow-up edits

A deterministic crop that never reaches the model, followed by an image-to-image update on the same file.

Edits target the most recent file of that kind in the thread, so “it” means the last image, clip or recording. Two paths:

  • Deterministic edits: crop or resize an image, crop, resize or convert a video, trim or convert audio. An obvious English request (“crop it to 1:1”, “resize the video to 720p”, “convert to WebM”) is recognised before the model is called and runs on the local engine, on any provider, with no token spent. A question never triggers one; a crop needs a standalone ratio such as 9:16.
  • Creative revisions: “make the slate matte black”, “same scene at dusk” run image-to-image on the last image (“Updated image”) through your Image model.
  • Validation: an argument the model gets wrong (an aspect ratio the file cannot take, a height off the ladder) is a tool error it can correct, never a silent default.
3.3

Video from images

Two attached images become the start and end frames of the clip.

A video request uses the turn’s own images as frames: one image attached to the message or made earlier in the turn becomes the start frame, two become start and end. With none, the two most recent images in the conversation are used. So “animate that” after an image, or “a video from the first to the second” with two attachments, both work. The Video slot’s model must take a start frame for this; a text-only model ignores them.

3.4

Running a workflow

A saved workflow run by name, its File-node outputs posted back as attachments.

Ask for one of your saved workflows by name (“run my podcast intro workflow”) and it runs headlessly with the same engine as the Workflows screen. Each File node’s media output is posted into the thread as an attachment, and the caption counts the nodes (“Ran workflow “Podcast intro” — 4 nodes completed”, with failures counted when some stop). A name that does not match lists the workflows you have.

Part 4

Give it material

4.1

Attaching images

Images and a document staged in the composer, the drop target, and the toast a text-only model shows.

Attach any number of PNG, JPG, GIF or WebP images with Add image, by dragging them onto the thread, or by pasting from the clipboard. On a vision-capable model each is sent as real image input, so you can ask what is in them or compare two. A model that cannot see images says so with a toast (“The current chat model doesn’t accept images — switch to a vision-capable model to attach them.”) rather than ignoring them. The images you attach are also what the next edit, update or video uses first, before anything older in the thread.

4.2

Documents and the digest

A 300-page PDF: the card shows how much the model saw, and the digest runs from a card above the composer.
1
Attach it
Add document, drag or paste a PDF, plain text, Markdown or HTML file. The text is extracted on your machine (a PDF page by page, with page numbers) and carried into the conversation, so follow-ups further down the thread still see it.
2
Read the card
The attachment’s card says what reached the model: “Sent in full”, or “Pages 1–30 of 300 seen (10%)” when the document is larger than the model’s context window allows on one turn. Ask about a specific part, pick a model with a larger window, or digest it.
3
Digest when it will not fit
A card above the composer offers Digest whole document with a section and token estimate. The model summarises the document section by section, then consolidates, with progress and Cancel. From then on every turn reads the digest and the assistant gains a lookup tool: ask about “page 10” or “pages 12 to 14” and it reads those pages verbatim; ask a question and it searches every section for the passages. The digest is kept per document and model and reused.
4.3

Web search

With Web on, the assistant searches, reads the top pages, cites them by number and lists the sources under the reply.
  • The Web toggle in the composer is on by default and offers search and page reading on every turn while it is on. Off, the chat is fully offline (“Click to keep this chat offline”).
  • No key, no service: the search runs from your machine. A hidden, sandboxed window loads a search engine’s own results page (Google, then DuckDuckGo, Bing and Brave if one gives nothing), and the top four results are read and reduced to text. The first search of a session takes about ten seconds, later ones about four.
  • Sources: pages are numbered per turn, the reply cites them as [1], [2] after the sentence they support, and the sources show as chips under the reply that open in your browser. Web text is framed to the model as source material, not instructions, and the reply knows today’s date.
  • Budget: a quarter of the model’s window is reserved for web results, so a small local model reads less of each page than a large cloud one.
  • Guard: addresses on your local network and private ranges are refused, because the URL is chosen by a model that has just read untrusted text.
4.4

What stays on your machine

Where each part of a conversation runs, by the kind of chat model you pick.

Conversations, messages and attachments live in the app’s database on your disk. With a local Ollama model, the replies, the tool decisions and every deterministic edit run on the machine; with a cloud model your messages, attached text and images go to that provider under your key. Generated media follows each slot’s model. Web search runs locally either way, and turning Web off keeps a thread entirely offline. The full picture is in Privacy & data.

Part 5

Recipes

5.1

A sourced research brief

1
Ask with Web on
A cloud model with a large window reads more of each page. Ask a precise question and let it search; check the [n] citations against the source chips.
2
Add what you already have
Attach your own notes or a PDF and ask it to reconcile the two: “Compare what you found with the attached brief and list the differences.”
3
Take it out
Copy the conversation as Markdown from the header, or copy the final reply, and paste it into the Text workspace to shape it into a document.
5.2

An asset pack in one thread

1
Set every slot first
Open Models and fill Image, Video and Speech so no request stops to ask.
2
Chain it
“Make a product image of the grinder on wet slate, 16:9. Then a 1:1 crop of it. Then a 5-second clip from the image with a slow push in, with audio. Then a two-sentence voice-over for the clip.” Watch the step list; each result lands in your project folder.
3
Fix one thing at a time
“Make the slate matte black” updates the image; “crop the video to 9:16” is a local edit. Regenerate a reply you dislike rather than re-describing everything.
5.3

Questions on a long PDF

1
Attach and digest
Drop the PDF, press Digest whole document on the card above the composer, and wait for the sections to finish; a local model works too, one call per section.
2
Ask overview questions
“What are the main findings?” is answered from the digest in context.
3
Then go to the page
“What does page 42 say about churn?” reads that page verbatim; “Where does it discuss retention?” searches every section and cites pages. The lookup answers appear as their own replies.
5.4

Quick edits by sentence

1
Attach the file
Drag the image, clip or recording onto the thread.
2
Say the edit plainly
“Crop it to 16:9.” “Resize to 1280x720.” “Trim the audio to 0:05 to 0:35.” “Convert the video to WebM.” These run locally with no model call and no cost; the result is a new file beside the original.
3
Stack them
“Crop to 1:1 and convert to WebP” runs as two tool steps in one turn.
5.5

A fully offline assistant

1
Pick a local tool-calling model
Install an Ollama tag flagged for tool calling (Gemma, Qwen, Llama, Granite) and select it as the chat model.
2
Turn Web off
Click the Web toggle so no search leaves the machine.
3
Keep the slots local too
Set Image to a GGML model and Speech to Supertonic TTS; crop, trim and convert are always local. Attached documents are read on the machine and go only to the local model.
5.6

Hands-free answers

1
Set a speech model
Under Models → More models, pick a Speech model and a voice you like; preview it in the Audio workspace.
2
Ask, then press the speaker
Read aloud under the reply voices it and plays it; press again to pause. Ask for “two sentences” when you want a short listen.
Part 6

Reference

6.1

Keyboard shortcuts

⌘ is Ctrl on Windows and Linux. The main guide lists every workspace’s shortcuts together.

Composer

Enter / Shift+Enter
Send a message / add a line
⌘V
Paste an image or a file to attach it
Esc
Cancel editing the last message

Conversations

Delete / Backspace
Delete the selected conversation (asks first)
⌘+ / ⌘- / ⌘0
Zoom the interface in, out, or back to 100%
6.2

Troubleshooting

  • “No chat model selected. Open Models and pick a Chat provider.” Set the chat slot; Auto needs at least one tool-capable provider.
  • “This chat model can’t make tool calls.” The picked model has no function calling; choose one the picker lists. The model still works in the Text workspace.
  • My favourite model is not in the picker. Replicate and Hugging Face models have no tool surface, and a few Runware tiers cannot finish a tool call there (Gemini works through OpenRouter). Use them in Text instead.
  • “No image model is selected yet. I’ve opened Models for you…” The slot for that kind is empty; pick one and ask again.
  • It asked “what kind of thing?” instead of generating. The request named no kind; say image, video, voice, music or effect, or answer yes to its offer.
  • “(Stopped after reaching the tool-call limit.)” Six tool rounds per message; split the job across two messages.
  • “The current chat model doesn’t accept images.” Switch to a vision-capable model to attach images; documents still work on any model.
  • “n files skipped”. Only PNG, JPG, GIF and WebP images and PDF, TXT, MD and HTML documents attach. “Couldn’t be read from where it was dragged”: save the file to disk first.
  • “Pages 1–30 of 300 seen”. The document is larger than the window; digest it, ask about a part, or use a larger model.
  • “Ran out of context window”. A thinking model reasoned into the window, or the history is long. Start a new conversation or pick a model with a larger window.
  • “Wait for the current reply to finish before attaching files.” Attach after the turn, or press Stop.
  • Web search found nothing or was slow. The first search of a session takes about ten seconds; engines are tried in turn and a consent page skips Google for a while. A local address or private network is refused by design.
  • “No workflow named …”. The reply lists the saved names; use one exactly, or save the workflow first.
  • “No text-to-speech model is selected.” Read aloud needs the Speech slot; press Open Models.
  • A crop did not happen locally. The deterministic matcher is English-only and needs a standalone ratio; in other languages the model runs the same edit tool.
  • “Stopped.” with an image already in the thread. That is intended: earlier rounds persist the moment they finish, and Stop only cancels what was still running.

One-time payment. Yours forever.

No subscriptions. No seats. No renewals. Buy CSuite once, future updates included.

Secure checkout via Stripe. Already have a license? Download the app