Flint

A crew on your machine

Your models. Your agents.

A senior splits the job. The workers do it in the folder you open. You see who touched what.

Flint

          
calculator.pyAgent

One job. Three workers. You watch.

Senior does not write the whole fix. It gives calculator.py to one worker and the tests to another. The third waits, because they share one model. Each row is a face, the file, and one sentence. The full brief stays closed until you open it.

The line is the work

Editing calculator.py means that worker has the file. Waiting for the model means they have not started. Those are not the same thing.

The folder is the limit

They read and write only the project you opened. The diff sits under the editor. A command does not run until you allow it.

The model stays yours

A local model, or an API key you already have. Several agents can share one. They take turns, and the row says whose turn it is.

From install to the first job.

01

Open Flint

Local. Private. Yours.

The model runs on your machine. The files stay in the folder you open. Flint is only the window.

Chats stay on this computer

There is no Flint account, and the folder is not uploaded. A web search goes to DuckDuckGo, or to Brave if you add a key. An update check asks GitHub whether a newer Flint exists. You can turn that check off.

Only the folder you choose

The agents can read and change that folder. The rest of the machine stays out of reach.

A crew you name yourself

Add the agents you want and call them whatever fits. One can lead. The others take a piece each, at the same time.

You keep the last word

A change waits until you keep it. A command does not run until you allow it.