Tempest AI

I never really shared why I'm building @usetempest. So here it is. I'm Prharsha, and over the past few years I've built products, shipped them, spent thousands of hours working with AI coding agents, and watched those tools evolve at an incredible pace. One thing has become clear to me. The future isn't a single AI replacing developers. It's agentic engineering team with a human orchestrator. AI agents are exceptional at executing well-defined tasks. They can research, write code, review changes, and test ideas in parallel. But they still lack the judgment to decide what should be built, when priorities change, or whether the solution actually solves the problem. That's where humans stay in the loop. I believe the best engineering teams of the future won't be one developer and one AI. They'll be one developer orchestrating a team of specialized agents. But today's experience isn't there yet. As you add more agents, token costs explode. Context gets duplicated. Every agent spends time rediscovering the same repository instead of building. I'm building Tempest to change that. Not just by making agentic engineering more efficient, but by making it safe, predictable, and easy to use. Every feature we build is centered around one principle: AI agents should work with you, not against you. Humans should stay in control. Agents should handle execution. The collaboration should feel transparent, reliable, and intentional....not like handing your codebase to a black box. I believe that's how software will be built over the next decade. And that's the future I'm trying to build. #buildinpublic