My experience using /goal

I had a major refactoring task to refactor my app from Ruby to Go that I was working on for the last few months, a little bit everyday. I had AI create the plan, and start executing it. The plan was to get Ruby test coverage to 100%, then make the Golang functionality with corresponding 100% test coverage. I started an uncountable number of prompts, overnight agent sessions, etc. to work on the refactoring, but I felt it wasn't going fast enough and required a lot of effort. Codex tells me the GoLang part of the app is 110,000 lines of code. I had heard about /goal before and Andrei Karpathy's autoresearch but I hadn't tried a tool like this before.

One day I decided, enough already, and I tried /goal. And what happened shocked me. Codex worked for 1 week on the refactor! While it was running I found bugs in my harness for multi-day tasks and my server ran out of space. I had underestimated how much of the task was left and how much of it many attempts had accomplished. But now that /goal was working on it for days at a time I didn't have to worry about it, I would just check a few times a day what 50 files had changed. Now I can focus on different tasks and have agents work on multi-day tasks without having to manage them myself. Give /goal a try it in Codex or Codex and see for yourself!

Update: there are some small bugs with the GoLang implementation now that I'm trying it, but it's running! It's not perfect, but it got me much closer, and I can't believe I didn't use /goal earlier!