Chat

Chat is the front door. You tell Fluso what to do in plain English, and it does the work. The window looks like a messenger. It isn’t one.

​

What happens when you send a message

A small pause between hitting enter and seeing the first words come back. In that pause, Fluso gathers everything it has on the situation. The thread’s history. Your project’s memory. Your connected apps. The skills available. The files in scope. Your preferences. Then it picks tools and uses them. Sometimes one. Sometimes ten in a row. Ask it to summarise your unread emails and create tasks from the actionable ones. Behind the scenes, it queries Gmail, finds twelve unread, reads the five that look like requests, drafts three tasks with deadlines, drops them into your task list, and writes a short summary. You see the summary. The work is already done. Describe the outcome. Get the outcome. Review.

​

Asking for things well

Two things matter more than anything else. Specifics beat generalities. “Help with email” isn’t a request. “Summarise my unread emails and tell me which need a reply today” is. Fluso will do both. The first comes back with a clarifying question. The second comes back with a list. Outcomes, not steps. You don’t need to instruct Fluso the way you’d instruct a junior. “Search Gmail for messages from Sarah, read them, then tell me what she wants” is what a robot would type. “What did Sarah email me about?” is what a person would say. Both work. The second is faster.

​

Threads

A thread is one conversation. It remembers what you’ve said and what Fluso has said back, so a follow-up prompt picks up where you left off. After Fluso summarises your inbox, “reply to the one from Legal” makes sense because the summary is still in context. Start a new thread when you switch topic. The plus button at the top works, or you can ask for one in chat. Old threads stay in the sidebar. Pick any of them back up and Fluso has the full history.

​

Things you can do inside chat

Speak instead of typing. Tap the microphone in the input bar and dictate your request. Useful between meetings, on a walk, or whenever your hands are busy. Attach a file. Drag a PDF in and ask for a summary. Drop in an image and ask what’s in the chart. Hand it a CSV and tell it to make a deck from the data. Files Fluso creates appear as attachments in the reply. Work with files in your workspace. Read a report, write a markdown file, append to an existing one. Use any connected app as part of an answer. Pull the latest message from Sarah, search for a Slack thread, list open PRs that need review.

​

A few habits

• One topic per thread. Switching subjects mid-thread blurs the context Fluso uses. The cost of starting a new thread is zero.
• Switch into a project when you’re working on something specific. Project context tightens the answers. Without it, Fluso draws on everything.
• Don’t fight clarifying questions. If Fluso asks “Which project?” or “What format?”, answer it. The back-and-forth is faster than guessing on its behalf.

​

Next

For the rest of the primitives, see Connectors, Skills, Tasks, and Memory.