Movi

Movi is a review-first local file organizer and workbench for messy photos, screenshots, documents, and audio. It lets AI assist with the manifest first, then lets you inspect, label, and approve the plan before deterministic apply or rollback touches your files.

Safe First Look · 10-Second Tour · Good Fit / Not A Fit · Public Proof · Docs · Distribution · Integrations · Submission Manifest · MCP Descriptor · Review-First Skill Packet · OpenClaw Bundle · Browser Surface · Releases · Discussions · Security · Movi MCP v1 · Codex Integration · Claude Code Integration · Developer Guide

Movi is a review-first local AI file organizer. It turns a chaotic intake folder into a review queue, then into a reviewed manifest, and only then into safer file moves you can dry-run, audit, and roll back. The current shipped surface stays intentionally narrow: Movi Review, Movi Rules, Movi Inbox, Movi Copilot v1, and Movi MCP v1 all describe real current surfaces, but they still stay inside one safety story instead of pretending Movi is an autonomous organizer.

Public maintenance posture: limited-maintenance open source.

Current proof posture: reproducible smoke-tier evidence with a live release trail, Pages front door, and repo-side safety gates. It is not broad benchmark-grade proof yet, but the current front door already clears a truthful public-entry bar, and the proof routes stay explicit in Public Proof instead of being buried in operator-only docs.

Canonical Public Roots

Read Movi like a workshop with one front desk and several labeled shelves:

• Canonical public root: this root README.md plus the root manifest.yaml
• Canonical pure-MCP registry descriptor: server.json
• Current pure-skills packet: examples/skills/
• Host-specific supporting bundle: examples/openclaw/
• Pure-MCP support surface: docs/mcp.md
• Pure-MCP runtime implementation guide: apps/mcp/README.md

Why Movi Exists

Cleaning up a mixed folder usually fails for one of two reasons: either the tool is too manual, or the AI is allowed to move files before you can inspect the plan.

Movi splits those jobs on purpose:

• analyze is where AI helps understand the files
• apply is where deterministic rules execute the approved manifest
• rollback is where you can undo with the same paper trail

Think of it like moving house: AI makes the packing list, but the moving crew still follows an approved checklist instead of guessing in the hallway.

What You Get

• Review-first workflow: AI drafts the manifest, but file changes only happen after you inspect the plan.
• AI-assisted, not AI-autonomous: Movi helps draft and suggest, but deterministic execution still waits for your approval.
• Dry-run by default: you can see what Movi wants to do before a real rename or move happens.
• Rollback-ready workflow: the same manifest chain supports recovery when a batch needs to be undone.
• Local-first runtime: your folders, manifests, and reports stay under your chosen workspace root.
• Operator-grade guardrails: quality gates, structured logs, and release runbooks exist for people who need deeper operational truth.

... View full README on GitHub