Which AI works with lite.computer

Any AI that can save an HTML file into your folder can work with lite.computer. If your AI only creates a downloadable file, save it to your Showspace yourself. The app displays the same page either way.

Check two things: how the page reaches your Showspace, and whether the AI can connect to lite.computer to open pages and arrange windows.

Agents working on your Mac

Agents with access to your Mac can save directly into your Showspace. Those that support the app’s MCP connection can also open pages and arrange windows. See Give your AI the app’s commands.

• Claude Code — a terminal, the Claude desktop app, or your editor. Built for long unattended runs, so it suits a job with twenty steps in it.
• Claude Desktop, including the Cowork tab — your files and scheduled work, without a terminal anywhere in sight. A good place to start if you would rather not work in a terminal.
• Codex — OpenAI's agent, in a terminal or built into the ChatGPT desktop app, which now works with your local files and apps through it.
• ChatGPT Work — OpenAI's agent for working across your apps, files and documents. Same rule as the rest: what it can reach depends on where it runs.
• Antigravity — Google's, as a desktop app and a terminal tool, with agents that plan a job and then check their own work.
• Cursor — editor-first, if that is where your day already happens.
• Gemini CLI — Google's agent in a terminal, working on the files in the folder where you start it.
• Hermes — runs as a permanent process rather than a session, remembering across conversations and working on a schedule. Good for a Showspace that should be current before you open it.
• OpenClaw — reached through the messaging apps you already use. Ask for a page from your phone over Telegram or WhatsApp, and the machine at home writes it.

This list is not complete. Any AI that runs on your Mac and can save an HTML page into your Showspace works with lite.computer. If it can also connect to the app, it can open pages and arrange windows for you.

Agents that keep working while you are not

Grok Bot is the one to know here, and it sits in neither group above. xAI's Bots share a cloud computer of their own and sign into your tools the way a person would, so they carry on after you close your laptop.

A cloud agent can prepare a daily brief, update records or rebuild a dashboard while your Mac is off. The finished HTML still needs to reach your Showspace: through a cloud folder the agent can write to, or a transfer when your Mac is on again.

For a schedule that runs on your Mac, keep the Mac awake and the agent or refresh job running.

A cloud task cannot use lite.computer’s local connection to open pages or arrange windows. Use a connected agent on your Mac for those actions.

What connecting the app adds

This is the part worth setting up. A connected agent does not just write the page. It can put it in front of you.

• Open a page on your second screen while you keep working on the first.
• Explode your open tabs into a window on every display you own, so the whole desk becomes one dashboard. See Explode and Implode.
• Check the Showspace for broken links and missing images, and then fix them.

Twenty commands in all, including switching Showspaces by name. See Every command your AI has.

Away from your desk

You do not have to be sitting at the Mac. Several of these let you start or continue work from your phone while the Mac does it.

• Claude Code Remote Control — pick up a session running on your Mac from the Claude app on your phone, or from a browser.
• Codex — the same idea, from the ChatGPT app.
• Claude Cowork Dispatch — hand a task to your desktop Cowork session from your phone. Aimed at people who do not want a terminal at all.
• Hermes and OpenClaw — reached through the messaging apps you already use, so you ask in Telegram or WhatsApp and the Mac gets on with it.

All of these keep the work on your machine, which is the part that matters here: your phone is the remote, and the Mac is still the thing writing into your Showspace and driving the app. The Mac does need to be awake.

From a browser, with nothing installed

Some browser assistants can reach cloud folders through connectors. Support depends on the product, your plan, permissions and file type. Check that the connector can read HTML files, not just Google Docs.

Try it with one page: ask your assistant to read an HTML file from your Showspace and summarize its contents.

For writing, ask it to save a file called test.html into your chosen folder, then check that the file reaches lite.computer. Grok’s Google Drive documentation lists uploads of generated files with write permission. That supports a possible route; a one-file test confirms whether HTML delivery works in your account. If it cannot save the file there, download it into your Showspace yourself.

The limits, and what to use instead

A short list, and every item on it has a route that works, usually the same tool in a different place.

• A cloud assistant cannot use the app’s local connection. It may still read or write pages through a cloud connector. Use an agent on your Mac to control the app.
• A desktop app does not automatically have file access. Choose a local task and give the agent access to your Showspace. A cloud task in the same app may use a different computer.
• Claude's Google Drive integration reaches Google Docs, not your HTML pages. This is only about the web and phone apps — Claude Code or Claude Desktop on your Mac has no such limit.
• A browser assistant cannot reach iCloud Drive at all. No major one offers an iCloud connector today. If reaching your pages from a browser matters, keep the Showspace in Google Drive instead — see Where to put your Showspace.
• Hermes or OpenClaw running on a server somewhere else will still write into a synced folder, but it is not on your Mac, so it cannot drive the app. Run it on the Mac if you want both.
• Your Mac has to be awake for anything driven from a phone. The phone is a remote, not a second computer.

Picking one

Most people end up with two: an agent on the Mac that writes the pages, and whatever assistant is on their phone for reading them later.

• Comfortable in a terminal — Claude Code or Codex CLI.
• You would rather not use a terminal — Claude Desktop.
• You want the Showspace already up to date when you open it — Grok Bot, on a schedule. It can prepare updates while your Mac is off; check how it delivers the files to your Showspace.
• You want pages current without asking — either an agent that runs on a schedule, such as Hermes or scheduled work in Cowork, or better for anything data-driven: have any of them write you a small script and run that on a schedule instead. Steadier and cheaper than waking a model every hour.
• You want to ask from your phone and have it happen at home — OpenClaw.
• You are in a code editor all day anyway — Cursor or Antigravity.
• You work mostly from a browser or a phone — keep the Showspace in Google Drive and run the one-file test above.

We keep a page on every agent we know of, with the setup steps, where its standing instruction goes and whether it can use the app's commands: Aider, ChatGPT, Claude Code, Claude Desktop and Cowork, Cline, Codex, Cursor, DeepSeek Harness, Gemini CLI, Google Antigravity, Grok Bot, Grok Build, Hermes Agent, Kimi Work, Kiro, Manus, Mistral Vibe, Muse Code, Open Interpreter, OpenClaw, Qwen Code, TraeCode.

You are not choosing once

Any local agent you point at the folder writes ordinary HTML files into it. Nothing here ties you to one: change your mind, change agents, and every page you already have is exactly where you left it, still opening in any browser on earth.

That is the whole reason the app reads a folder rather than a service.

The quickest way to find out is to try it. The trial is the complete app for fourteen days, with no account and no card, so you can point whatever AI you already use at a folder this afternoon and see what comes back. See The 14-day trial.