The chat is where you and your colleague work together. Each conversation is a session that lives in its own tab, with full history, files, and the colleague’s accumulated memory.Documentation Index
Fetch the complete documentation index at: https://docs.eluu.ai/llms.txt
Use this file to discover all available pages before exploring further.
What a session is
A session is one continuous conversation with one colleague. You can:- Run as many sessions as you want, with as many colleagues as you want, in parallel.
- Reopen a session days later and pick up where you left off.
- See every step the colleague took — tool calls, thoughts, files written.
- Pause and resume any time.
What you can do in a chat
A few things you can ask a colleague to do, by way of example:| Ask | What happens |
|---|---|
Summarise the last 20 emails in my inbox | Calls Gmail tools, reads the messages, writes a summary back. |
Build a dashboard of our open Salesforce opportunities | Calls Salesforce, builds a view inline, keeps it live. |
Look at this file and tell me what's wrong (with attachment) | Reads the attached file, runs analysis, replies. |
Find five companies similar to Acme and draft outreach for each | Researches, drafts five emails, optionally schedules them in Gmail. |
Run this every weekday at 8am NYC time | Turns the conversation into a job. |
Anatomy of a chat
- Tab strip — every open session, drag to reorder.
- Message list — your messages, colleague messages, tool calls (collapsible), thinking sections, inline views, file cards.
- Step plan header (when shown) — the colleague’s current todo list with progress.
- Composer — your input area. See the composer reference.
What “thinking” is
Some messages have a small collapsed “Thinking…” block above the response. Click it to expand the colleague’s reasoning trace. This is the model thinking out loud about the problem before it answers. The more thinking the colleague does, the better it tends to handle hard problems — at the cost of being slower. You can dial this with the Thinking level picker. See Models and thinking.Tool calls
When a colleague calls a tool (sends an email, reads a row from Sheets, opens a file), it shows up as a card in the chat. Each card shows:- Which tool ran.
- The input the colleague sent.
- The output it got back.
- Whether it succeeded, failed, was blocked, or is awaiting approval.
Inline views and files
When the response is structured enough to be a dashboard, the colleague builds a view inline. You can interact with it right there or click into the persistent version. When the colleague writes a file, a card for that file shows up in the chat. Click to open the Hard Drive viewer.Pause anytime
If a colleague is going down the wrong path, click the pause button on the composer. The colleague stops, you see what it had so far, and you can:- Type a new message to redirect (sending auto-resumes).
- Click resume to keep going.
- Just close the tab — the session is saved.
Multi-tab — parallel work
You can have many sessions open at once across many colleagues. Each session runs in its own backend sandbox, so they don’t interfere. Tabs reorder by drag. Click the + to open a new chat. Closing a tab doesn’t end a running task — your colleague keeps going. Reopen later and the history is there.Sessions list
To find an old chat, open All sessions in the sidebar. The dialog shows every session you’ve had, with rename, delete, and label actions.Where to next
The composer reference
Every control in the input area, with limits and shortcuts.
Slash commands
Pre-packaged playbooks you trigger with
/.Pause and resume
Stop and restart a colleague mid-task.
The mental model
How sessions, jobs, views, and files fit together.