SplitMind

How was your experience building with Codex?

Codex was central to building SplitMind. I used it not only to write code, but to reason about the product direction, improve the CLI workflow, debug Windows path and test runner issues, refine the frontend dashboard, and shape the hackathon submission. The most useful part was using Codex as an engineering partner: it helped connect the CLI, Git worktree orchestration, deterministic pytest evaluation, and the telemetry UI into one coherent product. The project itself is also inspired by how Codex changes software development: moving from asking one model for one answer to orchestrating multiple validated agent strategies.

Describe your experience using Loops House as the hackathon platform. What worked well, what challenges (if any) did you face, and what improvements would you like to see?

Loops House gave a clear structure for turning the project into a hackathon submission. The project steps, required fields, and submission flow made it easy to understand what judges need: screenshots, repo, live demo, and video. The main challenge was time pressure and deciding how to present a CLI-first tool in a platform that also asks for a live app URL. A useful improvement would be clearer guidance for projects that are developer tools, CLIs, or local agent workflows rather than traditional hosted web apps.

Tell us about your overall experience at Codex Community Hackathon Pune.

The hackathon was intense and very aligned with the future of software development. Building SplitMind pushed me to think beyond a normal app and focus on agent orchestration, verification, worktrees, and developer trust. I learned that the real value is not just generating code, but creating workflows where multiple AI-generated solutions can be tested, compared, and merged safely.

What could Codex Community improve to create a better experience for participants?

It would help to provide more examples of strong submissions for CLI tools, Codex Skills, and agentic developer workflows, not only hosted web apps. More explicit judging guidance around local-first tools would also help participants present their projects better. A template for demo videos and architecture diagrams would make the final submission process smoother under hackathon time pressure.