Founder pricing: up to 75% off a Meeteor license · 100 seats per tier, per platformSee seats left →
← All posts

Point Claude Code at a folder, get a Meeteor project

Meeteor is only as good as the project you give it. Before a call it needs the documents, a brief that says what the deal is and what you want, a note on where things stand, and a glossary so that "Dana" on the call finds "Dana Whitfield" in the project. Building that by hand is an hour of reading and typing, and it is exactly the hour nobody has before a call.

So Meeteor now has a command-line tool, meeteor-cli, and the interesting thing about it is not the commands. It is who can run them.

What the CLI does

It writes to the same database as the app, through the same code. project create and project brief set up the project. ingest queues files through the app's pipeline and waits until each is parsed, chunked and indexed. note add and glossary import do what their names say, and index what they add. search and ask let you check the result. There is a backup command, and it goes first.

Nothing in that list needs an AI key. Parsing, OCR and indexing run on your PC. Only ask talks to the AI route you set in the app.

What an agent does with it

I develop Meeteor with Claude Code, so it was the obvious thing to try: point it at a project's folder and a website, and ask for a Meeteor project. The prompt was a paragraph. What came back was better than what I would have typed myself.

It read a product's repository and its public site, wrote a three-paragraph brief, then wrote seven notes: where things stand as of today, the open queue and what to ask the other person on the call, who is who, the commercial facts, a timeline, a cheat sheet of the platform, and what the website says. It copied thirty-five documents in under descriptive names, so a card cites "Build log, one entry per task (Aug to Oct 2026)" instead of "BUILD-LOG.md". It built a glossary of a hundred people, companies, products and acronyms with aliases. It ran a backup first, imported everything, then searched the project for a question I would plausibly be asked and showed me the passages that came back.

The agent is doing the reading. Meeteor is doing the remembering. I am doing the call.

A few things I learned

  • Date the notes. "Where things stand (Oct 23)" is a fact. "Status" is a trap, because next month you will not know when it was true.
  • Rename on the way in. The file name is what the card shows. Give the agent that rule and it names everything sensibly.
  • Keep the deliberate gaps. I left out the engineering playbook, secrets and other people's personal files. The agent writes that list down, so the next refresh skips them too.
  • Re-running is cheap. Documents already in the project are skipped, glossary terms merge by name, the brief is replaced. Notes are added each time, so I replace a stale status note in the app.

Where it stands

The CLI is part of Meeteor and built from the same code as the app, but it is not in the beta installer yet. If you are on the beta and want it before it ships, write to me. The command line and coding agents page has the walkthrough, the example prompt and the glossary format.

Founder program

Bring your whole context to the next call.

Founder licenses are a one-time purchase per major version, up to 75% off, and limited to 100 seats per tier on each platform.