Your Agentic Software Development Team
A secure, locally hosted agent orchestrator. Work asynchronously with autonomous AI agents while you focus on product, architecture, and giving guidance.
$ git clone https://github.com/getlazy/lazy.gitWhat makes lazy different?
Stop micromanaging your coding assistants. Let agents do the work while you focus on what matters.
Autonomous Agents
Agents work in isolation, concurrently and asynchronously. Extended autonomous horizon — hours, not minutes.
Git-Native Workflows
Task lifecycle management through git. Create, review, accept or reject tasks with full branch isolation.
Captured Conversations
Every prompt, review, and decision is searchable. Both you and your agents can reference past context.
Secure by Default
Agents run in isolated Docker containers. File permission controls prevent unwanted modifications.
Asynchronous Reviews
Give feedback on your own time. No more watching code fly by — review after the agent completes its turn.
Full Situational Awareness
Agents can search across all past tasks and prompts to understand prior decisions and context.
Simple, powerful CLI
Everything you need to manage your agentic development workflow from the terminal.
1# Initialize lazy in your git repository2cd your-project/3lazy init45# Launch the interactive builder6lazy builder78# Or create tasks directly9lazy create --code add-auth \10 --goal "Add user authentication" \11 --prompt "Use JWT tokens, bcrypt for passwords"1213# Start the task14lazy start <task-id>Core Concepts
Understanding the building blocks of lazy's development workflow.
The Builder
Your interactive team lead. Chat with the builder to ideate, plan work, create tasks, and review agent output. It never touches code directly — it delegates to agents.
Tasks
A unit of work with a goal and prompt. Tasks have lifecycle states: backlog, working, blocked, complete. Each runs in its own git worktree and branch.
Turns
A single message in the conversation. Every turn records content, token usage, git SHAs before/after, and model used. Turns are the primary record of why code changed.
Reviews
Human feedback on a task. Reviews capture verdict (approve, reject, request_changes), rationale, and timestamp. A permanent record for future reference.
Ready to get lazy?
Join the alpha and start building software the lazy way. Contributions, feedback, and bug reports are welcome.
Report Bugs
Found an issue? Open a GitHub issue
Request Features
Submit Prompt Requests for enhancements
Test Alpha
Email testing@getlazy.dev to join