Where this came from

An honest note on how Takuto started, and what that means for you.

How it started

A while ago I started to vibe code a small tool to try automating some of my Jira tickets at work. I wanted to let AI handle trivial issues headlessly, so I can focus on work requiring more attention. So I've built that thing I called Maestro that pulls Jira bug tickets automatically, spawns a Docker container per item and let an agent run there in isolation, mitigating risks for the host machine.

It worked quite well, so I started expanding it. Now I use Takuto to experiment with vibe coding on a language I chose for performance and modernity, but that I do not master at all. This means although I'm making sure things work as well as possible, I cannot devote all my time to it nor can I give it as much attention as I do in my job.

Found a rough edge, or have an idea?

Share feedback