How whereevenami/ezapplication works
EzApplication turns a natural-language request into a generated multi-file project. Users can start generation through the CLI or the FastAPI endpoint; the LangGraph workflow plans the app, expands that plan into file-level tasks, then iteratively has a coding agent edit files. The API also exposes job progress and generated-file contents. The README describes the product broadly; sampled code shows the workflow and file tools, but no frontend or additional validation stage, so neither is represented.
Main entry points: graph.py LangGraph workflow · api.py HTTP API · main.py CLI runner · tools.py File tools
Components 10
User entrypoints
- CLI runner
main.py - HTTP API
api.py
Planning workflow
- LangGraph workflow
agent/graph.py - Agent prompts
agent/prompts.py - Plan and state schemas
agent/states.py
Code generation
- Coding agent
agent/graph.py - File tools
agent/tools.py
Generated project
- Generated files
Other components
- User
- Groq model
Connections 11
- User → CLI runner: enters prompt
main.py - User → HTTP API: submits request
api.py - CLI runner → LangGraph workflow: invokes workflow
main.py - HTTP API → LangGraph workflow: streams workflow
api.py - LangGraph workflow → Agent prompts: builds prompts
agent/graph.py - LangGraph workflow → Plan and state schemas: uses schemas
agent/graph.py - LangGraph workflow → Groq model: calls model
agent/graph.py - LangGraph workflow → Coding agent: dispatches tasks
agent/graph.py - Coding agent → File tools: registers and invokes
agent/graph.py - File tools → Generated files: reads and writes
agent/tools.py - HTTP API → Generated files: lists and reads
api.py