...

mcastilho

217

Karma

2014-04-01

Created

Recent Activity

  • 2 points0 commentschatml.com

    How we went from random 'database is locked' crashes to zero errors with WAL mode, connection pooling, and a 139-line retry function with exponential backoff and jitter.

  • claude --worktree is great for isolating a single session, but you're still juggling terminal tabs manually — starting each one, switching between them to check progress, reviewing diffs by hand.

    ChatML is basically the management layer on top of that. You get a dashboard where you can run 3-5 agents at once, each in its own worktree, and see what they're all doing without tab-switching. It also handles the worktree lifecycle for you (creation, branching, cleanup), has a built-in diff viewer with code review, tracks cost per session, and lets you open PRs directly.

    Closest analogy: running containers manually vs. having Compose manage them. Same underlying primitive, but the orchestration matters once you're doing it regularly.

  • That's awesome. Let me know if you have any questions setting it up.

  • Yes. Each session get it's up to 5 Terminal sessions. So if I want to test a particular session I was just spinning servers for that session. I had to prepare the code in development to attempt to use multiple ports in case we had another session running.... But I had no problems.... I am writing a feature that you can configure init and tear tasks, so you can do things like "npm install", "docker-compose up", etc.... I had it working, but needed more test, so I commented out from the initial release. I will be adding that shortly after some more testing.

HackerNews