Really like your idea

[sakshamagrawal1993]

I have been vibe coding for a while and though I have no formal computer engineering degree, I really appreciate what you are building. How I see it is that it is n8n for app/CLI based harnesses, which is actually useful as the cost of running via CLI/app is much lower than via API.

Thus this can become a widely adopted n8n substitue/workflow builder. However, I would love if the team can include some of the following features, which I feel would be really helpful :

1. Gates/Approval gates - After a step in workflow, an artifact is created which is approved/edited by the human and allows the workflow to continue
2. Creation of artifacts/markdown files - As a product manager, I have built my loops by having each of my node write a markdown file which is passed as context to the other agent. This can be BRD, PRD, Ticket, Design Wireframes, Technical Specification Document, Market Research/Competitive benchmarking, clarifications required for further movement etc
3. Agent to Agent graphs/loops which exit when conditions are met (like code writer/QA) similar to langraph but for CLI terminals