
Today I was confused by Antigravity errors about high load on their services. It made my work...
Today I was confused by Antigravity errors about high load on their services. It made my work impossible even with the cheapest model Gemini 3 Flash.


Some time ago I heard something about the OpenCode. And it was the time to try it!
I've installed the opencode in my system by brew install anomalyco/tap/opencode and respective extension from the marketplace.

I have a good documentation inside the repo like described in the article Specification-First Agentic Development: A Methodology for Structured, Traceable AI-Assisted Development. So the default free OpenCode model Big Pickle performed planning, reviewing and coding stage well.
But then I realized that it was working without taking into the account system instruction and rules which I had for Antigravity.
So I've performed calls of Antigravity assurance workflows (like here and here) right from the OpenCode chat and it performed them perfectly.
As I have a lot of workflows for linting, security check of diff and the whole repo, and especially external self-made security gateway I was sure that the quality of code produced by the OpenCode was good enough and aligned with my codebase.
The only thing I can mention is a redundant file was left after some iterations of testing. But it can be fixed by a good review right after MR creation.
So seems the OpenCode is a good fallback for cases when Google servers are experiencing problems. Also it can by used to save tokens for some kind of tasks.
aiMost of us have seen a coding agent fail to complete a task we know it can do. We just don't...
googlecloudWhen building Generative AI applications, developers often encounter a massive bottleneck: sequential...
discussI’ve been thinking about sharing some electronic circuit posts on Dev.to — small circuits, DIY...
agentsWhat nobody tells you about exporting your multi-agent prototype to a local workspace. Every...
agenticarchitectAutonomous agents are genuinely good at answering messy business questions. Give one an LLM and a set...
aiPR volume went up, ticket quality didn't, and the gap got filled with LLMs on both sides of the review: bots reviewing, bots replying, bots occasionally arguing with bots about priorities that only existed in a teammate's head. Our CEO named the actual problem, and it's bigger than code review.
Workflows from the Neura Market marketplace related to this Stable Diffusion resource