# Micromeet Cowork documentation (Cowork 0.1.41) Source: https://docs.micromeet.ai/getting-started/what-is-cowork.html # What Is Cowork Micromeet Cowork is your AI coworker for everyday work: one app where people, AI and the systems you use every day work together. It is not tied to one industry. In one window you have: - **AI chat** — tell the AI what result you want. It plans, operates web pages, reads and writes files, connects to other systems, and delivers finished work. - **A browser** — open any website in tabs, as in a normal browser. - **Your files** — the AI works in a folder you choose and saves what it makes there. ## Working together - **You and the AI** — every step the AI takes is shown in the chat, so you can follow, change direction, stop or take over at any time. Routine steps run on their own. Writing through a website function and running a skill's script always wait for your approval; on web pages, the AI is told to ask before anything it cannot undo. See [When the AI asks you](https://docs.micromeet.ai/getting-started/workspaces-and-approvals.md#when-the-ai-asks-you). - **AI and AI** — AI coworkers for different kinds of work each have their own instructions and skills; big tasks are split among several of them. - **You and your team** — skills and AI coworkers can travel with a workspace folder, and your institution can publish shared skills, so the team works the same way. Work you do with the AI once can become a skill, so the next time it is done the same way. ## In healthcare **Micromeet Care Workspace**, the solution for healthcare institutions, includes Cowork: it adds the shared workbench for patients, check-ups, reports and staff. Cowork is also available on its own. ## Before you start - Cowork runs on macOS (Apple Silicon and Intel) and Windows (x64). - The interface is available in English, Bahasa Indonesia, Simplified Chinese and Traditional Chinese. - You need a Micromeet account to use the AI chat and Care Workspace. Websites can be browsed without signing in. These docs are the Cowork manual for everyone who uses it, inside Micromeet and out. The line under each page title says who the page is for: everyone, institutions that use Care Workspace, or builders who make skills, extensions, mini apps and packages. Next: [Quickstart](https://docs.micromeet.ai/getting-started/quickstart.md). --- Source: https://docs.micromeet.ai/getting-started/quickstart.html # Quickstart Install Cowork, sign in, and hand the AI its first real piece of work. It takes about ten minutes. ## Before you begin - A computer running macOS (Apple Silicon or Intel) or 64-bit Windows 10 or 11 - A Micromeet account. If you do not have one yet, ask your institution administrator for an invitation ## 1. Install Cowork 1. Open [crms.micromeet.ai/#/download](https://crms.micromeet.ai/#/download) and click **Download** on the card marked **Detected**. 2. On macOS, open the `.dmg` file and drag Micromeet Cowork into **Applications**. On Windows, run the `.exe` file. 3. Open Cowork. Cowork updates itself from then on. See [Install and Update](https://docs.micromeet.ai/getting-started/install-and-update.md) for details. ## 2. Sign in 1. In the chat panel on the left, choose your **Region**: **Singapore**, **Hong Kong** or **Indonesia**. 2. Enter your **Email** and **Password**, or switch to a verification code and click **Send code**. 3. Accept the Privacy Policy and Terms & Conditions and click **Sign in**. 4. If your account belongs to more than one institution, choose one and click **Continue**. > **Not sure which region** > Use the region your institution's administrator told you. A wrong region shows up as a wrong password or "account not found". ## 3. Give the AI a task 1. Click **New chat** at the top of the chat. 2. An empty chat shows **Start here** with a few ready-made tasks. Under **You can also ask me to…** click an example to put it in the input box, edit it, then send. **Show more** shows other examples. 3. Or type your own request and press **Enter**. Use **Shift+Enter** for a new line. 4. Watch the steps appear in the chat as the AI works. When it shows a card with a question or an approval, answer it there. A good first request names the result you want and where to find what it needs. For example: ```text Open the folder I attached, read the three meeting notes, and write a one-page summary of the decisions and who owns each next step. Save it as summary.md. ``` You can add instructions while it works, or click **Stop** to take over. See [Steering, Stopping and Taking Back](https://docs.micromeet.ai/chat/steering.md). ## Next steps - [How Cowork Works](https://docs.micromeet.ai/getting-started/how-cowork-works.md): Skills, AI coworkers, workspaces and how the AI decides when to ask you - [Give Clear Instructions](https://docs.micromeet.ai/guides/clear-instructions.md): Requests that get the result you want the first time - [Common Workflows](https://docs.micromeet.ai/guides/common-workflows.md): Complete examples, from request to result - [Build Your First Skill](https://docs.micromeet.ai/skills/first-skill.md): Turn a job you did once into a method the AI repeats --- Source: https://docs.micromeet.ai/getting-started/how-cowork-works.html # How Cowork Works You tell the AI the result you want. It plans the work, uses tools to carry it out step by step, and shows every step in the chat so you can follow, steer or take over. ## The layers Cowork is built in layers. Each one has its own page: | Layer | In one line | Read more | |---|---|---| | **Skills** | Written methods for one kind of task. When a request matches, the AI follows the method | [What Skills Are](https://docs.micromeet.ai/skills/what-are-skills.md) | | **Workspace and its rules** | The folder the AI works in, and the rules that apply to every chat there | [Workspaces, Rules and Approvals](https://docs.micromeet.ai/getting-started/workspaces-and-approvals.md) | | **Approvals** | Which steps run on their own and which wait for you | [Workspaces, Rules and Approvals](https://docs.micromeet.ai/getting-started/workspaces-and-approvals.md#when-the-ai-asks-you) | | **AI coworkers** | A setup for one kind of work: instructions and the skills it uses, named by its job. A package bundles everything one job needs; an institution switches it on for a team and the team works with it as an AI coworker | [Your AI Coworkers](https://docs.micromeet.ai/ai-employees/employee-list.md) | | **Models** | The AI model that thinks and answers, chosen per chat | [Models and Reasoning Effort](https://docs.micromeet.ai/chat/models.md) | Where the words in these docs differ from the names in the app, see [Terms and Interface Names](https://docs.micromeet.ai/reference/glossary.md). ## What happens when you send a request 1. **The AI reads your request** together with the chat so far, the files you attached and the workspace rules. 2. **It looks for a matching skill.** If one fits, it follows that method instead of working it out from scratch. 3. **It works in steps.** Each step uses a tool: open a page, read a file, click a button, call a website, run a script. Each one appears in the chat. 4. **It asks you when it should.** Reading and looking things up run on their own. Writing through a website function and running a skill's script always wait for your approval; on web pages, the AI is told to ask before anything it cannot undo. See [When the AI asks you](https://docs.micromeet.ai/getting-started/workspaces-and-approvals.md#when-the-ai-asks-you). 5. **It delivers the result** in the chat, and saves files it made in the workspace. You can type while it works to change direction, or click **Stop**. See [Steering, Stopping and Taking Back](https://docs.micromeet.ai/chat/steering.md). ## Where skills come from | Place | Who has it | |---|---| | Built into Cowork | Everyone | | This computer | Only you, in every workspace | | A workspace folder | Everyone who opens that folder. It travels with the folder | | Published by Micromeet or your institution | Everyone in that scope. Updated automatically | AI coworkers can be saved on this computer or in a workspace folder. This is how a team works the same way: put a project's skills, AI coworkers and rules in its workspace folder, and everyone who opens it gets them. ## Working with several AIs For big jobs the AI can split the work among helper agents that run in the background at the same time, for example checking many files in parallel. You see them in a task bar above the input box and can pause or stop them. See [Workflows and Background Agents](https://docs.micromeet.ai/skills/workflows.md). ## Next steps - [Workspaces, Rules and Approvals](https://docs.micromeet.ai/getting-started/workspaces-and-approvals.md): Where the AI works, what it follows and when it asks you - [Give Clear Instructions](https://docs.micromeet.ai/guides/clear-instructions.md): How to ask so the AI gets it right the first time - [Build Your First Skill](https://docs.micromeet.ai/skills/first-skill.md): Turn a job you did once into a method the AI repeats --- Source: https://docs.micromeet.ai/getting-started/workspaces-and-approvals.html # Workspaces, Rules and Approvals The workspace sets where the AI works and what rules it follows there. Approvals set which of its steps wait for you. Together they are the boundary around everything the AI does. ## The workspace The workspace is a folder on your computer. The AI reads, searches, creates and edits files there, and saves what it produces there. Each chat remembers its workspace. See [Choose a Workspace](https://docs.micromeet.ai/files/workspace.md). A workspace folder can carry more than files: | In the folder | What it does | |---|---| | `AGENTS.md` at the top of the folder | Rules the AI follows in every chat in this workspace | | `.agents/skills/` | Skills for everyone who opens the folder | | `.agents/agents/` | AI coworkers for everyone who opens the folder | Because these travel with the folder, a shared project folder gives the whole team the same rules, skills and AI coworkers. ## Rules for a workspace Put an `AGENTS.md` file at the top of the workspace folder and write the rules in plain words, for example where drafts go, which files are authoritative, or what must never be sent outside. Cowork adds it to the AI's instructions for chats in that workspace. - Only the `AGENTS.md` at the top of the workspace is read. Files with the same name in subfolders are not. - A chat in another workspace does not see these rules. - Change the file whenever you like; the next message you send uses the new version. ## When the AI asks you Not every step needs a person. Cowork decides step by step: | Kind of step | What happens | |---|---| | Reading a page, opening or searching files, looking something up | Runs on its own | | Clicks, typing and filling in forms on web pages | No approval card. The AI is told to stop and ask you before anything it cannot undo, such as submitting, paying, deleting or sending a message, when your request and the page do not already settle it | | A script the AI runs inside a web page | No approval card. The chat shows afterwards what ran: the tab, the purpose the AI gave and the script itself | | Calling a website function that writes data (see [API Doc](https://docs.micromeet.ai/capture/api-doc.md)) | An approval card, every time | | Running a skill's script on your computer | An approval card, every time | When it asks, a card marked **Waiting on you** appears in the chat. Nothing happens until you answer. See [Tool Steps, Approvals and Decisions](https://docs.micromeet.ai/chat/tool-steps-and-approvals.md). To be asked more often, say so in the request or in the workspace rules, for example "ask me before you submit or send anything" or "do not change any data, only report". See [Give Clear Instructions](https://docs.micromeet.ai/guides/clear-instructions.md). ## What your institution sets If your account belongs to an institution, some things come from it rather than from you: - **Institution skills**: published by your institution and updated automatically. You can read them but not change them; to adapt one, copy it into your own skills. - **Sign-in and region**: your institution and region decide which account and data you work with. See [Sign In and Regions](https://docs.micromeet.ai/getting-started/sign-in-and-regions.md). ## Next steps - [What Skills Are](https://docs.micromeet.ai/skills/what-are-skills.md): Where skills come from and how the AI picks one - [Terms and Interface Names](https://docs.micromeet.ai/reference/glossary.md): The words these docs use, and what the app calls them --- Source: https://docs.micromeet.ai/getting-started/install-and-update.html # Install and Update Install Cowork from the download page; after that it updates itself. ## When to use it When you set Cowork up on a new computer, or want to know how updates arrive. ## How to use it ### Install 1. Open the download page: [crms.micromeet.ai/#/download](https://crms.micromeet.ai/#/download). No sign-in is needed. 2. Find the card for your computer. The one marked **Detected** matches the computer you are using. 3. Click **Download**. 4. Open the installer: - **macOS**: open the `.dmg` file and drag Micromeet Cowork into **Applications**. - **Windows**: run the `.exe` file and follow the steps. ### Update Cowork checks for new versions by itself while it is running and downloads them in the background. - While a version downloads, the right end of the address bar shows **Downloading** with its progress. - When it is ready, an **Update** button appears there. Click it: Cowork restarts on the new version. To see which version you have, open **Settings › About** (see [About and Updates](https://docs.micromeet.ai/settings/about.md)). --- Source: https://docs.micromeet.ai/getting-started/sign-in-and-regions.html # Sign In and Regions You sign in inside the chat panel on the left of the window. ## When to use it When you sign in for the first time, switch institution, or cannot sign in. ## How to use it 1. **Region**: choose the region your institution uses — **Singapore**, **Hong Kong** or **Indonesia**. 2. **Email**: enter the email of your Micromeet account. 3. Enter your **Password**, or switch to a verification code and click **Send code** to get one by email. 4. Accept the Privacy Policy and Terms & Conditions. 5. Click **Sign in**. 6. If your account belongs to more than one institution, choose one in **Choose an institution** and click **Continue**. ## Good to know - **First sign-in**: you may be asked to **Set your password**. If your account requires a password, you must set one before you continue. - **Forgot password?** Click it under the Sign in button and reset the password with a code sent to your email. - **Without signing in** you can still browse websites in tabs. The AI chat and Care Workspace need you to sign in. - **Account menu**: click your avatar at the right end of the address bar. It shows your institution and email, and has **Change password** and **Log out**. --- Source: https://docs.micromeet.ai/getting-started/interface-tour.html # Interface Tour ```text ┌──────────────────────────────────────────────────────────────────┐ │ Tabs: AI Employees · Care Workspace · Omni Preview · yours · + │ │ ← → ↻ Address bar Settings and more · Avatar │ ├──────┬───────────────────────┬───────────────────────────────────┤ │ Rail │ Chat │ Page of the current tab │ │ │ │ (website, Care Workspace, files…) │ └──────┴───────────────────────┴───────────────────────────────────┘ ``` ## Top: tabs and address bar - **Fixed tabs**: **AI Employees**, **Care Workspace** and **Omni Preview** are always there (see [Terms and Interface Names](https://docs.micromeet.ai/reference/glossary.md) for how the app labels them). Your own tabs follow; **+** opens a new tab. - **Address bar**: type a web address or search words. - **Settings and more** (the slider icon on the right): opens **Settings**, **Browser history** and **Downloads**. - **Avatar**: your account, **Change password** and **Log out**. - **Update** appears at the right end when a new version is ready. ## Left: the chat panel The narrow **rail** on the far left has, from top to bottom: - **Show chat / Hide chat** — open or fold the chat. When folded, only the rail stays. - **Scheduled tasks** (clock) — your scheduled tasks and their chats. - **AI Employees** — opens the AI Employees page. - Your AI coworkers — click one to chat with it. The top of the chat has **Sessions** (your chat list), the chat title, **New chat** and **More** (**Profile**, **Archive**, **Tasks**, **Archived Chat**). ## Right: the page The page of the tab you selected: a website, Care Workspace, a file preview or Settings. --- Source: https://docs.micromeet.ai/guides/common-workflows.html # Common Workflows Complete examples, from the request you type to the result you get. Each one uses only what Cowork does today. Change the details to fit your own work. ## Summarise a folder of documents You have a folder of reports, notes or contracts and need the main points in one place. 1. Click **Choose workspace** at the bottom left of the input box and pick the folder. 2. Ask for the result and its shape: ```text Read every document in this folder. Write a summary with one section per document: its date, the three most important points and any open question. End with a list of actions and owners. Save it as summary.md. ``` 3. The AI lists the folder, reads each file (PDF, Word, Excel, PowerPoint and scanned PDFs all work) and writes `summary.md` into the folder. 4. Open the file from the workspace chip, or ask the AI to change the format. See [Files and Documents the Agent Reads](https://docs.micromeet.ai/files/reading-files.md). ## Pull information out of a website You need data from a website you use every day, for example a list of this month's orders. 1. Open the website in a tab and sign in as usual. 2. Ask: ```text On the orders page, collect all orders for this month: date, order number, customer and total. Do not change anything. Put the result in orders.csv in the workspace. ``` 3. The AI opens its own tab in the background and reads the pages. Your tab stays in front. 4. If it reaches a sign-in or verification page it cannot pass, it stops and tells you. Do that step in the tab, then tell it to continue. For large amounts of data, ask the AI to write a crawl script instead: it is faster and continues where it stopped if the connection drops. See [Crawl Scripts](https://docs.micromeet.ai/capture/crawl-scripts.md). ## Update records on a website, safely You need to change a batch of entries, such as marking a list of orders as shipped. 1. Ask for the plan first: ```text For each order number in the attached list, set the status to Shipped on the orders page. Before you change anything, tell me how you will do it, then do the first one and stop so I can check. ``` 2. Check the first change in the tab yourself. 3. Tell the AI to continue with the rest. To check each change yourself, say "ask me before each save"; the AI then waits for you on a card marked **Waiting on you** every time. See [Tool Steps, Approvals and Decisions](https://docs.micromeet.ai/chat/tool-steps-and-approvals.md). ## Make a weekly job run by itself A job you do every week, such as a Monday summary, can run without you starting it. 1. Do the job once in a chat, until the result is right. 2. Ask: "Turn what we just did into a skill called weekly-summary". See [Build Your First Skill](https://docs.micromeet.ai/skills/first-skill.md). 3. Ask: "Every Monday at 9:00, run weekly-summary and save the result in the workspace". 4. Each run appears in its own chat under the clock (**Scheduled tasks**) on the rail. Scheduled tasks run only while Cowork is open. See [Scheduled Tasks](https://docs.micromeet.ai/skills/scheduled-tasks.md). ## Check many files at once You need the same check done on dozens of files, for example every contract in a folder for a missing clause. 1. Choose the folder as the workspace. 2. Ask: "Check every contract in this folder for a termination clause. Give me a table of the ones without it, with the file name". 3. For a job this size the AI may split the work among helper agents that run at the same time. A task bar above the input box shows each one, and you can **Pause** or **Stop** them. 4. When they finish, the AI combines their findings into one answer. See [Workflows and Background Agents](https://docs.micromeet.ai/skills/workflows.md). ## Start a job from a button on the website If you start the same jobs on the same website often, put a button on the website itself. 1. Open the website in a tab. 2. Ask: "Add a button to this site with: Run weekly-summary, Check today's orders". 3. A floating **micromeet** button appears on the page. It lists those jobs; click one and the AI starts it in the chat. See [Website Buttons (Injections)](https://docs.micromeet.ai/skills/injections.md). --- Source: https://docs.micromeet.ai/guides/clear-instructions.html # Give Clear Instructions The AI can only use what it can see. Most disappointing results come from a request that left out the result, the material, or the limits. A few habits fix almost all of them. ## Say the result, not only the first step Describe what "done" looks like: the output, its format and where it goes. | Instead of | Try | |---|---| | "Look at these invoices" | "Check each invoice in the attached folder against the price list and give me a table of the ones that don't match, with the difference" | | "Write something about the meeting" | "Write a one-page summary of the decisions and owners from meeting-notes.docx. Save it as summary.md in the workspace" | ## Point at the material Name the exact file, folder, page or record. Better still, put it in front of the AI: - **Files and folders**: attach them, or choose the folder as the workspace. See [Attachments, Images, Folders and Long Text](https://docs.micromeet.ai/chat/attachments.md). - **Web pages**: open the page in a tab first, or give the AI its address - **Long text**: paste it. A long paste becomes a **Pasted text** block, and the AI still receives all of it. ## Say what it must not do Limits keep the AI on track and spare you approval cards for things you never wanted: - "Do not change any data, only report." - "Only look at records from this month." - "Ask me before sending anything outside the company." ## Give it a way to check its work When there is a way to tell right from wrong, say it. The AI uses it to verify before it reports back: - "The totals must match the summary row on the last sheet." - "Every order number in the output must exist in the input file." - "Open the page after you save and confirm the new value shows." ## Break up big jobs, or let it plan first For a long or risky job, ask for the plan before the work: ```text Before you change anything, list the steps you will take and what each one touches. Wait for my OK. ``` Then approve, adjust, or ask it to start with one item so you can check the result. ## Steer as it goes You do not have to get everything right up front. While the AI works you can add instructions, correct it, or click **Stop** and take over. See [Steering, Stopping and Taking Back](https://docs.micromeet.ai/chat/steering.md). ## When you repeat yourself, make a skill If you find yourself typing the same long instructions again, the job deserves a skill. Do it once together with the AI, then ask "Turn what we just did into a skill". See [Build Your First Skill](https://docs.micromeet.ai/skills/first-skill.md). --- Source: https://docs.micromeet.ai/chat/conversations.html # Conversations and History Each conversation is a separate chat with its own history, model and workspace. ## What it is A chat is where you give the AI work and see every step it takes. Cowork starts with an empty **New chat** every time it opens; your earlier chats stay in **Sessions**. Each chat keeps its own model and workspace, so two chats can work on different projects at the same time. ## When to use it | Start a new chat when | Stay in the same chat when | |---|---| | The topic or project changes | You are refining the same result | | A long chat has drifted and you want a clean start | The AI needs what was said earlier | | You want a different model or workspace for this job | You are answering the AI's questions | ## How to use it | To | Do this | |---|---| | Start a new chat | Click **New chat** at the top of the chat, or press ⌘N (Windows: Ctrl+N) | | See your chats | Click **Sessions** (⌘L / Ctrl+L). A dot shows **Running**, **Unread reply** or **Waiting for your confirmation** | | Find a chat | In the list, click the search icon or press ⌘F / Ctrl+F, then type part of the title | | Rename a chat | Double-click its title at the top of the chat | | Archive a chat | Click the archive icon on its row, or **More › Archive**. A running chat shows **Stop and archive** | | Undo the last archive or rename | Press ⌘Z / Ctrl+Z outside the input box | | Bring back an archived chat | **More › Archived Chat**, select it, click **Restore** | | Delete a chat for good | Right-click its row › **Delete forever…**, or **Delete** in **Archived Chat** | ## Example You finish a supplier report in one chat and want to start on next week's schedule. Click **New chat**, choose the schedule's folder as the workspace, and ask. The report chat stays in **Sessions** with its history; open it again later to make changes. ## Limits and permissions - A new chat is saved only after you send its first message. - Archiving keeps all messages; it only takes the chat off the list. - **Delete forever…** cannot be undone. - Chats from scheduled tasks are not in **Sessions**; they are under the clock on the rail. See [Scheduled Tasks](https://docs.micromeet.ai/skills/scheduled-tasks.md). ## If something goes wrong | What you see | What to do | |---|---| | A chat says it can no longer restore its context | Start a new chat. The old messages stay readable | | The AI seems to have forgotten something from much earlier | Long chats are compacted. Repeat the detail, or start a new chat. See [Long Chats and Automatic Compaction](https://docs.micromeet.ai/chat/compaction.md) | | An archived or renamed chat is not where you expected | Press ⌘Z / Ctrl+Z outside the input box to undo the last change | ## Related - [Steering, Stopping and Taking Back](https://docs.micromeet.ai/chat/steering.md): Change direction while the AI works - [Choose a Workspace](https://docs.micromeet.ai/files/workspace.md): Give a chat its folder - [Models and Reasoning Effort](https://docs.micromeet.ai/chat/models.md): Pick the model for a chat --- Source: https://docs.micromeet.ai/chat/models.html # Models and Reasoning Effort Choose which AI model answers in a chat, and how long it thinks before it answers. ## What it is Every chat uses one language model (**LLM**), shown with the effort at the bottom right of the input box. Cowork offers Micromeet models as soon as you sign in, and can also use your own ChatGPT (Codex) or Claude account. Pictures use a separate **Image** model. ## When to use it | Change the model or effort when | Keep the default when | |---|---| | A job needs careful reasoning, such as a long analysis | Everyday tasks: summaries, tables, emails | | You want quicker answers for simple work | You are not sure; the default is chosen for most work | | You want to use your own Claude or ChatGPT subscription | | ## How to use it 1. Click the model name at the bottom right of the input box to open **Models**. 2. Under **LLM**, click a model for **this chat**. Use the search icon to find one by name. 3. Under **Image**, choose the model for pictures; this applies to **All chats**. 4. Next to the model, choose the effort: **Low**, **Medium**, **High**, **Max** or **Default**, depending on the model. Higher effort thinks longer and answers more slowly. 5. For **Codex** or **Claude**, sign in when asked: a **Login** button appears next to it, or sign in under **Settings › General › Models**. The gear icon (**Model settings**) opens that page. ## Example You ask for a quarterly sales analysis across several spreadsheets. Before sending, you switch this chat to a stronger model and set the effort to **High**. The answer takes longer but works through every sheet. For the next chat, a quick email draft, the default is enough. ## Limits and permissions - Each chat keeps its own model; changing it in one chat does not change the others. - The image model applies to all chats. - **Codex** and **Claude** use your own account and its limits. - You can change the model while the AI is working: the current answer finishes on the old model, and the next step uses the new one. ## If something goes wrong | What you see | What to do | |---|---| | The chat says your Codex or Claude session expired | Sign in again under **Settings › General › Models** | | A model you expect is not in the list | Use the search icon; if it is still missing, it is not available to your account | | Answers are too slow | Lower the effort, or choose a faster model for this chat | ## Related - [Conversations and History](https://docs.micromeet.ai/chat/conversations.md): Each chat keeps its own model - [Image Generation](https://docs.micromeet.ai/files/image-generation.md): Make pictures with the image model - [Sign-in Problems](https://docs.micromeet.ai/troubleshooting/sign-in-problems.md): Signing in to Claude or Codex --- Source: https://docs.micromeet.ai/chat/attachments.html # Attachments, Images, Folders and Long Text Give the AI the files, images, folders or long text it needs, right in the chat. ## What it is Attachments put material in front of the AI for one message: documents to read, images to look at, a folder to go through, or a long text you paste. They stay on your computer; the AI reads them from where they are. ## When to use it | Attach when | Use the workspace instead when | |---|---| | The AI needs one or a few files from somewhere else | The whole job is about one project folder | | You want it to look at a screenshot or a photo | The AI should also save its results next to the files | | You paste a long text, such as an email thread | | ## How to use it 1. Click **Attach files** next to the input box, drag files onto the chat (**Drop files to attach**), or paste files, images or a folder into the input box. 2. Each attachment shows as a card above the input box. Click an image card to preview it; hover over a card and click **×** to remove it. 3. Write what you want done with them, and send. What the AI does with each kind: | Kind | What it does | |---|---| | Documents (PDF, Word, Excel, PowerPoint, text and more) | Reads and summarises them | | Images | Looks at them, up to 20 at a time | | Folders | Lists what is inside and opens the files it needs | | Long text (more than about 1,200 characters or 20 lines) | Becomes a **Pasted text** block instead of filling the box; the AI still receives all of it | ## Example ```text [attach: supplier-contract.pdf, price-list.xlsx] Check whether the prices in the contract match the price list. List any item where they differ, with both prices. ``` The AI reads both files and replies with the items that differ. ## Limits and permissions - Up to 20 attachments per message. - Attachments stay on your computer; the AI reads them from where they are. - Scanned PDFs without text are read with text recognition; very large files are read in parts. - To have the AI save results next to the files, choose their folder as the workspace instead. ## If something goes wrong | What you see | What to do | |---|---| | The AI says it cannot read a file | Check the type in [Files and Documents the Agent Reads](https://docs.micromeet.ai/files/reading-files.md), or save it as PDF and attach again | | You attached the wrong file | Hover over its card and click **×** before sending, or tell the AI which file to ignore | | A long paste filled the box instead of becoming a block | It was shorter than the limit; it is still sent in full | ## Related - [Choose a Workspace](https://docs.micromeet.ai/files/workspace.md): Work with a whole folder and save results there - [Files and Documents the Agent Reads](https://docs.micromeet.ai/files/reading-files.md): Which file types it can read and write - [Give Clear Instructions](https://docs.micromeet.ai/guides/clear-instructions.md): Say what to do with what you attached --- Source: https://docs.micromeet.ai/chat/voice-input.html # Voice Input Speak instead of typing. Your words are turned into text in the input box; you check them and send. ## When to use it When speaking is faster than typing, for example a long request or notes on the move. ## How to use it 1. Click the microphone (**Voice scribe**) left of the Send button. 2. Speak. The box shows **Recording** and the time — up to 5 minutes. 3. Click **Stop and transcribe**. After **Transcribing…** the text appears in the input box. 4. Edit if needed, then send. ## Good to know - You must be signed in to Cowork. - The first time, allow microphone access when your computer asks. If you said no, allow it in your system settings. - Cancelling or getting no speech leaves your draft unchanged. --- Source: https://docs.micromeet.ai/chat/steering.html # Steering, Stopping and Taking Back While the AI works you can add instructions, stop it, or take back your last message. ## What it is You do not have to wait for the AI to finish. Anything you send while it works is taken into account at its next step. **Stop** ends the current work, and a message the AI has not acted on yet can be taken back. ## When to use it | Do this | When | |---|---| | Add an instruction | You remembered a detail, or want to narrow the job | | Stop | It is clearly going the wrong way, or you want to do the rest yourself | | Take back | You sent something by mistake, or too early | ## How to use it 1. **Add an instruction**: type and send while the AI is working. Your message shows **Queued** and then **Steering**, and the AI takes it into account at its next step. 2. **Stop**: click **Stop** (where the Send button is). The chat shows **Stopped.** Everything done so far stays in the chat. 3. **Take back**: hover over your message and click the **Take back** icon (a curved arrow) under it. The message goes back into the input box. ## Example You asked for a report on last month's orders. While it works you notice it is including cancelled orders, so you send "leave out cancelled orders". The message shows **Steering**, and the AI changes course at its next step without starting over. ## Limits and permissions - A message still **Queued** can always be taken back. - Your latest sent message can be taken back only if the AI has not started answering or using tools yet, for example while it is still thinking, or right after you clicked **Stop**. It is then removed from the chat and the AI forgets it. - **Stop** does not undo what was already done, such as a file already saved or a form already submitted. ## If something goes wrong | What you see | What to do | |---|---| | The **Take back** icon is missing | The AI already started answering; send a correction instead | | The AI ignored your added instruction | It takes it at the next step; if the step was long, repeat it after it finishes | | You stopped too early | Send "continue" and say where to pick up | ## Related - [Tool Steps, Approvals and Decisions](https://docs.micromeet.ai/chat/tool-steps-and-approvals.md): Follow each step the AI takes - [Give Clear Instructions](https://docs.micromeet.ai/guides/clear-instructions.md): Fewer corrections from the start - [Offline Queue and Retries](https://docs.micromeet.ai/chat/offline-and-retry.md): Messages sent without a connection --- Source: https://docs.micromeet.ai/chat/tool-steps-and-approvals.html # Tool Steps, Approvals and Decisions Every action the AI takes shows as a step in the chat, and when it needs you, it asks on a card and waits. ## What it is While it works, the AI shows each action (opening a page, reading a file, calling a site) as a step. When an action needs your answer, a card appears and the AI waits. Which kinds of action wait for you is defined once, in [When the AI asks you](https://docs.micromeet.ai/getting-started/workspaces-and-approvals.md#when-the-ai-asks-you). ## When to use it | Look at the steps when | Answer a card when | |---|---| | You want to check how the AI reached a result | A card marked **Waiting on you** appears | | Something takes longer than expected | The AI asks you to choose between options | | You want to stop it early because it went the wrong way | | ## How to use it 1. Only the latest step is shown; click **earlier steps** to see the rest. The status line under the steps says what the AI is doing now, for example **Thinking…**. 2. When the AI asks, a card marked **Waiting on you** appears and the question opens on a panel above the input box. 3. Read what the card says the action will do. Click the button that carries out the action, or the other button to refuse. 4. For a question with options, pick one or type your own answer. 5. The answer is recorded on the card (**Answered**). The AI continues only after you answer. ## Example You ask the AI to update a record through a website's own function. Before it writes, a card shows which record and what will change. You click the button to go ahead; the card shows **Answered**, and the AI reports the result. ## Limits and permissions - Writing through a website's function and running a skill's script on your computer always ask on a card. - Clicks, typing and scripts inside web pages do not show an approval card. The AI is told to ask before anything it cannot undo; scripts it runs in a page are recorded in the chat afterwards. - To be asked more often, say so: "ask me before you submit anything". ## If something goes wrong | What you see | What to do | |---|---| | The AI is waiting and nothing happens | Look for a card marked **Waiting on you**; it may be on the panel above the input box | | You refused by mistake | Tell the AI to try again; it asks once more | | The AI did something you expected it to ask about | Add the rule to your request or to the workspace rules. See [Workspaces, Rules and Approvals](https://docs.micromeet.ai/getting-started/workspaces-and-approvals.md) | ## Related - [Workspaces, Rules and Approvals](https://docs.micromeet.ai/getting-started/workspaces-and-approvals.md): Which steps run on their own and which wait - [Questionnaires](https://docs.micromeet.ai/chat/questionnaires.md): When the AI needs you to check many items at once - [Steering, Stopping and Taking Back](https://docs.micromeet.ai/chat/steering.md): Change direction or stop --- Source: https://docs.micromeet.ai/chat/questionnaires.html # Questionnaires When the AI needs you to go through many items — for example to check a batch of records — it sends a questionnaire instead of asking one by one. ## When to use it When the AI needs your answer on many items at once, such as checking a batch of records. ## How to use it 1. A questionnaire card appears in the chat. Click **Open**: it opens in its own tab. 2. **Questions** on the left lists every question. Filter with **All** / **Unanswered**, or use **Search questions**. 3. Answer each question. Options marked **(Recommended)** are suggestions — you decide. Some questions let you add files. 4. When every question is answered, click **Continue**. Cowork goes back to the chat and tells the AI you are done. ## Good to know - You can answer at your own pace; answers are saved as you go. - **Back to chat** returns to the conversation without handing in. --- Source: https://docs.micromeet.ai/chat/slash-commands.html # Slash Commands Type **/** in the input box to see the list of commands. Keep typing to filter, then press **Enter**. ## When to use it When you want to run a command or a skill directly, without describing it in words. ## How to use it | Command | What it does | |---|---| | `/manual` | Ask how to use Cowork. | | `/menu` | List the Settings tabs; `/menu models` opens one. | | `/archive` | Archive this chat. | | `/compact` | Compact this chat now — see [Long Chats and Automatic Compaction](https://docs.micromeet.ai/chat/compaction.md). | | `/clear` | Permanently delete this chat's messages and start over in the same chat. | | `/workflow` | List workflows, or run one: `/workflow `. | | `/shortcut` | See, add, change or delete your own commands. | Each skill you have also appears as `/name`. See [What Skills Are](https://docs.micromeet.ai/skills/what-are-skills.md). --- Source: https://docs.micromeet.ai/chat/compaction.html # Long Chats and Automatic Compaction A model can only keep a limited amount of conversation in mind. So that a chat can go on as long as you need, Cowork **compacts** it automatically: when the chat gets close to the model's limit, the older part is replaced by a summary, and the latest part is kept in full. ## When to use it When a chat has become very long and you want to keep going in it. ## How to use it ### What you see - The status line shows **Compacting conversation…** while it runs, then **Compacted conversation automatically.** - Messages you send meanwhile wait and go out in order when it finishes (**New messages wait until compaction finishes.**). - All messages stay visible in the chat. Only what the model reads is shortened. ### Compact by hand Type `/compact` to compact now, for example before starting a new part of a long task. If there is too little old history, Cowork says there is nothing to compact yet. ## Good to know - After compaction the AI keeps the summary and recent work, but may lose small details from long ago. If a detail matters, repeat it, or start a new chat for a new topic. - Clicking **Stop** during compaction cancels it; nothing is changed. --- Source: https://docs.micromeet.ai/chat/offline-and-retry.html # Offline Queue and Retries Cowork keeps your messages safe when the network drops, and tells you what to do when something fails. ## When to use it When the network drops or a message fails while you work. ## How to use it ### No network If you send while the network is down, the message shows **Offline — sends automatically when the connection is back**. Up to 10 messages can wait; after that you are asked to wait for the earlier ones. ### Short outages If the connection drops while the AI is working, the status line shows **Connection lost, reconnecting** and retries by itself. ### When something fails - If the chat says the conversation was interrupted, send your message again. - If it says your session expired, sign in again (for Codex or Claude: **Settings › General › Models**). - If a chat says it can no longer restore its context, start a new chat. The old messages stay readable. See also [Sign-in Problems](https://docs.micromeet.ai/troubleshooting/sign-in-problems.md). --- Source: https://docs.micromeet.ai/files/workspace.html # Choose a Workspace The workspace is the folder on your computer that the AI works in: it reads, searches, creates and edits files there, and saves what it produces there. ## What it is Each chat works in one folder. Everything the AI makes goes there by default, and the folder can carry rules (`AGENTS.md`), skills and AI coworkers that apply to everyone who opens it. See [Workspaces, Rules and Approvals](https://docs.micromeet.ai/getting-started/workspaces-and-approvals.md). ## When to use it | Choose a workspace when | You can skip it when | |---|---| | The job is about files in one project folder | You only ask a question or work on a web page | | You want the results saved next to the project | You attach the one or two files the AI needs | | The folder has rules or skills the AI should follow | | ## How to use it 1. At the bottom left of the input box, click **Choose workspace**. 2. Pick a folder. 3. The folder shows as a chip with three parts: the folder name (click to open it in Omni Preview), switch to another folder, and clear. ## Example Choose your `Q4 Tenders` folder as the workspace and ask: "List every tender in this folder with its deadline, and save the list as deadlines.xlsx." The AI reads the files there and saves `deadlines.xlsx` into the same folder. ## Limits and permissions - Each chat remembers its workspace. A new chat starts with the folder you picked last. - Without a workspace, the AI uses a default folder of the app. - Files outside the workspace can still be attached or opened, but the workspace is where the AI saves by default. - The AI changes your files only for the task you gave it. ## If something goes wrong | What you see | What to do | |---|---| | The AI saved a file somewhere unexpected | Check the workspace chip; choose the right folder and ask it to move the file | | The AI does not follow the folder's rules | Make sure `AGENTS.md` is at the top of the folder, not in a subfolder | | You cannot find what the AI made | Click the folder name on the chip to open it in Omni Preview | ## Related - [Workspaces, Rules and Approvals](https://docs.micromeet.ai/getting-started/workspaces-and-approvals.md): What a workspace folder can carry - [Files and Documents the Agent Reads](https://docs.micromeet.ai/files/reading-files.md): Which file types it can read and write - [Omni Preview](https://docs.micromeet.ai/files/omni-preview.md): Browse and preview the workspace --- Source: https://docs.micromeet.ai/files/omni-preview.html # Omni Preview Omni Preview is the third fixed tab. It shows the files of your workspace and previews them — documents, spreadsheets, PDFs, images, web pages, Markdown and code. ## When to use it When you want to browse the workspace, open what the AI made, or point it at a file. ## How to use it ### Left side - **Project** — the folder tree of the workspace. **Recents** — files you opened recently. - **Bookmarks** — right-click a file or folder › **Add bookmark** to keep it at the top. - No workspace yet? Click **Choose workspace**. ### Search Type in **Search files and contents…**. Choose **All** or **Current Directory**. Results come in two lists: **Contents** (text inside files) and **Files** (file names). ### Right-click a file or folder **Preview**, **Open in system app**, **Reveal in folder**, **Copy Path**, **New Folder**, **Rename…**, **Delete…**, **Search in this folder**, and **Add bookmark**. On an HTML preview, right-click › **Copy Element for Agent** works as on web pages (see [Copy Element for Agent](https://docs.micromeet.ai/browser/copy-element.md)). ### Ask the AI to show a file Say "show me the report" and the AI opens the file in Omni Preview. --- Source: https://docs.micromeet.ai/files/file-preview.html # File Preview A file **outside** your workspace opens in its own **File Preview** tab instead of Omni Preview. Each file gets its own tab. ## When to use it When you open a file that is not in the workspace. ## How to use it This happens when you click such a file in the chat — a file link in a reply, or an attachment — or when the AI shows you one. The address bar shows the file's path. Type another file path to show that file instead, or a web address to turn the tab into a web page. ### File links in replies Click a file link in an AI reply to preview it. Right-click it for **Open**, **Open in default app**, **Copy path** and **Reveal in Finder** (Windows: Explorer). --- Source: https://docs.micromeet.ai/files/reading-files.html # Files and Documents the Agent Reads The AI can read files you attach and files in your workspace: ## When to use it When you want to know whether the AI can read or write a kind of file before you give it. ## How to use it | Kind | Examples | |---|---| | Documents | PDF, Word, PowerPoint, OpenDocument, RTF, EPUB | | Spreadsheets | Excel, CSV | | Text and code | TXT, Markdown, JSON, HTML, source code | | Images | PNG, JPG, WEBP and more — it looks at them | Scanned PDFs without text are read with text recognition. Large files are read in parts. It can also **write** files in the workspace — reports, tables, documents — and change existing ones when you ask. Changes to your files happen only for the task you gave it. --- Source: https://docs.micromeet.ai/files/image-generation.html # Image Generation Ask in a chat: "Make a poster for our team event" or "Change the background of this photo" (with the photo attached). The image appears in the chat. ## When to use it When you need a picture, such as an illustration, a draft visual or an icon. ## How to use it ### Choose the image model In the model picker, the **Image** column applies to all chats: - **Micromeet**: **Wan 2.7 Image** and **Wan 2.7 Image Pro** — ready once you are signed in. - **Codex**: **GPT Image 2** — needs your ChatGPT account; click **Login** next to it. ## Good to know - To edit, attach up to 8 reference images. - Images are saved on your computer. Say where if you want them in a specific folder. --- Source: https://docs.micromeet.ai/browser/agent-browsing.html # Let the Agent Use Web Pages The AI can read and work on websites in Cowork's tabs, signed in as you: open pages, click, fill in forms and collect what it finds. ## What it is Cowork's tabs are a full browser. When a job needs a website, the AI opens the page in a tab of its own, reads it, and acts on it step by step, the way you would. It uses the sign-in you already have in that tab, so it sees what you can see and nothing more. For data, the AI first looks for the website's own functions (see [API Doc](https://docs.micromeet.ai/capture/api-doc.md)); it is faster and steadier than clicking. It works through the page itself when there is no such function, or when the job is the page: filling in a form, pressing a button, checking what shows. ## When to use it | Good fit | Better another way | |---|---| | A website you use every day that has no export or report for what you need | One-off reading of a public page: paste the address or the text into the chat | | Repeating the same steps across many records | Very large amounts of data: ask for a [crawl script](https://docs.micromeet.ai/capture/crawl-scripts.md) | | Checking or updating records in a system you sign in to | A system that blocks automated use, or needs a code from your phone at every step | ## How to use it 1. Open the website in a tab and sign in as usual. Or click **Let the agent operate a website** in a new chat; the AI asks which website and what to do. 2. Say the result you want, and what it must not change. For example: "On the orders page, list this week's unpaid orders. Do not change anything." 3. The AI opens its own tab in the background, so your current tab stays in front. A tab it works in shows **The agent is controlling this tab**. 4. Follow the steps in the chat. Type to correct it, or click **Stop** to take over. ## Example ```text Open our order system, go to yesterday's orders and give me a table: order number, customer, total, and whether it has been paid. Read only. ``` The AI opens the order system in its own tab, goes to yesterday's list, reads every page of results and returns the table in the chat. Your own tab stays where it was. ## Limits and permissions - It only opens web addresses (`http` and `https`). Files on your computer are read with [file tools](https://docs.micromeet.ai/files/reading-files.md), not tabs. - It works with the sign-in in the tab. It does not have accounts of its own. - Clicks and typing on web pages run without an approval card. Before anything it cannot undo, such as submitting, paying, deleting or sending a message, it stops and asks you unless your request already settles it. To be asked every time, say "ask me before you submit anything". See [When the AI asks you](https://docs.micromeet.ai/getting-started/workspaces-and-approvals.md#when-the-ai-asks-you). - When it runs a script inside a page, for example to close a pop-up that covers a button, the chat shows afterwards what ran and why. - It does not close tabs on its own. Ask it to close the ones you name; it will not close a pinned tab or the last one. ## If something goes wrong | What you see | What to do | |---|---| | It stopped at a sign-in, verification or payment page | Do that step yourself in the tab, then tell it to continue | | It says a button is covered or does not respond | Tell it what you see on the page, or do the click yourself and tell it to continue | | It is working in the wrong place | Type a correction while it works, or click **Stop** | | The page does not load at all | See [Network and Proxy](https://docs.micromeet.ai/troubleshooting/network-and-proxy.md) | ## Related - [Workspaces, Rules and Approvals](https://docs.micromeet.ai/getting-started/workspaces-and-approvals.md): When the AI asks you, and how to set rules for a workspace - [API Doc](https://docs.micromeet.ai/capture/api-doc.md): How the AI uses a website's own functions - [Tabs](https://docs.micromeet.ai/browser/tabs.md): Opening, pinning and naming tabs - [Import Chrome Sign-ins](https://docs.micromeet.ai/browser/chrome-import.md): Use the sign-ins you already have in Chrome (macOS) --- Source: https://docs.micromeet.ai/browser/tabs.html # Tabs Cowork's tabs work like a browser's, plus a few fixed tabs that are always there. ## What it is Each tab shows a website, a mini-app such as Omni Preview, or a file. You and the AI share the same tabs: the AI can work in a page you have open, signed in as you, and opens its own tabs in the background when it needs them. ## When to use it | Use tabs to | For example | |---|---| | Keep the websites you work with open | Your order system, email and a supplier portal side by side | | Let the AI work in a page you are already signed in to | Open the page, then ask the AI to collect data from it | | Keep track of many pages | Pin the ones you use most, or give them your own names | ## How to use it 1. **+** opens a new website tab. Hover over **+** to choose a mini-app instead, for example Omni Preview. 2. Drag a tab to move it. 3. Right-click a tab for more: | Item | What it does | |---|---| | **Reload** | Load the page again | | **Duplicate** | Open the same page in a new tab | | **Dimensions** | **Default** or **Phone** width; see [Phone-Width View](https://docs.micromeet.ai/browser/phone-width.md) | | **Pin** / **Unpin** | Keep a tab small at the left | | **Alias…** | Give the tab your own name; leave it empty to use the page title | | **Close**, **Close other tabs**, **Close tabs to the right** | Close tabs | **AI Employees**, **Care Workspace** and **Omni Preview** are fixed tabs: always there, and they cannot be closed. The app may label some of them differently; see [Terms and Interface Names](https://docs.micromeet.ai/reference/glossary.md). ## Example You open your order system and your shipping portal, pin both and name them "Orders" and "Shipping". Then you ask the AI: "In Orders, find today's unshipped orders, and check each one in Shipping." It works in its own background tabs, using your sign-ins. ## Limits and permissions - When Cowork starts again it reopens your tabs, up to 20, fixed tabs included. - A tab the AI is working in shows **The agent is controlling this tab**. - The AI does not close tabs on its own. It closes tabs you name; never a pinned tab or the last one. ## If something goes wrong | What you see | What to do | |---|---| | A page looks wrong or stopped loading | Right-click the tab › **Reload** | | Some tabs did not come back after a restart | Only the first 20 are reopened; open the others again | | A tab is controlled by the AI and you want it back | Click **Stop** in the chat | ## Related - [Let the Agent Use Web Pages](https://docs.micromeet.ai/browser/agent-browsing.md): How the AI works in tabs - [Address Bar, Search and History](https://docs.micromeet.ai/browser/address-bar-and-history.md): Open pages and find ones you visited - [Import Chrome Sign-ins](https://docs.micromeet.ai/browser/chrome-import.md): Bring your Chrome sign-ins (macOS) --- Source: https://docs.micromeet.ai/browser/address-bar-and-history.html # Address Bar, Search and History Open websites, search the web and find pages you visited before, as in any browser. ## When to use it When you open a website yourself, search the web, or find a page you visited before. ## How to use it ### Address bar Type a web address, or words to search Google (**Search Google or enter address**), then press **Enter**. Use **Back**, **Forward** and **Reload** on the left. While you type, pages you visited before appear below. Click one to open it, or **Remove from history** to delete it from the list. ### Browsing history Click **Settings and more** (right of the address bar) › **Browser history**. It opens **Settings › Browser › History**: all saved pages, newest first. --- Source: https://docs.micromeet.ai/browser/downloads.html # Downloads Files you download from web pages are saved to your download folder. ## When to use it When a website gives you a file, or you need to find a file you downloaded earlier. ## How to use it Click **Settings and more** › **Downloads** to open **Settings › Browser › Downloads**. It shows: - the **Download folder**; - every download, in progress or finished, with **Pause**, **Resume** and **Retry**. The AI can also check the download list for you, for example to find a file it just downloaded. --- Source: https://docs.micromeet.ai/browser/chrome-import.html # Import Chrome Sign-ins Cowork has its own browser, separate from Chrome. To avoid signing in to every website again, copy your Chrome cookies once. ## When to use it When you are already signed in to your websites in Chrome and do not want to sign in again in Cowork. ## How to use it 1. Open **Settings › Browser › Agent runtime browser**. (When an import is possible, a shortcut also appears in the address bar.) 2. Click **Import cookies from Chrome**. 3. If you have several Chrome profiles, choose one and click **Import this profile**. 4. Allow access when macOS asks. 5. Open or reload the websites you need. ## Good to know - macOS only. On Windows the option is not shown. - Only cookies are copied — no passwords or history. Your other Cowork cookies are kept. - **Undo this import** puts back what the import changed. - A copied cookie does not guarantee the website accepts the sign-in. --- Source: https://docs.micromeet.ai/browser/phone-width.html # Phone-Width View See a web page at phone width, for example to check a mobile site. ## When to use it When you need to see or test how a page looks on a phone. ## How to use it - Right-click the tab › **Dimensions** › **Phone**. The page is shown 440 px wide, in the middle. - **Dimensions** › **Default** returns to full width. Only the width changes. The page is not reloaded and the website is not told it is a phone. --- Source: https://docs.micromeet.ai/browser/copy-element.html # Copy Element for Agent Point the AI at an exact part of a web page. ## When to use it When you want to point the AI at one exact part of a page, such as a button or a table. ## How to use it 1. Right-click the part of the page — a button, a table, a paragraph. 2. Choose **Copy Element for Agent**. Use **Select Parent** first if you want the larger block around it. 3. Paste into the chat and say what you want, for example "Fill this form" or "Read this table". What is copied is the page address and a description of that element, so the AI can find it on the page. --- Source: https://docs.micromeet.ai/ai-employees/employee-list.html # Your AI Coworkers An AI coworker is a setup for one kind of work: its instructions and the skills it uses. Each AI coworker has its own chats. In 0.1.41 the app lists AI coworkers under **AI Employees**. ## What it is Every AI coworker is one folder with an `AGENT.md` file: its name, its job, how it should work and which skills it uses. Choosing an AI coworker starts a chat with that setup instead of the general one. AI coworkers saved on this computer are yours; AI coworkers saved in a workspace folder go to everyone who opens that folder. See [Local and Workspace AI coworkers](https://docs.micromeet.ai/ai-employees/local-and-workspace.md). An AI coworker is named by its job, not given a person's name. When an institution switches on a package for your team (everything one job needs, in one folder), you work with it here as an AI coworker too. ## When to use it | Use an AI coworker when | A plain chat is enough when | |---|---| | You do the same kind of work often, with the same rules and skills | The job is one-off | | Several people should handle that work the same way | You are exploring or asking a question | | You want that work kept in its own chats | | ## How to use it 1. Find your AI coworkers on **the rail** on the left of the chat (small icons), or in the **AI Employees** tab (the first fixed tab, or the **AI Employees** icon on the rail), which shows **Your AI Team**. 2. Click an AI coworker's icon, or **Chat** on its row. A chat opens with that AI coworker, and it greets you first. 3. A dot on an icon means a reply is waiting or the AI coworker needs you. 4. Earlier chats with an AI coworker are under **Sessions**. ## Example Your team writes the same kind of supplier report every month. You create an AI coworker whose instructions say how the report is laid out and which skills it uses, and save it in the team's workspace folder. Everyone who opens the folder sees the AI coworker on the rail and gets the report done the same way. ## Limits and permissions - An AI coworker is saved on this computer or in a workspace folder. It cannot be published by an institution in 0.1.41; skills can. - A workspace AI coworker is only there while that workspace is open. - Each AI coworker has one chat thread per workspace. - The skills listed for an AI coworker are suggestions, not a limit: the AI coworker can also use your other skills. What the AI may see and change is set by the workspace, not by the AI coworker. ## If something goes wrong | What you see | What to do | |---|---| | An AI coworker is missing from the rail | Check the workspace: workspace AI coworkers only show while their folder is open | | An AI coworker shows **Invalid** | Its `AGENT.md` has a problem; the reason is shown next to it. Ask the AI to fix the file | | An AI coworker shows **Same name as …** | Two AI coworkers share a name. Both still work; rename one to avoid mixing them up | ## Related - [Create an AI Coworker](https://docs.micromeet.ai/ai-employees/create-employee.md): Set one up from a form or a chat - [Local and Workspace AI Coworkers](https://docs.micromeet.ai/ai-employees/local-and-workspace.md): Where AI coworkers are saved - [Default AI Coworkers](https://docs.micromeet.ai/ai-employees/default-employees.md): The AI coworkers that come with Cowork --- Source: https://docs.micromeet.ai/ai-employees/create-employee.html # Create an AI Coworker Set up an AI coworker for one kind of work: a name, a job and the instructions it follows. ## What it is An AI coworker is a saved setup: a name and icon, a job, and instructions in plain words about what to do, how, and what to ask you first. You can create one from a form or by asking in a chat; nothing is saved until you click **Create**. ## When to use it | Create an AI coworker when | A skill or plain chat is enough when | |---|---| | The same kind of work comes back often, with the same rules | You need one method, not a whole job: make a skill | | Several people should handle that work the same way | The job is one-off | | You want that work kept in its own chats | | ## How to use it 1. Open the **AI Employees** tab and click **Create Your AI Employee**. A form opens in the chat. 2. Choose an icon: **Shape**, **Color** and **Eyes**, or click **Random**. 3. Fill in **Name** (name it by its job, such as "Weekly reports") and **Role** (the job, in a few words). 4. In **Talk about this employee**, write what the AI coworker should do, how, and what it must ask you before acting. 5. **Save to**: **This computer** (only you, everywhere), or **This workspace** (kept with the current workspace folder). 6. Click **Create**. The AI coworker appears on the rail and writes its greeting (**Writing a greeting…**). You can also type, for example, "Create an AI coworker that drafts weekly reports". The AI asks for a name and the job, then shows the same form for you to check and **Create**. ## Example In your sales team's workspace you create "Reports" with the role "weekly sales report". Under **Talk about this employee** you write: "Every Monday, read last week's order export in the workspace, write the report in our usual layout, and ask before sending it to anyone." You save it to **This workspace**, so everyone who opens the folder gets it. ## Limits and permissions - **This workspace** is only available when a workspace is open. - The skills you mention guide the AI coworker; it can also use your other skills. - An AI coworker cannot be published by an institution in 0.1.41; share it through a workspace folder instead. ## If something goes wrong | What you see | What to do | |---|---| | **This workspace** cannot be chosen | Choose a workspace first, then create the AI coworker | | The AI coworker does the job differently each time | Make the instructions more specific, or turn the method into a skill | | You created it in the wrong place | Create it again with the right **Save to**, and delete the other one | ## Related - [Your AI Coworkers](https://docs.micromeet.ai/ai-employees/employee-list.md): Find and chat with your AI coworkers - [Edit and Delete](https://docs.micromeet.ai/ai-employees/edit-and-delete.md): Change or remove an AI coworker - [Build Your First Skill](https://docs.micromeet.ai/skills/first-skill.md): When a method is enough --- Source: https://docs.micromeet.ai/ai-employees/edit-and-delete.html # Edit and Delete Change an AI coworker's icon, job or instructions, or remove an AI coworker you no longer need. ## When to use it When an AI coworker keeps getting something wrong, its job changed, or you no longer need it. ## How to use it ### Edit - On the rail: right-click the AI coworker › **Profile**. - On the **AI Employees** tab: click **…** on its row › **Edit profile**. The profile shows the icon, name, role, greeting and instructions. Change what you need and click **Save**. ### Delete - On the rail: right-click › **Delete**. - On the **AI Employees** tab: **…** › **Delete**. - Or **Delete** at the bottom left of the profile. Confirm in **Delete {name}?**. The AI coworker and its chats are removed. You can also ask in a chat to change or delete an AI coworker; you confirm before anything changes. --- Source: https://docs.micromeet.ai/ai-employees/local-and-workspace.html # Local and Workspace AI Coworkers An AI coworker is saved in one of two places, marked on its row: ## When to use it When you decide whether an AI coworker is only for you, or for everyone who works in a project folder. ## How to use it | Mark | Saved in | Available | |---|---|---| | **Local** | This computer | In every workspace on this computer. | | **Workspace** | The `.agents/agents/` folder inside the current workspace | Only while that workspace is open. Anyone who gets the folder gets the AI coworker too. | Each AI coworker is one folder with an `AGENT.md` file. You can copy such a folder into the agents folder to add an AI coworker. See [Choose a Workspace](https://docs.micromeet.ai/files/workspace.md). --- Source: https://docs.micromeet.ai/ai-employees/default-employees.html # Default AI Coworkers Cowork 0.1.41 comes with four AI coworkers, added to this computer the first time it starts: ## When to use it When you want to know which AI coworkers came with Cowork and whether you need them. ## How to use it | Name in the app | Job | For | |---|---|---| | **Ada** | Web page operator: works on websites for you | Everyone | | **Mia** | Check-up package to Care Workspace: turns an institution's MCU materials into records | Institutions that use Care Workspace | | **Ivy** | Reports: generate, send and track | Institutions that use Care Workspace | | **Zoe** | Accounts, invitations and roles | Institutions that use Care Workspace | They are ordinary local AI coworkers: you can edit or delete them. A deleted default AI coworker does not come back. If your institution does not use Care Workspace, you can delete Mia, Ivy and Zoe. --- Source: https://docs.micromeet.ai/extend/overview.html # Extension Overview Cowork can take on new abilities without a new version of the app. There are four kinds of addition: **Skill**, **Extension**, **Injection** and **Mini App**. All four can be packed together into one **Cowork package**, so one job's skills, code, page scripts and screen travel as one unit. ```mermaid flowchart LR cowork(("Cowork")) subgraph pkg["Cowork package"] direction TB skill["Skill
SKILL.md + scripts"] subgraph ext["Extension · package.json"] direction TB entry["Entry file
activate()"] conn["Connector"] inj["Injection
script inside a web page"] end mini["Mini App
its own screen"] end gw["Gateway
one way in and out
for outside messages"] web["Websites"] chan["Outside channels
WhatsApp …"] cowork -- the AI reads it --> skill cowork -- runs after you approve --> ext cowork -- opens in a tab --> mini entry -- puts into pages --> inj inj -- runs inside the page --> web cowork <-- messages --> gw gw <-- joins --> conn conn <-- sends and receives --> chan style pkg fill:#efe8dc,stroke:#d3c6b1,stroke-width:1px,color:#5c5145 style ext fill:#e4dacb,stroke:#c4b49b,stroke-width:1px,color:#5c5145 classDef core fill:#8a7660,stroke:#8a7660,color:#ffffff,stroke-width:1px classDef part fill:#fbf8f3,stroke:#c4b49b,color:#3f362b,stroke-width:1px classDef outer fill:#f6f2eb,stroke:#cdbfa9,color:#6b6052,stroke-dasharray:4 3 classDef gateway fill:#6e5d4b,stroke:#6e5d4b,color:#ffffff,stroke-width:1px linkStyle default stroke:#a8957a,stroke-width:1.2px class cowork core class skill,entry,conn,inj,mini part class web,chan outer class gw gateway ``` ## Cowork package A Cowork package is one folder that holds what one job needs: a Mini App and its screen, the Extension it brings, the Skills the AI uses and an `INSTALL.md` with the setup steps for the AI. Injections are scripts inside the Extension. ```text / miniapp.json appId, name, version, entry, extension: "extension" index.html … the Mini App screen extension/ the Extension: package.json + index.mjs skills// Skills, optional INSTALL.md setup steps the AI follows ``` In 0.1.41 Cowork does not yet install a package in one step. Each part goes in its own way, as the sections below say. ## Skill A Skill teaches the AI how to do one kind of job. It is a folder with a `SKILL.md` file, plus scripts if the job needs them. - The AI reads it when a request matches. Its scripts run on the Bun runtime that comes with Cowork. - To turn it on, put it in a skill folder. See [Skill](https://docs.micromeet.ai/extend/skills.md). - Anyone can write one. ## Extension An Extension is a code package that runs in its own background process: a `package.json` and one entry file. - In 0.1.41 it registers **Connectors**. Messages from outside channels, such as WhatsApp, come in and go out through **Gateway**; a Connector is the part that joins one channel to Gateway. - With the browser permission it can also put Injections into the websites it names. - It is kept in `/extensions/packages//`. It runs only after you approve it in **Settings › Extensions**. See [Extension](https://docs.micromeet.ai/extend/extensions.md). ## Injection An Injection is a script that runs inside a web page, apart from the page's own scripts. Use it to read or act on a website's pages. - An Extension runs it, or you add a website button in **Settings › Injections**. - It acts only on the pages it is meant for. See [Injection](https://docs.micromeet.ai/extend/injections.md). ## Mini App A Mini App is an app with its own screen that opens in a Cowork tab, for you to use. - In 0.1.41 only the Mini Apps that come with Cowork exist. You cannot build your own yet. See [Mini App](https://docs.micromeet.ai/extend/mini-apps.md). `` is `~/.micromeet-cowork` for the released app and `~/.micromeet-cowork_preview` for Preview. ## Which one to build 1. To teach the AI how to do a kind of job, write a **Skill**. 2. To connect an outside message channel to Cowork, write an **Extension** with a Connector. 3. To act inside a website's pages, write an **Injection**: a script inside an Extension, or a website button. 4. An app with its own screen is a **Mini App**. In 0.1.41 only the Mini Apps that come with Cowork exist. ## Related - [Skill](https://docs.micromeet.ai/extend/skills.md): Folders, sources and rules for skills - [Extension](https://docs.micromeet.ai/extend/extensions.md): Package layout, Connectors and approval - [Injection](https://docs.micromeet.ai/extend/injections.md): Scripts and buttons inside web pages - [Mini App](https://docs.micromeet.ai/extend/mini-apps.md): Apps in a tab and what is available today --- Source: https://docs.micromeet.ai/extend/skills.html # Skill A Skill is a written method for the AI: a folder with a `SKILL.md` file, plus optional scripts and reference files. When a request matches a skill's description, the AI reads the skill before it starts. ## The folder | Part | What it holds | |---|---| | `SKILL.md` | A short header with `name` and `description`, then the method in plain words | | `scripts/` | Optional code the skill runs, for example `run.mjs` | | `references/` · `assets/` | Optional material the AI reads when it needs it | ## Where skills are kept | Source | Folder | Who can change it | |---|---|---| | This computer | `/skills/` | You and the AI on this computer | | Workspace | `/.agents/skills/` | You and the AI; travels with the folder | | Your home folder | `~/.agents/skills/` | You | | Platform | `/platform_skills/` | Read-only; updated from Micromeet | | Institution | `/institution_skills//` | Read-only; updated from Micromeet | ## Rules - The header of `SKILL.md` must have `name` and `description`. The description says what the skill does and when to use it. - JavaScript and TypeScript scripts run on the Bun runtime that comes with Cowork, so nobody has to install Node or Python. - To create a skill, ask the AI in the chat. It creates the folder and checks the format. The new skill can be used from your next message. ## Related - [What Skills Are](https://docs.micromeet.ai/skills/what-are-skills.md): Skills from a user's point of view - [How a Skill Is Written](https://docs.micromeet.ai/skills/skill-anatomy.md): The header and the method, step by step - [Build Your First Skill](https://docs.micromeet.ai/skills/first-skill.md): Make one with the AI --- Source: https://docs.micromeet.ai/extend/extensions.html # Extension An Extension is a code package that runs in its own background process. In 0.1.41 it registers **Connectors**: the parts that send and receive messages between an outside channel and Cowork's Gateway. With the browser permission it can also read and act on the pages of the websites it names. ## How it goes live 1. Put the package in `/extensions/packages//`, or use **Install from folder** in **Settings › Extensions**, which copies a folder there. 2. **Settings › Extensions** shows it as waiting for approval. Nothing in it runs yet. 3. You approve it and switch it on. Cowork starts its process and calls its `activate` function. 4. If any file in the folder changes, it waits for approval again. ## The package | File or folder | What it holds | |---|---| | `package.json` | `name`, which must equal the folder name (lowercase letters, digits and hyphens); `version`; `description`; `pi.extensions`, which lists exactly one entry file; and the Cowork section, which declares `connectors`, `capabilities`, `origins` and `platforms` | | The entry file, for example `index.mjs` | Exports `activate(api)`, which calls `api.registerConnector(...)` for each declared Connector | | `/extensions/logs/.log` | What the Extension writes to its log; Cowork writes the file | | `/extensions/data//` | The Extension's own folder for its data; its process runs in this folder | ## What it can declare | Item | Meaning | |---|---| | `connectors` | The IDs of the Connectors it registers. Registering an ID that is not listed is refused | | `capabilities` | `browser` to act on web pages; `audio` (needs `browser`) to capture a page's sound; `platform-gate-v1` to use `platforms` | | `origins` | With `browser`: the exact websites it may use, from 1 to 20, such as `https://example.com` | | `platforms` | The computers it supports: `darwin-arm64`, `darwin-x64`, `win32-x64` | ## A Connector A Connector has an `id` and three functions. `start(ctx)` starts it: open connections and timers here, not in `activate`; it has 5 seconds. `stop()` must be safe to call more than once; it has 5 seconds. `send(reply)` delivers one reply to the channel; it has 30 seconds. Through `ctx`, the Connector hands incoming messages to Cowork (`ctx.emit`), writes to its log (`ctx.log`), and, with the browser permission, uses `ctx.browser`. ## Limits - Only you can approve an Extension. The AI cannot. - The approval covers the exact files you approved. Changing one byte means approving again. - A package can have at most 200 files and 5 MB. Packages from npm and `dependencies` are not installed. - If the process crashes, Cowork restarts it after a short wait. - In 0.1.41 an Extension cannot add tools or commands for the AI. To give the AI a new method, write a [Skill](https://docs.micromeet.ai/extend/skills.md). ## Related - [Extensions](https://docs.micromeet.ai/connections/extensions.md): Install, approve and switch on an Extension - [Gateway: Outside Messages](https://docs.micromeet.ai/connections/gateway.md): Where Connector messages go - [Injection](https://docs.micromeet.ai/extend/injections.md): Scripts an Extension runs inside web pages --- Source: https://docs.micromeet.ai/extend/injections.html # Injection An Injection is code that runs inside a web page, like the content script of a Chrome extension. It runs apart from the page's own scripts. Anything Cowork puts into a page is an Injection, not an Extension. ## Two sources | Source | Use | Example | |---|---|---| | An Extension's `ctx.browser.inject` | Package code reads or acts on a website's pages | A Connector that reads and sends a web chat's messages | | **Settings › Injections** | A floating **micromeet** button on a chosen website; clicking a job on it asks the AI to do that job | Start a common job on an admin page in one click | ## Rules - An Extension can inject only into websites listed in its `origins`, and only with the `browser` permission. - A script first checks that the current address is the page it is meant for, and does nothing on any other page. - A script does not read or send cookies, tokens or personal data. ## Related - [Website Buttons (Injections)](https://docs.micromeet.ai/skills/injections.md): Add and remove a website button - [Extension](https://docs.micromeet.ai/extend/extensions.md): Declaring `browser` and `origins` --- Source: https://docs.micromeet.ai/extend/mini-apps.html # Mini App A Mini App is an app with its own screen that opens in a Cowork tab. In 0.1.41 only the Mini Apps that come with Cowork exist. You cannot build or install your own yet. ## Mini Apps that come with Cowork | Mini App | What it does | |---|---| | AI Employees | The list of AI employees and their chats | | Omni Preview | Browse and preview the files of your workspace | | File Preview | Preview one file | | Questionnaire | Answer a questionnaire the AI sent | | Connector | Channels connected through Gateway, such as the WhatsApp seat | ## What the AI can do - List the Mini Apps it can open, and open one in a tab. ## Related - [Extension Overview](https://docs.micromeet.ai/extend/overview.md): Which kind of addition to build - [Omni Preview](https://docs.micromeet.ai/files/omni-preview.md): The file preview Mini App - [Questionnaires](https://docs.micromeet.ai/chat/questionnaires.md): The questionnaire Mini App --- Source: https://docs.micromeet.ai/skills/what-are-skills.html # What Skills Are A skill is a written method for one kind of job — for example "prepare the weekly sales report" or "send this month's invoices". When your request matches a skill, the AI reads it and follows it, so the job is done the same way every time. Each skill is a folder with a `SKILL.md` file and, if needed, scripts and other files. ## Where skills come from | Source | Where | Who can change it | |---|---|---| | Built-in | Inside Cowork | Nobody — see [Built-in Skills](https://docs.micromeet.ai/skills/builtin-skills.md). | | This computer | Cowork's `skills/` folder | You. | | Workspace | `.agents/skills/` in the current workspace | You; travels with the folder. | | Your home folder | `~/.agents/skills` | You. | | Platform / institution | Published by Micromeet for everyone, or for your institution | Read-only; updated automatically. | ## Use a skill - Just describe the job; the AI picks the matching skill. - Or type `/` and the skill's name to use it directly (see [Slash Commands](https://docs.micromeet.ai/chat/slash-commands.md)). ## Build your own Start with [Build Your First Skill](https://docs.micromeet.ai/skills/first-skill.md), then see [How a Skill Is Written](https://docs.micromeet.ai/skills/skill-anatomy.md) and [What Makes a Good Skill](https://docs.micromeet.ai/skills/good-skills.md). --- Source: https://docs.micromeet.ai/skills/first-skill.html # Build Your First Skill The fastest way to a good skill is to do the job once with the AI, get the result right, then ask it to write down how. This page walks through that with a real example: a weekly summary of meeting notes. ## 1. Do the job once, together Pick a job you do often. Choose the folder it needs as the workspace, then ask for the result in full: ```text Read all meeting notes in this folder from the last 7 days. Write a summary with: decisions made, open questions, and actions with owner and due date. Save it as weekly-summary-.md. ``` Correct the AI until the result is what you want. Each correction ("owners as first names only", "group actions by owner") is something the skill will remember. ## 2. Ask the AI to turn it into a skill ```text Turn what we just did into a skill called weekly-summary. Include the corrections I made. ``` The AI writes the skill's `SKILL.md`, checks its format and tells you where it saved it: - With a workspace open, it goes into the workspace's `.agents/skills/` folder, so everyone who opens the folder gets it - Without a workspace, it goes into this computer's skills, for you alone ## 3. Read what it wrote Open the skill in **Settings › Skills**, or ask "show me the weekly-summary skill". Check two things: - **The description** says what the skill does and when to use it. This is what the AI reads to decide whether your request matches. - **The steps** match how you want the job done, including your corrections See [How a Skill Is Written](https://docs.micromeet.ai/skills/skill-anatomy.md) for each part. ## 4. Test it in a new chat Start a **New chat** and ask in your own words, without naming the skill: ```text Summarise this week's meetings. ``` If the AI uses the skill, the description works. You can also run it directly by typing `/weekly-summary`. > **If the AI does not pick it up** > The description is too narrow or too vague. Ask: "Update the weekly-summary description so it is used when I ask for a summary of meetings or notes." ## 5. Improve it as you use it Every time the result is off, fix it in the chat, then ask: "Update the weekly-summary skill with that." A skill gets better each time you use it. If you edit `SKILL.md` yourself outside Cowork, ask the AI to "reload skills", or start a new chat, so it reads the new version. ## Next steps - [How a Skill Is Written](https://docs.micromeet.ai/skills/skill-anatomy.md): The parts of SKILL.md, scripts and other files - [What Makes a Good Skill](https://docs.micromeet.ai/skills/good-skills.md): Scope, descriptions, checks and sharing - [Skill Examples](https://docs.micromeet.ai/skills/skill-examples.md): Complete skills you can copy and adapt - [Scheduled Tasks](https://docs.micromeet.ai/skills/scheduled-tasks.md): Run your skill every week by itself --- Source: https://docs.micromeet.ai/skills/skill-anatomy.html # How a Skill Is Written A skill is a folder. The only required file is `SKILL.md`: a short header that tells the AI what the skill is for, followed by the method in plain words. Scripts and reference files are optional. ## The folder ```text weekly-summary/ ├── SKILL.md required: header + method ├── scripts/ optional: code the skill runs │ └── run.mjs └── references/ optional: material the AI reads when needed └── format.md ``` The folder name is the skill's name. Use lowercase letters, digits and hyphens, for example `weekly-summary` or `check-invoices`. ## SKILL.md ```markdown --- name: weekly-summary description: Summarise the last 7 days of meeting notes into decisions, open questions and actions with owners. Use when asked for a weekly summary, a recap of meetings, or what was decided this week. --- # Weekly summary ## Inputs and outcome - Input: meeting notes (.md, .docx or .pdf) in the workspace, dated in the file name or first line. - Outcome: weekly-summary-YYYY-MM-DD.md in the workspace. ## Procedure 1. List notes from the last 7 days. If there are none, say so and stop. 2. From each note take decisions, open questions and actions. 3. Write the summary in three sections. Actions as a table: owner (first name) · action · due date. Group by owner. 4. Save the file. Do not change the notes. ## Representative check Every action in the summary appears in one of the notes, and every note from the last 7 days is listed under Sources. ``` ### The header | Field | Required | What it does | |---|---|---| | `name` | Yes | The skill's name; the same as the folder name. You can run it as `/name` | | `description` | Yes | What the skill does **and when to use it**. The AI reads only this to decide whether a request matches, so put the words people actually use in it | | `entry` | No | The main script, for example `scripts/run.mjs` | | `resources` | No | A list of other files in the folder the skill uses | | `disable-model-invocation` | No | `true` means the AI never picks the skill by itself; it runs only when you type `/name` | ### The body Write the method the way you would brief a new colleague. Three parts work well, and they are what Cowork's skill creator starts you with: - **Inputs and outcome**: what the skill needs and what "done" looks like - **Procedure**: the steps, the limits ("do not change the notes") and the expected output - **Representative check**: one example input and the result you would expect, so the AI can tell whether it worked The AI reads the full body only when it uses the skill, so it can be as long as the job needs. ## Scripts Add a script when part of the job must be exact every time: a calculation, a file conversion, a call to a system. The AI runs it and uses what it prints. - Scripts are JavaScript or TypeScript (`.mjs`, `.js`, `.ts`). Cowork runs them with its own bundled runtime; nothing extra to install. - Running a script on your computer always asks you first - Scripts run with your normal permissions. Only use scripts you or someone you trust wrote. ### A command that runs without the AI A skill can also be a plain command: typing `/name` and some words runs its script directly, without the model, and shows what the script prints. The header for that is: ```yaml --- name: count-files description: Count files in the workspace by type. entry: scripts/run.mjs x-shortcut: run: scripts/run.mjs --- ``` The words after `/count-files` reach the script as command-line arguments. Ask the AI to "make a command skill" and it sets this up for you. ## Where the folder goes | Location | Who gets it | |---|---| | `.agents/skills/` in a workspace | Everyone who opens that workspace | | This computer's skills (Cowork's `skills/` folder) | Only you, in every workspace | | `~/.agents/skills` in your home folder | Only you; also read by other tools that use this folder | Published platform and institution skills are read-only. To change one, copy it to your own skills first. See [What Skills Are](https://docs.micromeet.ai/skills/what-are-skills.md). ## Check a skill Ask "check the weekly-summary skill". Cowork verifies the header, that declared files exist and that no template placeholders are left. A format check does not prove the skill works: test it on a real request. --- Source: https://docs.micromeet.ai/skills/good-skills.html # What Makes a Good Skill A good skill gives the same right result every time, for anyone who uses it. These are the habits that get you there. ## Make a skill when the job repeats Make a skill when you have done a job more than once and expect to do it again, when the steps should be the same each time, or when someone else needs to do it your way. Don't make a skill for a one-off question, or for knowledge that changes every day. For a one-off, a clear request is enough. See [Give Clear Instructions](https://docs.micromeet.ai/guides/clear-instructions.md). ## One skill, one job A skill that does one job well is easier to describe, test and fix than one that does several. If you write "and also" in the description, think about two skills. | Too broad | Better | |---|---| | `finance` | `check-invoices`, `monthly-expense-report` | | `website-helper` | `export-orders`, `update-stock-levels` | ## Write the description for the request, not for the skill The AI chooses a skill by its description alone. Say what it does and when to use it, in the words people will actually type: | Weak | Strong | |---|---| | "Invoice tool." | "Check supplier invoices against the agreed price list and list mismatches. Use when asked to check, verify or reconcile invoices." | | "Does the weekly report." | "Write the weekly operations report from this week's tickets and orders. Use when asked for the weekly report, a weekly update or this week's numbers." | ## Say what done looks like Name the output, its format and where it goes. "A table" is vague; "a CSV with columns date, supplier, amount, difference, saved as mismatches.csv" is not. ## Write down the limits Tell the AI what it must not do and when it must stop and ask: - "Read only. Never change records on the website." - "If more than 20 items fail, stop and report instead of continuing." - "Ask before sending anything to someone outside the team." ## Include a check Give one representative input and the result you expect, plus a rule the AI can test: "every total matches the sum of its rows", "every ID in the output exists in the input". The AI uses it to verify before it reports back, and you use it to tell whether a change broke something. ## Put exact work in a script If part of the job must be exactly the same every time, such as a calculation, a format conversion or a fixed sequence of calls, put it in a script. The AI's judgement goes into the parts that need judgement. See [How a Skill Is Written](https://docs.micromeet.ai/skills/skill-anatomy.md#scripts). ## Keep it short; move detail out Keep `SKILL.md` to the method. Long reference material such as a price list, a style guide or a field list belongs in a separate file in the skill folder, mentioned in the method ("use references/prices.csv"). The AI opens it when it needs it. ## Share it where the work lives - A skill for one project goes in that project's workspace (`.agents/skills/`). Everyone who opens the folder gets the same skill. - A personal habit goes in this computer's skills - A method for your whole institution can be published by your institution, so everyone gets it and updates arrive automatically ## Improve it every time it misses When a result is wrong, correct it in the chat, then ask the AI to update the skill with that correction. Over time the skill collects the judgement of everyone who uses it. ## Checklist - [ ] Does one job - [ ] Description says what and when, in the users' words - [ ] Output, format and location are named - [ ] Limits and stop conditions are written down - [ ] Has a representative check - [ ] Exact steps are in a script - [ ] Saved where the people who need it will find it - [ ] Tested in a new chat without naming the skill --- Source: https://docs.micromeet.ai/skills/skill-examples.html # Skill Examples Three complete skills you can copy and adapt: one written only in words, one that works on a website, and one that runs a script. To use one, ask the AI to "create this skill" and paste it, or save the folder into your workspace's `.agents/skills/`. ## Check invoices against a price list A method in words, with a reference file. Good for any check you do by comparing documents with a list. ```text check-invoices/ ├── SKILL.md └── references/ └── prices.csv ``` ```markdown --- name: check-invoices description: Check supplier invoices against the agreed price list and list every line that does not match. Use when asked to check, verify or reconcile invoices or supplier bills. --- # Check invoices ## Inputs and outcome - Input: invoices (PDF or Excel) attached or in the workspace. - Price list: references/prices.csv (columns: item_code, item_name, unit_price). - Outcome: mismatches.csv in the workspace with columns invoice_file, item_code, invoiced_price, agreed_price, difference. ## Procedure 1. Read each invoice and take every line: item code, quantity, unit price. 2. Look up each item code in references/prices.csv. 3. A line is a mismatch when the unit price differs by more than 0.01, or the item code is not in the price list (agreed_price empty). 4. Write mismatches.csv. In the chat, give the number of invoices checked, lines checked and mismatches found. 5. Read only. Do not change or move the invoices. ## Representative check An invoice line for item A-100 at 12.50, with A-100 at 12.00 in the price list, appears in mismatches.csv with difference 0.50. The count of lines checked equals the sum of lines across all invoices. ``` ## Export this month's orders from a website A method that works on a website you are signed in to. Good for any regular export from a system that has no export button. ```markdown --- name: export-orders description: Export this month's orders from the orders website into a CSV. Use when asked for this month's orders, an order export or an order list. --- # Export orders ## Inputs and outcome - Input: the orders website, open and signed in, in a Cowork tab. - Outcome: orders-YYYY-MM.csv in the workspace with columns order_no, date, customer, total, status. ## Procedure 1. Go to the orders list and filter to the current month. 2. Read every page of results, not only the first. 3. Write the CSV. Dates as YYYY-MM-DD, totals as plain numbers. 4. Read only: never click Save, Delete, Submit or change any field. 5. If a sign-in or verification page appears, stop and tell me which page. ## Representative check The number of rows in the CSV equals the result count the website shows for the month. ``` If you run this every month and the list is long, ask the AI to "write a crawl script for this" instead. It is faster and resumes where it stopped. See [Crawl Scripts](https://docs.micromeet.ai/capture/crawl-scripts.md). ## Count files by type (a command) A skill that runs a script directly when you type `/count-files`, without the AI. Good for quick, exact jobs that need no judgement. ```text count-files/ ├── SKILL.md └── scripts/ └── run.mjs ``` ```markdown --- name: count-files description: Count the files in the workspace by file type. entry: scripts/run.mjs x-shortcut: run: scripts/run.mjs --- # Count files Typing /count-files runs scripts/run.mjs on this computer. It prints how many files of each type are in the workspace. ``` ```js // scripts/run.mjs — stdin is JSON { args, sessionId, workspace }. import { readdirSync } from 'node:fs'; import { extname, join } from 'node:path'; let raw = ''; for await (const chunk of process.stdin) raw += chunk; const { workspace } = raw ? JSON.parse(raw) : {}; if (!workspace) throw new Error('Choose a workspace first.'); const counts = {}; const walk = (dir) => { for (const entry of readdirSync(dir, { withFileTypes: true })) { if (entry.name.startsWith('.')) continue; const path = join(dir, entry.name); if (entry.isDirectory()) walk(path); else { const type = extname(entry.name).toLowerCase() || '(none)'; counts[type] = (counts[type] ?? 0) + 1; } } }; walk(workspace); for (const [type, count] of Object.entries(counts).sort((a, b) => b[1] - a[1])) { console.log(`${type}\t${count}`); } ``` More on scripts in [How a Skill Is Written](https://docs.micromeet.ai/skills/skill-anatomy.md#scripts). ## Next steps - [What Makes a Good Skill](https://docs.micromeet.ai/skills/good-skills.md): The checklist to run before you share a skill - [Scheduled Tasks](https://docs.micromeet.ai/skills/scheduled-tasks.md): Run a skill at set times --- Source: https://docs.micromeet.ai/skills/manage-skills.html # Install, Create and Manage Skills See, create, install, change and delete your skills. ## What it is Skills come from several places: built into Cowork, this computer, the workspace, your home folder, and your platform or institution (see [What Skills Are](https://docs.micromeet.ai/skills/what-are-skills.md)). Your own skills you can change; published ones are read-only. Everything here is done either in **Settings › Skills** or by asking the AI. ## When to use it | To | Use | |---|---| | Turn a job you just did into a method | Create, by asking the AI | | Use a skill someone published | Install from its source | | Fix a skill that gives the wrong result | Change it | | Take a skill with you or give it to a colleague | Export, then import | ## How to use it | To | Do this | |---|---| | See your skills | Open **Settings › Skills** to browse every skill by source and read it | | Create one | Ask: "Turn what we just did into a skill called weekly-summary". The AI writes `SKILL.md`, checks its format and tells you where it saved it: in the workspace if one is open, otherwise on this computer | | Install one | Paste the source into the chat (a GitHub address, an npm package or a `skills add` command) and ask the AI to install it. It shows what is inside first, then installs only what you choose | | Change one | Ask the AI to change it, or edit its `SKILL.md` yourself | | Export or import | **Settings › Skills** imports or exports a skill package | | Delete one of this computer's skills | Ask the AI; it asks you to confirm first | | Manage your `/` commands | Type `/shortcut` | ## Example ```text Install the skill from https://github.com/example/meeting-minutes-skill ``` The AI shows the files in the package and asks which to install. After you choose, the skill appears in **Settings › Skills** and as `/meeting-minutes`. ## Limits and permissions - Platform and institution skills are read-only. To adapt one, copy it into your own skills. - A skill's scripts run with your normal permissions; running one asks you first. Install only from sources you trust. - After you edit a skill outside Cowork, ask the AI to "reload skills", or start a new chat. - Updating or removing an installed skill is refused if you changed its files locally. ## If something goes wrong | What you see | What to do | |---|---| | The AI does not use your skill | Make the description say when to use it, in the words you type. See [What Makes a Good Skill](https://docs.micromeet.ai/skills/good-skills.md) | | An edited skill still behaves the old way | Ask the AI to "reload skills", or start a new chat | | Two skills have the same name | Both are listed with their source; run the one you mean with `/name`, or rename one | ## Related - [Build Your First Skill](https://docs.micromeet.ai/skills/first-skill.md): Step by step from a finished job - [How a Skill Is Written](https://docs.micromeet.ai/skills/skill-anatomy.md): The parts of `SKILL.md` - [Built-in Skills](https://docs.micromeet.ai/skills/builtin-skills.md): The skills that come with Cowork --- Source: https://docs.micromeet.ai/skills/builtin-skills.html # Built-in Skills These come with Cowork. You do not need to install them; just ask. ## When to use it When you want to know what Cowork can do without installing anything. ## How to use it | Skill | Ask for example | |---|---| | **Manual** | "How do I…?", `/manual`, `/menu` | | **Tabs** | "Open this page", "Close the tabs I opened" | | **Dimensions** | "Show this page at phone width" | | **Archive chat** | "Archive this chat", `/archive` | | **Image generation** | "Make an image of…" | | **Bookmarks** | "Bookmark this folder in Omni Preview" | | **Drill** | "Drill this site" | | **Capture whitelist** | "Make a whitelist for this site" | | **Crawl script** | "Crawl all records of this month" | | **Scheduler** | "Every Monday at 9, remind me to…" | | **Configuration** | "Turn on Stay Awake" | | **Safe Env** | "Save this API key" | | **Decision** | Sorting or scoring a batch of items | | **Reload Skills** | "Reload skills" after editing skill files outside Cowork | --- Source: https://docs.micromeet.ai/skills/injections.html # Website Buttons (Injections) You can put a floating **micromeet** button on a website you use often. The button lists the jobs you set for that site; click one, and the AI starts it in the chat. ## When to use it When you start the same jobs on the same website often and want a button for them on the page. ## How to use it 1. Open the website in a tab. 2. Ask: "Add a button to this site with: Export this week's orders, Check today's deliveries". 3. The blue **micromeet** button appears on the page. Drag it where you like. - See and remove buttons in **Settings › Injections**, or ask "Remove the button from this site". - Removing a button changes nothing else on the website. --- Source: https://docs.micromeet.ai/skills/workflows.html # Workflows and Background Agents For big jobs, the AI can split the work among several helper AIs ("Agents") that work in the background at the same time. ## What it is A workflow is a plan for a large job: which Agents do which part, and in what order. The AI can start one on its own when a job is big enough, or you can run a saved one by name. The Agents work in the background while you keep chatting; when they finish, the result is posted into the chat and the AI continues from it. ## When to use it | Good fit | Not needed | |---|---| | The same check on dozens of files or records | A job that one pass can do | | Research with several independent parts | Work where each step depends on your answer | | A saved procedure your team runs often | Quick questions | ## How to use it 1. Ask for the job in plain words; the AI decides whether to use helpers. Or type `/workflow` to list saved workflows, and `/workflow ` to run one. 2. A task bar above the input box shows the active workflows and their Agents: **In progress**, **Paused**, **Completed**, **Failed** or **Stopped**. 3. Expand a workflow to see what each Agent is doing. **Pause**, **Resume** or **Stop** it there. 4. Open **More › Tasks** for the full list of this chat's tasks, including finished ones. 5. Keep chatting meanwhile. When the work finishes, the result appears in the chat. ## Example ```text Check every contract in this folder for a termination clause and a renewal date. Give me one table: file, clause found (yes/no), renewal date. ``` With many contracts, the AI splits them among Agents that read in parallel. The task bar shows their progress; when all are done, the AI posts one combined table. ## Limits and permissions - Two workflows can run in the same chat at the same time. - **Pause** waits for the current step to finish (**Pausing**), then stops before the next one. **Resume** continues from the same place. - More Agents use more of your model usage. ## If something goes wrong | What you see | What to do | |---|---| | An Agent shows **Failed** | Expand it to read the error, then ask the AI to retry that part | | The task bar disappeared | It only shows active work; open **More › Tasks** for finished ones | | The result looks incomplete | Ask the AI which items each Agent covered, and rerun the missing ones | ## Related - [Background Commands and the Task Bar](https://docs.micromeet.ai/skills/background-commands.md): Long commands running on your computer - [Scheduled Tasks](https://docs.micromeet.ai/skills/scheduled-tasks.md): Run a job at set times - [Common Workflows](https://docs.micromeet.ai/guides/common-workflows.md): Complete examples --- Source: https://docs.micromeet.ai/skills/background-commands.html # Background Commands and the Task Bar The AI can run commands on your computer — for example converting files or running a script. A command that takes long keeps running in the background, so the chat is not blocked. ## When to use it When the AI runs a long command on your computer and you want to see or stop it. ## How to use it - Background commands appear in the task bar above the input box, with their output. - **Stop this background task** ends one. - When it finishes, the chat shows **Background task finished** (or failed / stopped) and the AI continues with the result. You can keep chatting while it runs. --- Source: https://docs.micromeet.ai/skills/scheduled-tasks.html # Scheduled Tasks Let the AI do a job at set times: every weekday morning, every hour, or once next Friday. ## What it is A scheduled task is a request the AI runs on its own at the times you set. Each run happens in its own chat, with the same tools and the same back-and-forth as a normal chat, so you can open the run afterwards and continue the work by hand. ## When to use it | Good fit | Not a good fit | |---|---| | A report or summary you need every week | Something that must run while your computer is off | | Checking a website or folder for something new | Work that needs your decision at every step | | A reminder with a little work attached ("remind me and list what is still open") | A one-off job you can just ask for now | ## How to use it 1. Get the job right once in a normal chat, or turn it into a skill (see [Build Your First Skill](https://docs.micromeet.ai/skills/first-skill.md)). 2. Ask in a chat, for example: "Every Monday at 9:00, summarise last week's meeting notes in the workspace". The AI creates the task and tells you when it will run. 3. To see the runs, click the clock (**Scheduled tasks**) on the rail. A run waiting for you is marked. 4. To see every task with its schedule and run history, open **Settings › General › Scheduler**. 5. To change, pause, resume or delete a task, ask the AI. ## Example ```text Every Friday at 16:00, run weekly-summary on this workspace and save the result as weekly-summary-.md. If there are no notes this week, say so. ``` Every Friday a new run appears under the clock with the summary. If the AI needs you during a run, the run is marked until you answer. ## Limits and permissions - Tasks run only while Cowork is open. A time missed while it was closed is not made up later. - The shortest interval is 1 minute. - Each task uses the model it was set up with. If that model is not available when it runs, the run fails and says so. - Runs work in the current workspace, like a normal chat. - Run chats are not in **Sessions**. Archived runs are under **Archived Chat › Scheduled**. ## If something goes wrong | What you see | What to do | |---|---| | A task did not run | Cowork was probably closed at that time. Keep it open at the times the task runs | | A run failed because of the model | Open **Settings › General › Models** and check the model is signed in, or ask the AI to change the task's model | | A run is waiting | Open it under the clock and answer the card | ## Related - [Build Your First Skill](https://docs.micromeet.ai/skills/first-skill.md): Make the job a skill before you schedule it - [Workflows and Background Agents](https://docs.micromeet.ai/skills/workflows.md): Run a big job in parallel - [Conversations and History](https://docs.micromeet.ai/chat/conversations.md): Where normal chats live --- Source: https://docs.micromeet.ai/capture/recording.html # Record Web Activity A recording keeps what a website does while you or the AI use it in a tab: the pages and the requests behind them. ## What it is When a tab is recorded, Cowork keeps the website's requests in the background. From recordings it learns how the website works and writes an [API Doc](https://docs.micromeet.ai/capture/api-doc.md), so later jobs on that website can use its own functions instead of clicking through pages: faster and steadier. ## When to use it | Record when | No need when | |---|---| | The AI will work on this website often | You use the website once | | Jobs there are slow or break when pages change | The website already has a good API Doc | | You want the AI to export or update data in bulk later | | ## How to use it 1. Open the website in a tab and sign in. 2. Ask in a chat: "Record this tab", or "Record" followed by the website's address. 3. Use the website as you normally would, or let the AI do the job. The tab shows **This tab is being recorded**. 4. Ask "Stop recording" when you are done. 5. To see what was kept, open **Settings › Capture**. | In **Settings › Capture** | What it shows | |---|---| | **Recording** | What the current recording has captured | | **History** | Earlier recordings; **Export** saves one, **Clear** deletes one | | **Blacklist** | Websites that are never recorded | | **API Doc** | The functions learned for each website | ## Example You record your order system while you open the order list, filter to this month and open two orders. Afterwards the API Doc lists the website's functions for listing and reading orders, and the next time you ask "Export this month's orders", the AI uses them directly. ## Limits and permissions - Only tabs you or the AI start recording are recorded, and never websites on the **Blacklist**. - A website makes many requests unrelated to your work; a [capture whitelist](https://docs.micromeet.ai/capture/whitelist.md) keeps only the ones that matter. ## If something goes wrong | What you see | What to do | |---|---| | Nothing was captured | Check the website is not on the **Blacklist**, and that the tab showed **This tab is being recorded** | | The API Doc is missing functions you used | Record again while you do those steps | | Recordings take up space | Open **History** and **Clear** old ones | ## Related - [API Doc](https://docs.micromeet.ai/capture/api-doc.md): What Cowork learns from recordings - [Capture Whitelist](https://docs.micromeet.ai/capture/whitelist.md): Keep only the requests that matter - [Drill](https://docs.micromeet.ai/capture/drill.md): Let the AI explore a website on its own --- Source: https://docs.micromeet.ai/capture/whitelist.html # Capture Whitelist A website makes many requests that have nothing to do with your work — statistics, ads, images. A whitelist tells Cowork which ones to keep for a website. ## When to use it When you want recording to keep only what matters on a website and skip the rest. ## How to use it 1. Record the website for a short while (see [Record Web Activity](https://docs.micromeet.ai/capture/recording.md)). 2. Ask in the chat: "Make a whitelist for this site". 3. The AI looks at what was recorded and keeps only the business requests. ## Good to know - The whitelist works immediately, also for a recording that is running. - Each website has its own whitelist. A website with no whitelist keeps everything. - Ask the AI to show, add to or remove from the whitelist at any time. --- Source: https://docs.micromeet.ai/capture/api-doc.html # API Doc The API Doc lists a website's own functions that the AI can call directly, without clicking through pages. ## What it is From recordings or a drill, Cowork writes an API Doc for each website: its functions grouped by module, each marked **Read** or **Write**. When a job needs that website's data, the AI looks here first and calls the function with your own sign-in. This is how it reads or exports data quickly and reliably. ## When to use it | Good fit | Better another way | |---|---| | Regular exports or reports from a website you use | A website you use once: let the AI use the pages | | Bulk reading of records | Very large exports: ask for a [crawl script](https://docs.micromeet.ai/capture/crawl-scripts.md), which is built from the API Doc | | Updates where every write should be confirmed | | ## How to use it 1. Record the website, or drill it, so Cowork can learn its functions. See [Record Web Activity](https://docs.micromeet.ai/capture/recording.md) and [Drill](https://docs.micromeet.ai/capture/drill.md). 2. Open **Settings › Capture › API Doc** and choose the website. Its functions are grouped by module. 3. Check each function's mark: **Read** or **Write**. **Delete** a function you do not want the AI to use. 4. Ask for the job in a chat. The AI uses the API Doc on its own when it fits. ## Example ```text From our order system, export all orders from last week with their status into orders-last-week.csv. ``` The AI finds the order-list function in the API Doc, calls it page by page with your sign-in, and saves the CSV, without opening the pages. ## Limits and permissions - The AI calls functions with your own sign-in in that website's tab. - Before it calls a function marked **Write**, or one not known to be read-only, it asks you on an approval card. - Only you can mark a function **Read**. The AI cannot. ## If something goes wrong | What you see | What to do | |---|---| | A website has no API Doc | Record it or drill it first | | A function fails because you are signed out | Sign in again in that website's tab and retry | | The AI keeps clicking pages instead | Check the function it needs is in the API Doc; record the steps if it is missing | ## Related - [Record Web Activity](https://docs.micromeet.ai/capture/recording.md): How Cowork learns a website - [Crawl Scripts](https://docs.micromeet.ai/capture/crawl-scripts.md): Fetch large amounts of data - [When the AI asks you](https://docs.micromeet.ai/getting-started/workspaces-and-approvals.md#when-the-ai-asks-you): Which actions wait for your approval --- Source: https://docs.micromeet.ai/capture/drill.html # Drill A drill lets the AI explore a website on its own and write the API Doc for it, instead of you recording by hand. ## When to use it When a website the AI will use often has no API Doc yet. ## How to use it 1. Open the website in a tab and sign in. 2. Ask: "Drill this site". Better: name the data you need — "Drill this site for the customer list and orders". 3. The AI visits the pages, records them, keeps the business requests and checks that they can be called. 4. When it finishes, it reports which of your needs it covered and which it could not. ## Good to know - If the website needs a login, the AI asks you to sign in and continues after. - You can add instructions while it runs, or tell it to stop. - The AI avoids buttons that save or delete data while exploring. --- Source: https://docs.micromeet.ai/capture/crawl-scripts.html # Crawl Scripts To fetch a lot of data from a website — all orders, all records of a year — the AI writes a crawl script from the website's API Doc. ## When to use it When you need a lot of data from a website, such as every record of a month or a year. ## How to use it 1. Make sure the website has an API Doc (see [Drill](https://docs.micromeet.ai/capture/drill.md)). 2. Ask: "Crawl all orders of this month from this site". 3. The AI writes the script. A second AI checks it before it may run. 4. You approve the run on a card (**Run** / **Cancel**). 5. Ask "How far is it?" at any time. The data is saved on your computer. ## Good to know - The script uses your sign-in from the open tab; it never sees your password or tokens. - It requests slowly (at least one second between requests) so the website is not overloaded. - If the connection drops, run it again: it continues where it stopped. --- Source: https://docs.micromeet.ai/connections/mcp-servers.html # MCP Servers An MCP server gives the AI new tools from another product, for example a project tracker or a database. ## What it is MCP (Model Context Protocol) is a common way for products to offer tools to AI assistants. Many products publish an MCP setup. When you add one to Cowork, the AI can use that product's tools in your chats, signed in with your account for that product. ## When to use it | Good fit | Better another way | |---|---| | A product you use publishes an MCP server | The product is a website you already use in a tab: let the AI use the page, or its [API Doc](https://docs.micromeet.ai/capture/api-doc.md) | | You want the AI to read or update that product directly | You only need its data once: export and attach it | ## How to use it 1. Copy the product's MCP configuration (the `mcpServers` entry) from its documentation. 2. Paste it into the chat and say "Install this MCP server". The AI adds it, and can use its tools right away. 3. A server that needs a sign-in asks for it the first time. 4. Ask the AI to list your MCP servers, or to turn one off or on. ## Example ```text Install this MCP server: [paste the mcpServers entry from the product's docs] Then list my open issues assigned to me. ``` The AI installs the server, asks you to sign in to the tracker the first time, and lists your issues. ## Limits and permissions - The AI uses the server with the sign-in you give it, and sees what that account can see. - Changes a server makes in its product follow that product's own permissions. - Only add servers from products you trust; a server's tools run with the access you give them. ## If something goes wrong | What you see | What to do | |---|---| | The AI says it has no tools from the server | Ask it to list your MCP servers and check the server is on | | Sign-in keeps failing | Check the account in the product itself, then ask the AI to connect again | | The server's tools stopped working | Ask the AI to turn the server off and on again | ## Related - [Extensions](https://docs.micromeet.ai/connections/extensions.md): Add-ons that bring other channels into Cowork - [Encrypted Environment Variables](https://docs.micromeet.ai/connections/env.md): Store keys a server needs - [API Doc](https://docs.micromeet.ai/capture/api-doc.md): Use a website's own functions without MCP --- Source: https://docs.micromeet.ai/connections/extensions.html # Extensions An extension is a small program that adds a capability to Cowork, for example a connection to an outside chat channel. ## When to use it When you want to add a capability to Cowork that comes as an extension, such as a new message channel. ## How to use it Open **Settings › Extensions**: 1. **Install from folder** — choose the extension's folder; it is copied into Cowork. 2. Review it and click **Approve**. Nothing runs before you approve. 3. Switch it on. - Each extension runs separately from Cowork, so a crash does not take Cowork down. - **Logs** shows what it is doing. **Uninstall** removes it. - If its files change, it must be approved again. - Only you can approve an extension; the AI cannot. --- Source: https://docs.micromeet.ai/connections/gateway.html # Gateway: Outside Messages The Gateway lets an extension bring messages from an outside channel — for example a website chat — into Cowork, and send the AI's reply back to that channel. ## When to use it When messages from an outside channel, such as a website chat, should be answered by the AI in Cowork. ## How to use it It is off by default. Only you can switch it on, in **Settings › Gateway**: | Setting | What it does | |---|---| | Gateway switch, and one switch per channel | Turn message handling on or off. | | **Kill** / **Kill all** | Stop everything at once. **Lift the kill** to resume. | | **Persona and rules** | Who the AI is in this channel, and what it may and may not say. | | **Model** | The model that answers this channel. | | **File access** | Which folder the AI may read for this channel. | | **Trial** | Show you each reply for confirmation before it is sent. | | **Recent audit** | The last 200 records of what came in and went out. | The Gateway needs an extension that provides the channel (see [Extensions](https://docs.micromeet.ai/connections/extensions.md)). --- Source: https://docs.micromeet.ai/connections/whatsapp-seat.html # WhatsApp Seat (Connector) If your institution has a WhatsApp service number in Care Workspace, you can receive its customer messages in Cowork. ## When to use it When your institution has a WhatsApp service number in Care Workspace and you want its customer messages in Cowork. ## How to use it 1. Hover over **+** in the tab bar and choose the **Connector** mini-app. It shows a bar on top and WhatsApp Web below. 2. Click **Take seat**. If there are several numbers, pick one. 3. While you hold the seat, customer messages go into each customer's chat in Cowork, and the bar shows the latest one. 4. Click **Release**, or close the tab, to give the seat up. ## Good to know - One number is held by one person at a time. If a colleague holds it, you are asked **Take over this number?** — taking over disconnects them. - The seat stays on this computer until you release it or close the tab. - If your institution has no service number, the bar says so. --- Source: https://docs.micromeet.ai/connections/env.html # Encrypted Environment Variables **Safe Env** keeps API keys, tokens and other secrets encrypted on your computer, so the AI can use them later without you pasting them again. ## When to use it When a skill or connection needs a key or password and you do not want it written in a file or a chat. ## How to use it - **Save**: tell the AI "Save this key as MY_SERVICE_KEY" and paste the value. A new key is saved straight away. - **See**: **Settings › General › Safe Env** lists each key with its description and update time. Values are never shown. - **Use**: when the AI needs a value, you confirm first — on macOS with your password or Touch ID, on Windows in a confirmation window. - **Change or delete**: the AI shows a card with the key name; nothing changes until you approve. --- Source: https://docs.micromeet.ai/troubleshooting/ask-ai.html # Solve Problems with AI When something does not work or you are not sure how to do it, an AI can usually get you to the answer faster than reading page by page. There are three ways, from quickest to most thorough. ## Ask Cowork Cowork has a built-in **Manual** skill that knows the app. - In any chat, ask "How do I…?", for example "How do I add a scheduled task?" - Or type `/manual`, or `/manual` and a topic: `/manual skills` - To jump to a setting, type `/menu` to list the Settings tabs, or `/menu` and a tab name to open it ## Hand these docs to any AI Every page of this guide can go to an AI assistant along with your question: Cowork's own chat, or any other. - **One page**: click **Copy page** at the top of a page and paste it into the chat with your question - **The whole guide**: give the AI [docs.micromeet.ai/llms.txt](https://docs.micromeet.ai/llms.txt) (a list of every page) or [docs.micromeet.ai/llms-full.txt](https://docs.micromeet.ai/llms-full.txt) (every page in one file) A question that gets a useful answer says what you tried, what you expected and what happened: ```text I'm using Micromeet Cowork 0.1.41 on Windows 11. Using the guide below, help me fix this. What I did: asked the AI to open our order system and export this week's orders. What I expected: a CSV in my workspace. What happened: it stopped and said it needed me to sign in, even though I am signed in in the tab. [paste the page, or the llms-full.txt link] ``` ## Let the AI look at the logs Cowork keeps logs on your computer. An AI can read them and explain what went wrong. 1. Open **Settings › General › Develop** and click **Reveal in Finder** (or **Explorer**) next to the log files. 2. Attach the latest log file to a chat. 3. Ask: "Something went wrong at about 14:20. Read this log and tell me what failed and what I can do about it." See [Logs and Diagnostics](https://docs.micromeet.ai/troubleshooting/logs-and-diagnostics.md). ## When you contact support If the AI cannot solve it, contact Micromeet support with: - the **Version** and **Build** from **Settings › About** - the time it happened - what you did, what you expected and what happened - the log files ## Next steps - [Find a Fix by Symptom](https://docs.micromeet.ai/troubleshooting/by-symptom.md): Common problems and what to do - [Logs and Diagnostics](https://docs.micromeet.ai/troubleshooting/logs-and-diagnostics.md): Where the logs are and what support needs --- Source: https://docs.micromeet.ai/troubleshooting/by-symptom.html # Find a Fix by Symptom Find what you see, then follow the fix. If your problem is not here, [solve it with AI](https://docs.micromeet.ai/troubleshooting/ask-ai.md). ## Signing in | What you see | What to do | More | |---|---|---| | Wrong password, or "account not found" | Check the **Region**. Your account belongs to one region: Singapore, Hong Kong or Indonesia | [Sign-in Problems](https://docs.micromeet.ai/troubleshooting/sign-in-problems.md) | | Forgot the password | Click **Forgot password?** under the Sign in button | [Sign-in Problems](https://docs.micromeet.ai/troubleshooting/sign-in-problems.md) | | Signed in, but no data | You may be in the wrong institution. Switch institution | [Sign-in Problems](https://docs.micromeet.ai/troubleshooting/sign-in-problems.md) | | Never received the invitation email | Ask your institution administrator to send it again | [Sign-in Problems](https://docs.micromeet.ai/troubleshooting/sign-in-problems.md) | | Chat says your Claude or Codex session expired | Sign in again under **Settings › General › Models** | [Models and Reasoning Effort](https://docs.micromeet.ai/chat/models.md) | ## Chat and the AI | What you see | What to do | More | |---|---|---| | Message shows **Offline — sends automatically when the connection is back** | Nothing. It sends when the network returns. Up to 10 messages can wait | [Offline Queue and Retries](https://docs.micromeet.ai/chat/offline-and-retry.md) | | Status says **Connection lost, reconnecting** | Wait. It retries by itself | [Offline Queue and Retries](https://docs.micromeet.ai/chat/offline-and-retry.md) | | Chat says the conversation was interrupted | Send your message again | [Offline Queue and Retries](https://docs.micromeet.ai/chat/offline-and-retry.md) | | Chat says it can no longer restore its context | Start a new chat. The old messages stay readable | [Offline Queue and Retries](https://docs.micromeet.ai/chat/offline-and-retry.md) | | The AI seems to have forgotten something from much earlier | Long chats are compacted. Repeat the detail, or start a new chat for a new topic | [Long Chats and Automatic Compaction](https://docs.micromeet.ai/chat/compaction.md) | | The AI is waiting and nothing happens | Look for a card marked **Waiting on you** and answer it | [Tool Steps, Approvals and Decisions](https://docs.micromeet.ai/chat/tool-steps-and-approvals.md) | | The AI went the wrong way | Type a correction while it works, or click **Stop** | [Steering, Stopping and Taking Back](https://docs.micromeet.ai/chat/steering.md) | ## Web pages | What you see | What to do | More | |---|---|---| | The AI stopped at a sign-in, verification or payment page | Do that step yourself in the tab, then tell the AI to continue | [Let the Agent Use Web Pages](https://docs.micromeet.ai/browser/agent-browsing.md) | | A page does not load | Check the internet in another browser. If you use a proxy or VPN, check it is running or turn it off fully | [Network and Proxy](https://docs.micromeet.ai/troubleshooting/network-and-proxy.md) | | The Care Workspace tab stays empty | Right-click the tab › **Reload** | [Network and Proxy](https://docs.micromeet.ai/troubleshooting/network-and-proxy.md) | ## Skills and scheduled tasks | What you see | What to do | More | |---|---|---| | The AI does not use your skill | Make the description say when to use it, in the words you type. Or run it directly with `/name` | [What Makes a Good Skill](https://docs.micromeet.ai/skills/good-skills.md) | | A skill you edited outside Cowork still behaves the old way | Ask the AI to "reload skills", or start a new chat | [Built-in Skills](https://docs.micromeet.ai/skills/builtin-skills.md) | | A scheduled task did not run | Tasks run only while Cowork is open. A missed time is not made up later | [Scheduled Tasks](https://docs.micromeet.ai/skills/scheduled-tasks.md) | ## Installing and updating | What you see | What to do | More | |---|---|---| | Windows shows **Windows protected your PC** | Click **More info** › **Run anyway** | [Windows Notes](https://docs.micromeet.ai/troubleshooting/windows.md) | | Cowork disappeared when you closed the window (Windows) | It is still running in the system tray. Click the tray icon | [Windows Notes](https://docs.micromeet.ai/troubleshooting/windows.md) | | Not sure if you have the latest version | Open **Settings › About**. When a new version is ready, **Update** appears in the address bar | [Install and Update](https://docs.micromeet.ai/getting-started/install-and-update.md) | --- Source: https://docs.micromeet.ai/troubleshooting/sign-in-problems.html # Sign-in Problems ## Signing in to Cowork | Problem | What to do | |---|---| | Wrong password, or "account not found" | Check the **Region**: your account belongs to one region (Singapore, Hong Kong or Indonesia). | | Forgot the password | Click **Forgot password?** under the Sign in button. | | Asked to set a password | New accounts must set one before they continue. | | Signed in, but no data | Check the institution: in the Care Workspace tab, click its name › **Switch institution**. | | Never received the invitation email | Ask your institution administrator to send it again (**Institution › Staff › Send email**). | ## Signing in to Claude or Codex - Open **Settings › General › Models** and click **Login** next to the provider. The browser opens; finish the sign-in there and come back. - If the chat says your session expired, sign in again the same way. - A sign-in that hangs can be cancelled and started again. --- Source: https://docs.micromeet.ai/troubleshooting/network-and-proxy.html # Network and Proxy Cowork follows your computer's proxy settings. If a proxy is on in the system, Cowork uses it; if it is off, Cowork connects directly. There is nothing to set in Cowork. ## If something does not load - Check that the internet works in another browser. - If you use a proxy or VPN app, check it is running, or turn it off fully. - In the chat, messages sent while offline wait and go out by themselves when the connection is back (see [Offline Queue and Retries](https://docs.micromeet.ai/chat/offline-and-retry.md)). - If the Care Workspace tab stays empty, right-click the tab › **Reload**. --- Source: https://docs.micromeet.ai/troubleshooting/logs-and-diagnostics.html # Logs and Diagnostics When you report a problem, support usually needs three things: 1. The **Version** and **Build** from **Settings › About**. 2. The time it happened. 3. The logs. ## Find the logs Open **Settings › General › Develop** (**Developer Info**). It shows: - the app folders and log files — **Copy** the path, **Open** it, or **Reveal in Finder/Explorer**; - the environment; - the status of the last start. Logs are kept on your computer and old ones are removed automatically. --- Source: https://docs.micromeet.ai/troubleshooting/windows.html # Windows Notes - Cowork runs on 64-bit Windows 10 and 11. - If Windows shows **Windows protected your PC** when you run the installer, click **More info** › **Run anyway**. - Keyboard shortcuts use **Ctrl** where macOS uses **⌘**, for example Ctrl+N for a new chat. - Closing the window keeps Cowork running in the system tray. Click the tray icon to show it again; right-click it to quit. - Updates download by themselves; click **Update** in the address bar to install. There is no **Check Update** menu on Windows. - **Import Chrome Sign-ins** is not available on Windows. --- Source: https://docs.micromeet.ai/troubleshooting/release-notes.html # Release Notes ## 0.1.41 — 4 November 2026 - Improved scheduled tasks, which now run with full agentic power: the same tools and multi-turn conversation as a normal chat. - Improved chat performance when using Claude. - Fixed several known issues. This guide describes Cowork 0.1.41 and Micromeet CLI 0.0.25. It is updated with each release. --- Source: https://docs.micromeet.ai/miniapp-sdk/overview.html # Mini App SDK A Mini App is a web page that Cowork opens in its own tab. Inside it, Cowork adds one global object, `window.MAESTROSDK`, through which the page talks to Cowork. This chapter lists the modules of that object that Cowork supports and every function in them, in the same layout as a method reference. > **Release status** > Functions marked are in Cowork's source but not in a released version yet. Check that a function exists before you call it (see [Check what is available](#check-what-is-available)). ## Modules | Module | Functions | What it is for | |---|---|---| | [Lifecycle](https://docs.micromeet.ai/miniapp-sdk/lifecycle.md) | `beforeRefresh(handler)` | Keep unsaved work when someone refreshes the tab | | [Interaction](https://docs.micromeet.ai/miniapp-sdk/interaction.md) | `confirm(request)` | Ask the person a yes / no question in a native dialog | | [Models](https://docs.micromeet.ai/miniapp-sdk/llm.md) | `llm.providers()` · `llm.complete(request)` | Use one of the AI models Cowork already has set up | | [Package](https://docs.micromeet.ai/miniapp-sdk/package.md) | `package.get()` | Read the package this Mini App came from, and which extensions it has | | [Sign-in](https://docs.micromeet.ai/miniapp-sdk/auth.md) | `auth.login(params?)` · `auth.status()` | Sign the person in with their Micromeet account (signed packages only) | To build a Mini App that signs people in with Micromeet, start with [Build a Sign-in Mini App](https://docs.micromeet.ai/miniapp-sdk/sign-in-guide.md). To package a Mini App and have Micromeet sign it, see [Build and Sign](https://docs.micromeet.ai/miniapp-sdk/build.md); every rule the package must meet is in [Package Spec](https://docs.micromeet.ai/miniapp-sdk/package-spec.md). Every function above returns a `Promise` except `beforeRefresh`, and none of them throws for an expected failure: each returns `false`, `null`, an empty list or `{ ok: false, error }`, as its section says. The object also has a `connectors` module (`root`, `list`, `agentMdPath`, `readAgentMd`, `writeAgentMd`, `onAgentMdChange`). Cowork does not support it: its functions return empty results, `{ ok: false, reason: 'unsupported' }`, or throw `unsupported`. Do not use it in a Cowork Mini App. ## The Mini App folder In 0.1.41 only the Mini Apps that come with Cowork exist; you cannot install your own. From the next version: ```text miniapp/ manifest.json { appId, name, version, entry } index.html the entry page app.js app.css anything else it loads, by relative path ``` The file is `manifest.json` from Cowork 0.1.46; earlier builds read `miniapp.json`, so keep a copy under that name while people still use one. A Mini App can also be a signed package (`app.asar`): see [Build and Sign](https://docs.micromeet.ai/miniapp-sdk/build.md). | Field | Type | Required | Description | |---|---|---|---| | `appId` | `string` | Yes | Reverse-domain id, lowercase, such as `ai.micromeet.janeapp-operator`; at most 128 characters. The tab is `miniapp:` | | `name` | `string` or `{ zh, en }` | Yes | Name in the tab and menus; at most 60 characters | | `version` | `string` | Yes | At most 32 characters | | `entry` | `string` | No | Entry page, a relative path inside the folder, at most 256 characters. Default `index.html` | | `extension` | `string` | No | Only for a Mini App installed on its own: a folder inside it holding its one extension. A Mini App in a package leaves it out | - Pages load by relative path and use hash routing (`#/page`). - Each Mini App keeps its own storage (cookies, `localStorage`), separate from web tabs and other Mini Apps. Uninstalling clears it. - Install it as part of a package, together with its extensions and skills: see [Extension Overview](https://docs.micromeet.ai/extend/overview.md). ## Check what is available ```js const sdk = window.MAESTROSDK; if (sdk && sdk.package && typeof sdk.package.get === 'function') { const info = await sdk.package.get(); } ``` On an older Cowork, a module that is not there yet is simply missing; show the person a short note instead of failing. ## Related - [Extension SDK](https://docs.micromeet.ai/extension-sdk/overview.md): What the extensions of the same package can call - [Mini App](https://docs.micromeet.ai/extend/mini-apps.md): The Mini Apps that come with Cowork - [Extension Overview](https://docs.micromeet.ai/extend/overview.md): Which kind of addition to build --- Source: https://docs.micromeet.ai/miniapp-sdk/sign-in-guide.html # Build a Sign-in Mini App The path from nothing to a Mini App that signs a person in with their Micromeet account and then calls Micromeet for them from its own backend. Every function is described in [Sign-in](https://docs.micromeet.ai/miniapp-sdk/auth.md), packaging in [Build and Sign](https://docs.micromeet.ai/miniapp-sdk/build.md), and every package rule in [Package Spec](https://docs.micromeet.ai/miniapp-sdk/package-spec.md). ## The whole flow Who does what, from the first build to a person opening the Mini App: ```mermaid flowchart TB subgraph dev["You"] build["vite build
miniapp-package/"] verify["micromeet-miniapp verify"] zip["micromeet-miniapp zip
signed zip"] file["serve the verification file
at the backend's domain"] end subgraph mm["Micromeet"] reg["register the AppID
client secret per region"] dom["verify the server domain"] sign["register and sign the version
checks every file and domain"] end subgraph cw["Cowork"] install["install"] open{"signature valid
and files unchanged?"} run["open the Mini App"] refuse["not certified:
does not open"] end reg --> file --> dom build --> verify --> sign dom --> sign sign -->|signed manifest.json| zip --> install --> open open -->|yes| run open -->|no| refuse ``` Cowork checks the signature on every open, and every file whenever the page reads it; a changed file closes the Mini App. Signing in, after the person clicks your button: ```mermaid sequenceDiagram actor P as Person participant Page as Page participant C as Cowork participant M as Micromeet participant B as Your backend P->>Page: click Sign in Page->>C: auth.login() C->>M: who is this Mini App, what may it ask C->>P: card (first time): Mini App, scopes, account P->>C: Allow C->>M: a code for this version and person Note over M: AppID active, version registered,
same files, verified server domain, scopes M-->>C: code (5 minutes, once) C-->>Page: code and region Page->>B: code and region B->>M: code and client secret M-->>B: access and refresh token, user.ref B->>M: profile with access token M-->>B: name, email, institution B-->>Page: your own session ``` The page never sees a password, a token or the client secret. The steps below build each part. ## 1. Ask Micromeet to register the Mini App There is no self-registration. Send Micromeet: | What | Example | |---|---| | AppID: a lower-case reverse domain | `ai.example.app` | | Name (English; Chinese optional) and developer | Example · Example Ltd | | Scopes the Mini App needs | `profile:read` | | Regions of the people who will sign in (SG, HK, ID) | HK | | Your backend's origin | `https://api.example.com` | For each region you get a **client secret**, shown once: keep it in the backend's secret store. For each origin you get a verification file (step 2). ## 2. Prove you own the backend's domain Serve the file at `https://api.example.com/micromeet-miniapp-<16 characters>.txt` over HTTPS, with status 200 and no redirect, and leave it there; Micromeet fetches it to verify the domain. During development the backend can run on `http://localhost:` or `http://127.0.0.1:`, which needs no file in the regions where Micromeet allows it. See [Server domains](https://docs.micromeet.ai/miniapp-sdk/build.md#server-domains). ## 3. Write the page Install `@micromeet-ai/miniapp-sdk` (see [Build and Sign](https://docs.micromeet.ai/miniapp-sdk/build.md#build-it)), then: ```js import { maestroSdk } from '@micromeet-ai/miniapp-sdk'; const BACKEND = 'https://api.example.com'; // a verified server domain export async function signIn() { const sdk = maestroSdk(); // null outside Cowork if (!sdk?.auth) return { error: 'open_in_cowork' }; const login = await sdk.auth.login({ scopes: ['profile:read'] }); if (!login.ok) return { error: login.error }; const response = await fetch(`${BACKEND}/login`, { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ code: login.code, region: login.region }) }); return response.json(); // { session, name }: send session with later requests } ``` - Call `auth.login()` when the person clicks: Cowork shows its card only on the tab the person is looking at. - `auth.status()` says whether the package is signed and whether someone is signed in to Cowork; use it to show or hide the button. - Put every script in a file: inline `