I recently came across https://claudecode.run/ (not affiliated). There are currently several similar products that help that multi-instance Claude Code layout

How quickly? There is no limit to that. If I can do my day of work in few hours I would be glad to take the afternoon off or to go twice as fast (importunately that's more the second!)

With git worktrees you can you have your agents working on literally different folders so they don't step up on each other.

that solves the problem of "stomping on things" in the short term but it might not be trivial to merge these later. depending on what kind of tasks you're giving them and the style in which they do them it could be anything from "no problems" to "lots of headaches" -- the same is true for human developers.

(I've definitely seen 20 developer teams that were spinning their wheels because they were stomping on each other despite using version control as well as teams that had code rot because they had a "no refactoring/don't touch a file you can possible avoid touching" policy)

I agree. However as you said, you can consider code agents like human contributors. My feedback is that an army of Claude Code instances with a strict CLAUDE.md file is more rigorous than a human team.

Fixed ! thank you

Hello, Manifest dev here, most backend-as-a-services rely on an UI and it's harder for AIs. In comparison, Manifest high-level DSL is really understandable by gen AIs. It's also very easy to validate in comparison to bootstrap frameworks that come with a lot of files.

But you are right we should explain it somewhere !

Thanks for the reply! It makes sense.

correct :)

Hello ! Manifest dev here, they are on the way ! There is a DB sync at the moment that does the job but we are going to implement the migrations soon :)

Nice. Manifest looks really cool :)

It will be an express based REST API that connects to an external Database.

The API will have to expose endpoints and do CRUD operations for the most part.

(dev here) Backend-as-a-service products are very popular right now because they remove or simplify a lot of the backend complexity. It comes super handy for some projects.

Yes, the DB is SQLite. We chose it among others as it is file based and thus you get get up and running in seconds.

Authentication and authorization are key features, I agree. They were not integrated in the POC but they will come very soon. There actually is auth for the admin panel, I just need to standardize it for other entities.

I got it for the CMS use case, Manifest's aim is not to be a competitor of large frameworks that gives you the control of everything. We rather think that it will fit for another typology of projects. You can use it as a headless CMS, but there already is products like Strapi or Directus that get the job done. I am thinking more about projects with more "app" logic, but the next step is adding custom logic to it.

Migrations are a tricky point I agree. In your system, do you keep your original model files as they were at the beginning or do you change them too ?