We finally got around to writing a blog. This is the first post.
There will be product updates and longer essays later. For now, the introduction: what Clico is today, how Desktop, Chrome and Web differ, why we built them, and the people helping us improve them.
What is Clico
Clico is an AI assistant for the screen you are on. Instead of asking you to rebuild the context in a separate chat, it starts from the page, app, file or task you choose.
Clico began in Chrome before expanding to Mac and Web.
There are three ways to use it. Desktop for Mac is the main workspace for work that crosses apps or depends on local files and screen context. The Chrome Extension works beside the current page, selection or text field. Web Agent gives longer browser tasks a conversation, visible progress and a place to return to later.
These are focused surfaces, not three interchangeable copies of one app. They use different context and keep different histories. The Clico product guide explains those boundaries in detail. The short version is to start with the surface closest to the work.
Three surfaces for three kinds of work
Desktop for Mac
Use Desktop when the useful context is spread across your Mac. Open the relevant app, file, image or screen, then tell Clico what outcome you need. You decide which context and system permissions are available. Clico can prepare work across supported tools, but important actions such as writing, sending, creating or clicking still require your approval.
Chrome Extension
Use the Extension when the page itself is the useful context. Focus a text field or select the text you want to change, then ask Clico to draft, rewrite, explain or summarize. A request can use the active page, the focused field, a selection or another tab you explicitly add. You review the result before inserting it into the page.
Web Agent
Use Web Agent for a longer browser task that you want to follow as a conversation. Describe the finished result, add only the inputs the task needs, then follow the run as it progresses. The Web conversation can be restored after a refresh or a later session. That history belongs to Web and does not automatically appear in Desktop or the Extension.
Why we built Clico
Clico fixes one specific thing. You should not have to rebuild the context every time you ask AI for help.
Sometimes that context is a draft in Gmail. Sometimes it is a spreadsheet beside a document on your Mac. Sometimes it is a longer task with attachments, connected apps and decisions you want to revisit tomorrow. Moving all of that into a blank chat means copying text, explaining what is open and repeating details the work already contains.
What this loop takes from you is bigger than it looks. Your rhythm goes with it, and so do the small details that explain why a message, document or decision matters.
Clico starts from the opposite end. Choose the surface where the work already lives, provide only the context the task needs, and keep control of what happens next.
A normal afternoon: how Clico helps you
Three moments from a regular working day show why the surfaces are different.
You open Gmail to reply to a customer asking for something you cannot ship this week. The reply needs to be clear without overpromising. The Chrome Extension can use the open thread and focused reply field while you ask Clico to polish the email. You review the draft where it will be sent.
Later, the answer you need is split between a document, a spreadsheet and an image on your Mac. Desktop lets you bring the relevant screen or file into one task. You can ask what is missing, prepare the next step and review any proposed action before it changes another app.
At the end of the day, you start a longer research task in Web Agent. The result does not need to be finished in one sitting. You can follow the run, return to the saved Web conversation and continue from the same browser workspace.
The point is not to force every job through the same interface. It is to keep the useful context close and choose the amount of workspace the task actually needs.
The practical stuff
If you are unsure where to begin, choose Desktop for work across apps, the Extension for work beside a page, and Web Agent for a longer task you want to revisit. The public Clico access page keeps all three entry points together.
Do not assume that context or history automatically follows you between them. Desktop, Extension and Web currently keep separate history models. Use the surface that contains the context you need, and open the detailed product guide when permissions, storage or current limits matter.
Current plan and credit details are on the pricing page. For sensitive work, read how Clico handles your data before deciding which context to provide.
Our users help shape what Clico becomes
These photos are from our partnership with GDG University Ambassadors. The students in the Clico shirts are part of that program.
We work with GDG ambassadors because students move between documents, messages, research and projects all day. They quickly find the places where a product loses context, asks for too much setup or gets in the way of the work.
The ambassador program is open beyond the GDG partnership. Anyone who wants to share Clico with their audience can join through Dub Partners in about a minute. You earn 50 percent of every referred sale for one year and your referrals get 20 percent off their first purchase.
Outside the ambassador program, we keep a Discord where users tell us what is broken in real time. We also sit down with a smaller group of users for longer one on one conversations. The biggest product decisions come from those conversations.
Feedback matters even more now that Clico has three surfaces. A task that feels natural beside a Chrome page can feel cramped when it spans several Mac apps, while a longer Web run needs progress and history that a quick rewrite does not. We use those differences to decide what belongs in each product.
If you want a seat in that loop, the Discord and the ambassador program are the two ways in.
That is the current tour. Start with the surface closest to the work, then move only when the task needs a different kind of context.
If something does not work once you have it, tell us. hey@tryclico.com lands in an inbox a real person reads. Replies are slow but they always come.