Inspiration
Working every day with coding agents made both the things they do well really exciting and the things they don’t do well really frustrating. I found myself using tools built for software engineers, and while I am a builder, they don’t resonate with me. On the other end of the spectrum, tools like lovable cloud code on the web and Claude design felt underpowered and underwhelming for the real job of creating working products. He said about to create something that felt both up for the challenge and also beautiful and enjoyable to work in. The Inby Browse is born out of all of these inspirations and the iteration I shipped with codex during the hackathon is a huge step to making rapid iteration and design smooth and enjoyable.
What it does
Inby brings a laundry list of usability and product improvements to the traditional terminal. Along with a terminal Inby has a agent native web browser, a powerful docs and code viewer that lets other humans and agents access your specs and plans remotely, a beautiful native diagram system and renderer, A lightning fast web server that lets your agents throw HTML CSS and JavaScript at the browser directly, And finally, a set of settings and controls that make your agents like Claude code Codex and open code easy to configure visually, whether it skills MCP servers or plugins. The browser changes I implemented with Codex and GPT 5.6 bring coding agents in the terminal powerful first class tools to create mockups, debug visual and technical issues and share ideas with humans and other agents faster and with more clarity and less tokens than ever before.
How we built it
I built the new Inby browser features with Codex CLI running in Inby. I had codex take the first pass at fleshing out the design and product direction and carefully guided it as it visualized the changes in the very same browser window it implemented it into. This type of meta design always produces great results making it fun to use coding agents in Inby to build Inby.
Challenges we ran into
Agents by default want to create over designed, over engineered solutions that make humans cringe. The Inby workflow and careful prompting to get the agent into a more minimal iterative loop help.
Accomplishments that we're proud of
Building something that I would pick out of all of the tools available to work in every day makes me feel really accomplished. Inbys ability to power up these models and harnesses from frontier labs in simple but elegant ways brings me joy.
What we learned
I learned that there’s no settled right or wrong way to build with agents, and that many tools have prematurely coalesced on similar experience and UI patterns. I also through this process became intimately familiar with what tools coding agents like Codex are missing today, When given the ability to create reusable extensions for themselves and future versions of themselves pre-running web servers to quickly show users mockups and a more advanced diagramming DSL agents tended to use these things more to make working with them easier.
What's next for Inby
I have a waiting list of 50 people and I intend to get as much feedback as possible from real users and grow Inby to be the best way to cowork on beautiful software with agents
Log in or sign up for Devpost to join the conversation.