fff.nvim vs OpenAI GPT-4o Computer-Use API

“The MCP integration and frecency scoring for agents is genuinely useful — I've measurably reduced token burn in Claude Code sessions by pointing it at fff.nvim instead of raw glob calls. The Rust prebuilts mean zero configuration pain. Strong ship.”

“The primitive here is clean: you send a screenshot, get back an action (click, type, scroll), execute it, send the next screenshot. It's a loop you own, not a platform you adopt, and that's exactly the right DX bet — put the orchestration complexity on the caller, not inside a black-box agent runtime. The moment of truth is wiring up your first sandboxed browser session, and the docs actually walk you through it without requiring five env vars before hello-world. The specific decision that earns the ship: the `computer_use` parameter slots into the existing Chat Completions endpoint rather than spawning a new API surface, so there's no new auth, no new SDK, no new mental model to adopt — it composes with what you already have.”

“Telescope and fzf-lua have years of plugin ecosystem maturity. The agent-aware MCP angle is clever marketing but how many Neovim users are also running Claude Code via MCP? The overlap feels narrow. Wait until the agent integrations mature.”

“Direct competitors are Anthropic's Computer Use (which shipped this pattern first) and browser-automation layers like Playwright with vision models bolted on — so OpenAI is late, not pioneering. The scenario where this breaks is multi-tab stateful workflows: the model loses context across long action chains, and the sandboxed environment means anything requiring persistent login state or SSO is a pain to set up correctly. What kills this in 12 months isn't a competitor — it's OpenAI themselves shipping a higher-level 'Operator' abstraction that makes this raw loop feel like assembly code, at which point developers stop using the primitive directly. What earns the ship anyway: it actually works on the class of tasks it's designed for (form-filling, data extraction from non-API sites), and the integration path for teams already on the OpenAI stack is genuinely low-friction.”

“Agent-aware developer tools are a new category. Once your IDE and file search are MCP-native, the agent can navigate your codebase as efficiently as an experienced human dev — without wasting 40% of its context window just finding the right files.”

“The thesis here is falsifiable: by 2028, the majority of software integration work will happen via UI-layer automation rather than API negotiation, because the long tail of enterprise software will never expose clean APIs. The dependency that has to hold is that vision-action loop latency drops fast enough to make real-time task automation economically viable — right now at several seconds per action step, synchronous workflows are painful. The second-order effect that matters most isn't developer productivity; it's that this decouples automation from cooperation from the software vendor — no partnership, no webhook docs, no SDK required. OpenAI is riding the trend of 'software that wasn't built for machines getting used by machines,' and they're on-time, not early — Anthropic already planted the flag. If this tool wins, the infrastructure state is: sandboxed browser runtimes become a commodity layer the way Lambda functions did, and the fight moves entirely to which model makes the fewest misclicks.”

“This is deeply Neovim-specific and developer-focused. If you're not living in a terminal editor with AI agents piped into your workflow, nothing here is for you. Pass.”

“The buyer is any developer team automating workflows against software that lacks APIs — which sounds like a wide market, but the pricing is the problem: at GPT-4o token rates plus screenshot tokens per action step, a 20-step task can cost more than a human doing it once, and at scale that unit economics breaks before the product does. The moat is zero: this is a capability that Anthropic, Google (Gemini + Project Mariner), and any open-weight model with vision can replicate, and OpenAI's only durable advantage is model quality, which is a temporary lead not a structural one. What would have to change for this to earn a ship: a pricing tier that caps cost per completed task rather than per token, so that developers can build products with predictable margins on top of it — right now you're taking on model cost volatility every time a task gets more complex.”