I’ve been building a terminal for running coding agents next to local models. Looking for feedback from Ollama users

I’ve been working on a macOS terminal called Tellurion for the past few weeks. It started as a Ghostty fork (it was GhosttyEXTREME until last week) because I kept running several coding agents at once and losing track of which one needed me. The part I think is relevant here: your Ollama models show up in a sidebar and you can drag one into a chat next to whatever else is running. You can also pull models from inside the app. In the video, Goose and OpenCode are both running on qwen3:4b through Ollama, alongside Claude Code and Codex. LM Studio, llama.cpp, MLX and Apple’s on-device model work too. Some other things it does: shows each agent’s status so you can see which one is waiting on a permission, lets you approve those from your phone over Tailscale, and has a Visual Fix mode where you click an element in your running app and send the change to an agent. Everything runs locally, there’s no account or telemetry, and it’s AGPL. It’s macOS and Apple silicon only, and it’s just me working on it, so there are rough edges. A couple I already know about: the sidebar doesn’t always notice right away when a model unloads, and Visual Fix can trigger a hydration warning in React apps. What I’d really like to know from people here: which local models have actually worked for you in agent workflows, and what would make running them alongside cloud agents more useful? https://github.com/steventsvik/Tellurion submitted by /u/Resident-Priority326 [link] [comments]

Related

• Locus - A MacOS tool for Ollama and other local models
• Ollama works locally, but my coding-agent integration does not
• I built an open-source local agent experiment with Ollama to explore what sits between 'chat' and actual everyday work

Source: r/ollama | 2026-10-18