Skip to main content

lazycode

Your backlog, done by morning. A coding agent that plans with a realtime model and executes on provider batch APIs (50% off, 24h SLA), structured like a database query engine: logical plan → optimizer → physical plan → staged wave execution.

Not a pair programmer — the night shift. Point it at backlog burn-down (test coverage, migrations, lint eradication, mass refactors), close your laptop, review branches in the morning.

Status: pre-alpha, milestone M0 complete. Full design: docs/DESIGN.md · Landing page: rajagurunath.github.io/lazycode.

Quickstart

git clone <this repo> && cd lazycode
uv sync

cd /path/to/your-repo   # any git repo with at least one commit
export ANTHROPIC_API_KEY=sk-ant-...

uv run lazycode run "add type hints to package X" --yes
# ┌─ Plan (logical) ────────────────────────────────────┐
# │ ...                                                   │
# └────────────────────────────────────────────────────┘
# ... waves run, a branch + report.md land in .lazycode/ ...

uv run lazycode status <job-id>     # per-node detail
uv run lazycode explain <job-id>    # logical + physical plan trees
uv run lazycode review <job-id>     # branches, verification, assumption ledger
uv run lazycode resume <job-id>     # after a crash / kill -9 / restart

--verify overrides the [verify].command from lazycode.toml; --model/--max-waves override defaults; no daemon is required (run/resume host the orchestrator in-process — see docs/DESIGN.md §2 for the daemon-mode alternative). Repo-local config lives in lazycode.toml (checked in), provider keys live in ~/.config/lazycode/config.toml (never checked in) — see Appendix B2.

Want to try it without an API key first? Point lazycode.toml at the mock provider seam ([defaults] provider = "mock", [providers.mock] fixture = "...") — the same mechanism tests/e2e/ and bench/ use for deterministic, zero-network runs.

M0 status

What works today, end to end, verified by the test suite:

  • lazycode run "<goal>" --yes — realtime plan → CLI approval → wave loop → git branch + report.md/report.json, all via the Anthropic batch + realtime adapters (or the mock seam for testing).
  • lazycode status / explain / review — read-only, work whether or not a job/daemon is live.
  • lazycode resume <job-id> — reopens the store and drives an interrupted job to completion; crash-safe: kill -9 mid-wave then resume does not double-submit the batch or double-apply the diff (event-sourced replay + the applied-diff ledger, DESIGN.md §7.1/§9). Covered by tests/e2e/test_crash_resume.py.
  • lazycode daemon — foreground-only single-writer daemon; run hands jobs to it over HTTP when it's up (--background is not implemented in M0 — run it under launchd/systemd/tmux instead).
  • Multi-file fan-out — independent Generate nodes land in one wave (tests/e2e/test_happy_path.py); optimizer is R1/R2 only (local pushdown + context pruning), no model tiering or speculation yet.
  • Benchmark harness (bench/) — three fixture-repo tasks, lazycode-vs-Claude-Code-CLI token comparison, <50% verdict (Appendix B7).

What doesn't work yet (by design — later milestones, Appendix B11):

  • No repair loop — a failed contract or verify run goes straight to NEEDS_HUMAN, not a retry (M1).
  • No cost estimate in the pre-flight prompt (plan tree + y/N only), no explain analyze, no cost/slider-driven optimizer beyond R1/R2 (M2).
  • No hedging or deadline-aware fallback to realtime (M2), no speculation/vectorization (M4).
  • No web UI, no desktop/Slack notifications (log line only), no watch TUI (M3).
  • Single provider (Anthropic) + realtime planner only — no OpenAI/Gemini/pseudo-batch adapters yet (M4).
  • --background daemon mode, merge/cancel commands, and GitHub Actions best-effort runner are all unimplemented (M1/M2).
  • Memo-key sharing across duplicate nodes (by design): two distinct nodes that render byte-identical prompts share one R10 memo entry — the second is served from cache and, its identical diff being already in the applied-diff ledger, is marked DONE without a second apply. Since the rendered prompt embeds the node's spec, harvested files, and contract globs, identical prompts always mean identical requested work at M0's temperature=0.0/sample_idx=0; deliberate N-best sampling of one prompt gets distinct sample_idx values in M4 (DESIGN.md §5.2 R7/R10).

Metadata

Release files for lazycode-agent 0.0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for lazycode-agent 0.0.1
File Size Uploaded Provenance Actions
lazycode_agent-0.0.1.tar.gz 220.1 kB Without provenance Details for lazycode_agent-0.0.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for lazycode-agent 0.0.1
File Interpreter ABI Platform Actions
lazycode_agent-0.0.1-py3-none-any.whl Python 3 none any Details for lazycode_agent-0.0.1-py3-none-any.whl

Total release size: 347.7 kB

Release files / lazycode_agent-0.0.1.tar.gz

Download URL lazycode_agent-0.0.1.tar.gz
Size 220.1 kB
Tags Source
SHA-256 checksum
How to use checksums
2cdb9420357bfde4a9b4e65b7354a1f49a150b54c89d01e0af22170bc04b0400
BLAKE2b-256 checksum
How to use checksums
e33343ff5aa4b31c8cddd2176ce3e520fe332de914a5fc15dfe3acd09853f60a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.5.26

Release files / lazycode_agent-0.0.1-py3-none-any.whl

Download URL lazycode_agent-0.0.1-py3-none-any.whl
Size 127.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b71bec00cb08c4a1be50aebca2d9508cf31f1cfc8778dc1693d2015a9efbb20a
BLAKE2b-256 checksum
How to use checksums
8414dc752be0c0e3553f2e331995a2883492d8028e39e7d89034538d95e0575c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.5.26

Security for lazycode-agent 0.0.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.0.1 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page