Organize
Keep your Drive in order, with the AI you already use
Mica maps your folders and checks every file in them, from Google Docs and Sheets to PDFs and Word files, for the mess that builds up: duplicates, old versions, empty files and broken links. Your AI turns that into a proposed cleanup, and you decide what changes.
How it works
Mica does the checking. Your AI does the thinking. You approve the changes.
- 1
Mica checks
When you or your AI ask, Mica reads the folder and works out the facts: every file in it, whatever its type, how they are named, what links to what, and which files are duplicates or old versions of each other. The same folder gives the same answer every time, and no AI model is involved.
- 2
Your AI decides
Claude, ChatGPT or Codex reads those facts, plus the docs it needs, and works out what should change and why: a one-line summary of each doc, which version is current, and where a stray file belongs.
- 3
You approve
The cleanup comes back as a proposal you review in Mica, with a reason for every change. Accept all of it, some of it or none of it, and undo it later if you change your mind.
What it finds
The mess that builds up when files arrive faster than anyone files them
Duplicates
Two files with the same contents, whatever they are called.
Old-version chains
The same file saved again as v2, final, revised or a copy.
Empty and scratch files
Files with next to nothing in them, and leftovers named Untitled, Scratch or zz.
Broken links
Links in your docs to files that no longer exist, with the likely target when there is exactly one.
Names that break the pattern
A file named differently from the series most of its folder follows.
Unfiled items
Files sitting in an Inbox folder, waiting for a home.
It also flags docs nothing links to, current docs that may have fallen behind the docs around them, mentions of another doc that could be links, and very large docs. Which checks a file gets depends on what Mica can read in it: an image or an archive is checked by name, size and exact duplicates. Every check ends with a health score from 0 to 100: the share of files with nothing to fix.
Folder check
- Duplicate
- Old-version chain
- Empty doc
- Broken link
- Name breaks the folder’s pattern
Who does what
Facts from Mica, judgment from your AI, decisions from you
Mica works out
- Every file in each folder, whatever its type, and each doc's status: draft, current, superseded or archived
- The naming pattern a folder already follows
- Links, backlinks and broken links
- Duplicates and old-version chains
- The health score
Your AI proposes
- A folder's purpose and conventions, and which docs to start with
- A one-line summary of every doc
- Which version is current, and what it replaces
- Moves, renames, merges, archives and trash, each with a reason
You decide
- What actually changes, item by item
- What to undo afterwards
- In a team folder, each owner decides for their own docs
Mica never calls an AI model to organize your folders. The judgment is your own AI's, on your own account, so there is no second AI bill.
Review and undo
You review before anything changes
Your AI sends a cleanup as a proposal: each move, rename, status, merge or trash with the reason for it. You see it on a review page in Mica and accept what you agree with. If you tell your AI to go ahead without a proposal, every change is still recorded, and can be undone.
- Accept all, accept some or reject them, item by item
- Undo changes later; trashed files and merged docs can be brought back for 30 days
- Nothing is permanently deleted, and a merge keeps the older versions in the surviving doc's history
- In a team folder, a change to someone else's doc waits for its owner (or, in a Shared Drive, a team admin) to accept it
- The record of each set of changes is a file in your own Drive, in the folder it touched
The map
INDEX.md: a map your AI reads first
Ask your AI to map a folder and Mica saves the result as INDEX.md in that folder: its purpose, its naming conventions, the docs to start with, every file in it, and a one-line summary of each doc. Any AI that reads the folder, through Mica or straight from Drive, can start there.
- A plain-text file you keep, useful with or without Mica
- Written only in folders where you or your AI asked for one, and kept current while you work there, never on a timer
- Visible in Drive to anyone who can open the folder, and to no one else; hidden in Mica so it never clutters your tree
- The summaries come from your AI; Mica keeps the list of files, dates and statuses up to date
Three commands
Ask in plain words, or use the shortcut
In apps that show MCP prompts as commands, such as Claude, each routine is one command. Anywhere else, ask for the same thing in your own words.
/index- Maps a folder: saves its purpose, conventions, start-here docs and a summary of each doc in INDEX.md. It changes only that file.
/tidy- Proposes a cleanup: one set of changes for you to review. It changes nothing until you say yes.
/garden- A full check-up: maps the folder, leaves a comment where an older doc contradicts a newer one, then proposes a cleanup.
Questions, answered
Does it delete anything?
Mica never permanently deletes a file. A file your AI suggests removing goes to Drive's trash only once you accept, and you can bring it back for 30 days. Merging a version chain keeps the older versions in the surviving doc's history.
Does it work with Google Docs, Sheets, PDFs and Office files?
Yes. Folder upkeep covers every file in the folders you connect, whatever its type: your AI can propose moving, renaming or trashing any of them, and nothing changes until you approve. Mica edits only its own docs; everything else opens where it always has.
Do I pay for the AI?
Not to Mica. Folder upkeep runs on the AI you already use, on your own Claude, ChatGPT or Codex account, and whatever that plan costs is between you and them. Mica never calls an AI model for it, and Mica itself is free during early access.
Does it run in the background?
No. Mica checks a folder only when you or your AI ask; nothing checks your folders on a schedule. If you want a weekly check-up, set one up in your AI (in Claude, as a scheduled task): each run leaves its cleanup as a proposal for you to review.
Does Mica read my documents to check them?
Only when you or your AI ask for a check, and only in that connected folder. The text is held in memory for that one request and is never logged or stored. What Mica keeps are derived facts, such as which doc links to which, and it keeps them in the folder's own INDEX.md.
Who can see a folder's INDEX.md?
Anyone who can open the folder in Drive, and no one else: it is a file in that folder with the folder's own sharing. A subfolder with narrower access is left out of its parent's map. Mica never shares the file on its own.
Does it work in team folders and Shared Drives?
Yes. Each person sees only what Drive lets them open, and a proposed change to someone else's doc waits for its owner to accept it. In a Shared Drive, where docs have no single owner, a team admin can.
What if I stop using Mica?
Your files and your folder maps stay exactly where they are in Drive. Mica docs are plain markdown any app can open, and each INDEX.md says at the top that Mica maintains it, so any person or tool can tell what it is.
Connect a folder. Ask your AI to map it.
Free during early access. Your files and your folder maps stay in your own Drive.
Start free