Skip to main content
Glama

fileman is a local-first file organizer. Drop a messy folder. Get a manifest, a plan, and a one-click apply. Your originals never move until you say so.

┌──────────────────────────────────────┐
│  LOCAL-FIRST          ████████ 100%  │
│  SOURCE-TRACEABLE     ████████ 100%  │
│  TYPING REQUIRED      ░░░░░░░░   0%  │
│  VIBES                ████████ ZERO  │
│                                FILLER│
└──────────────────────────────────────┘

AI-assisted file triage. Manifest-first, never destructive.

What You Get

Surface

What

fileman cli

Scan, plan, manifest. Apply only when you nod.

fileman webui

Browse the plan. Approve, edit, or send back for another pass.

fileman mcp

Same engine, exposed as an MCP server for any agent.

contracts & manifest

Plans are diffable. Plans are reviewable. Plans are receipts.

public skills

Drop into Claude/Codex/OpenClaw. Hand it a folder. Get a library.

IMPORTANT

Local-first by default. No silent telemetry. No cloud round-trip. Your data stays on your machine until you explicitly ship it somewhere.

Related MCP server: Organizer MCP Server

Install

git clone https://github.com/xiaojiou176-open/fileman.git
cd fileman
# follow the per-stack quickstart in INSTALL.md or docs/

Three commands. No curl | sh. No login. Read what you run.

Install break? Open your favorite agent and say "Read AGENTS.md and bootstrap fileman for me." Agent fix own brain. Long version: docs/.

How It Work

The repo is seven layers — exactly the seven commits in git log. New work goes in as small named PRs. No 50-file mystery commits.

Layer

What

chore: scaffold

License, governance, hygiene gates, CI scaffolding.

feat(core)

The primary engine. The reason fileman exists.

feat(modules)

Packages, adapters, services, plugins. The second floor.

feat(contracts)

Schemas, configs, public boundaries. Other code talks here.

test:

Receipts. Everything in this layer must run.

feat(ops)

Scripts, infra, CI helpers, build glue.

docs:

Public docs surface. The pretty face.

git log reads like a building floor plan. Look once, know the whole shape.

Ecosystem

fileman lives in the yard family: seven yards. one philosophy: structured input, structured output, structured proof.

Repo

What

switchyard

model & agent runtime switch board

browserclickyard

your AI clicks, your browser obeys

noteyard

your Apple Notes never really die

dealyard

let prices fight, you sit and watch

docyard

docs site in, markdown out, no scraping by hand

fileman (you here)

messy folders in, organized library out

proofyard

every claim ships with its receipt

Cross-family taste: BeamMe · BrewMe · OpenVibeCoding · proofyard.

Star This Repo

If fileman saves you a click, an hour, or a headache — star costs zero. Fair trade. ⭐

Star History Chart

Also by Yifeng[Terry] Yu

License

MIT — small print, big freedom.

Available Tools

16 tools
analyze.createC

Create an analyze job without mutating files. Review still happens later.

Inputs: input_directory (required), model, offline, workers, +7 more. Returns: object

apply.previewC

Create an apply job in dry-run mode only.

Inputs: output_root, manifest_path, analyze_job_id. Returns: object

inbox.analyzeC

Create an analyze job from one watch source and optional discovered batch id.

Inputs: watch_source_id (required), model, offline, workers, +6 more. Returns: object

inbox.scanA
Read-onlyIdempotent

Run inbox discovery only. This does not auto-start analyze or apply.

Inputs: no named parameters. Returns: object

jobs.getC
Read-onlyIdempotent

Get one Fileman job by id.

Inputs: job_id (required). Returns: object

jobs.listA
Read-onlyIdempotent

List current Fileman jobs from the local workspace job store.

Inputs: no named parameters. Returns: object

manifest.batch_patchB

Patch multiple manifest rows through the overlay only.

Inputs: job_id (required), operations (required). Returns: object

manifest.getB
Read-onlyIdempotent

Get the manifest view for one job. Defaults to the resolved review view.

Inputs: job_id (required), limit, resolved. Returns: object

manifest.patch_rowB

Patch one manifest row through the overlay only.

Inputs: patch (required), job_id (required), row_id (required). Returns: object

report.getA
Read-onlyIdempotent

Get one persisted report plus the review bridge metadata.

Inputs: job_id (required). Returns: object

review_queue.getC
Read-onlyIdempotent

Get the review queue with deterministic copilot hints and collection slices.

Inputs: job_id (required), limit. Returns: object

review_rule.applyC

Apply a review rule to the overlay only. This does not execute file changes.

Inputs: job_id (required), rule, rule_id. Returns: object

review_rule.previewA
Read-onlyIdempotent

Preview a review rule against the current review queue without changing anything.

Inputs: job_id (required), rule, rule_id. Returns: object

runtime.settings.getA
Read-onlyIdempotent

Read the current local runtime settings.

Inputs: no named parameters. Returns: object

strategy_packs.listA
Read-onlyIdempotent

List repo-shipped strategy packs and the active local default.

Inputs: no named parameters. Returns: object

watch_sources.listA
Read-onlyIdempotent

List local-first watch sources and their linked strategy packs.

Inputs: no named parameters. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct action (list, get, create, preview, apply, scan, etc.) across different domains (jobs, manifest, review rules, inbox). Overlap is minimal, with only 'analyze.create' and 'inbox.analyze' slightly related but clearly differentiated by source.

    Naming Consistency5/5

    All tools follow a consistent `domain.action` or `domain.subdomain.action` pattern using lower_snake_case. Verbs like list, get, create, preview, apply, scan are used uniformly, making the naming predictable.

    Tool Count5/5

    With 16 tools, the set is well-scoped for a file management system covering jobs, manifests, review rules, inbox processing, settings, and reports. No tool feels redundant or missing in terms of count.

    Completeness3/5

    The tool surface covers core workflows (analyze, review, manifest patching, inbox scanning) but lacks execution tools for applying changes (only preview exists), job cancellation, or manifest creation. Some lifecycle gaps exist.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers