u/Broad_Chemistry1080

Kevu laage aam desperate chokrav aaju baaju Che .. badhu kidhu Hu chokro chu to bhi accept nhi karto

I've been working on miii-cli — a terminal-based AI coding assistant that runs entirely on local models (Ollama, LM Studio, vLLM, whatever OpenAI-compatible endpoint you point it at). No API keys, no cloud calls, no usage limits.

To actually stress-test it instead of just demoing toy prompts, I gave it one task: build a Python app that zooms in and out using two-finger trackpad gestures.

I didn't touch the code myself. miii-cli:

• read the project structure
• wrote the gesture-tracking logic
• ran it
• hit a bug (gesture distance wasn't normalizing right)
• rewrote the function
• ran it again until it worked

End result: a small Python app where pinching in/out on the trackpad smoothly zooms a view in real time, powered fully offline.

Nothing revolutionary about the demo app itself — it's simple on purpose. The point was seeing whether a fully local, no-cloud setup could actually handle an iterative build-test-fix loop without hand-holding. It did.

Repo's here if you want to poke at it or run your own local model against it: https://github.com/maruakshay/miii-cli

Happy to answer questions about the architecture, model setup, or why I went local instead of just wrapping Openai or claude .

github: https://github.com/maruakshay/miii-cli

Check more on

Github: https://github.com/maruakshay/miii-cli

NPM: https://www.npmjs.com/package/miii-agent

I kept typing the same things over and over all day — my email, my address, a support reply I send constantly, code blocks I always reach for. Copy-pasting from a notes file or retyping from memory got old fast.

Chrome doesn't have a built-in way to say "when I type addr, drop in my full address," so I made one.

It's called CopyTap. You store a snippet once (addr → your full address), then trigger it anywhere by typing a short key with a prefix, like :addr. The moment it matches, it swaps in the full text — no clicking, no menus.

• Works in any input, textarea, or rich-text field, on any site
• Snippets sync across your signed-in Chrome via chrome.storage.sync
• Import/export everything as JSON

It's free and open source. Would love feedback, especially on edge cases with weird input fields.

GitHub: https://github.com/maruakshay/copytap

We don't have a shortage of terminal coding agents. We have a shortage of local models that can run the loop: read a file, edit it, run a command, check the output, and not fall apart halfway through.

That was the real pain for me. Almost never the agent. It was the model looping, mangling tool-call formatting, or ignoring the result of the command it just ran. And you don't find out until you're an hour deep.

So I built around that bottleneck. miii is a terminal agent that runs fully on local models via Ollama or any OpenAI-compatible endpoint (LM Studio, vLLM, etc):

• u/filename to inject file context
• model reads, writes, edits, and runs shell commands itself
• tool calls chain up to 6 hops, so it reads → edits → runs → verifies in one pass
• miii doctor checks if your setup is even capable first: Ollama up, model pulled, and whether the model returns valid tool calls

Repo: https://github.com/maruakshay/miii-cli

Which local models actually hold up in a multi-step tool loop for you? In my testing some sub-8B models can't keep tool-call JSON straight past two hops. Curious what's working, and what breaks if you try it.

We don't have a shortage of terminal coding agents. We have a shortage of local models that can run the loop: read a file, edit it, run a command, check the output, and not fall apart halfway through.

That was the real pain for me. Almost never the agent. It was the model looping, mangling tool-call formatting, or ignoring the result of the command it just ran. And you don't find out until you're an hour deep.

So I built around that bottleneck. miii is a terminal agent that runs fully on local models via Ollama:

• @ filename to inject file context
• model reads, writes, edits, and runs shell commands itself
• tool calls chain up to 6 hops, so it reads → edits → runs → verifies in one pass
• miii doctor checks if your setup is even capable first: Ollama up, model pulled, and whether the model returns valid tool calls

Repo: https://github.com/maruakshay/miii-cli

Which local models actually hold up in a multi-step tool loop for you? In my testing some sub-8B models can't keep tool-call JSON straight past two hops. Curious what's working, and what breaks if you try it.