Forgeo is a software factory for your coding-agent. You're already working with an AI coding agent, prompting it task by task or giving it a goal. Forgeo organizes your work in a structured way with a backlog, and it decides what to work on next, runs your agent on it, and commits the result. Progress, pending decisions, and history are tracked in plain files you can inspect at any time, plus a web dashboard. Forgeo only interrupts you when a decision is genuinely yours to make, everything else happens autonomously.
All you need is basic comfort with a terminal, a git repository, and any coding agent CLI.
Quickstart
The full walkthrough is in Getting started.
# 1. Install
curl -fsSL https://forgeo.org/install.sh | bash
or
pipx install forgeo-cli
# 2. Create your Forgeo (guided wizard, run from your project root)
forgeo init
# 3. Start Forgeo
forgeo start # run forever: every interval_minutes, implement the oldest OPEN task
forgeo init writes forgeo.yaml and a .forgeo/ folder for the backlog
and logs. Fill the backlog with plain JSON tasks (see
Backlog format) or add them from the web console while
it runs, Forgeo does the rest. Open the dashboard with forgeo web (default http://0.0.0.0:8790):
One-off commands: forgeo once (single cycle), forgeo status (summary),
forgeo stop, forgeo restart, every command is in the
CLI reference.
You can run several factories at once, one per repository, each config is
fully independent (own backlog, logs, locks). Register each forgeo.yaml
in the instance registry with forgeo instance add NAME --config PATH,
manage any of them by name with forgeo start/status/stop --name NAME,
list them all with forgeo list, and get one aggregate overview with the
central dashboard, forgeo web.
Documentation
| Topic | Where |
|---|---|
| Install, init, first cycle | Getting started |
Every forgeo.yaml key |
Configuration |
| Task schema and statuses | Backlog format |
| How the agent is invoked (env, exit codes, timeouts) | Agent contract |
| All CLI commands | CLI reference |
| Web dashboard & HTTP API | Web console & HTTP API |
Everything is stored in plain files: the backlog, forgeo.log, and
BLOCKER.md whenever a decision is pending.
Develop
pip install -e ".[dev]"
pytest
See CONTRIBUTING.md for the development setup, quality
gates (pytest, ruff check, mypy src/forgeo), and the pull-request
process.
License
MIT — see LICENSE.
Metadata
Release files for forgeo-cli 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| forgeo_cli-0.4.0.tar.gz | 790.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| forgeo_cli-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 863.8 kB
Release files / forgeo_cli-0.4.0.tar.gz
| Download URL | forgeo_cli-0.4.0.tar.gz |
|---|---|
| Size | 790.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
41201431593b97b2dcee35de0e336502d15e311c71ebe9a04fcf26de7914a1d4
|
|
BLAKE2b-256 checksum How to use checksums |
28ded2bab112aacd10c9adbd29a34b73610bacf0d31c6218637bd2e7e119f7fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 10, 2026.
Transparency logRelease files / forgeo_cli-0.4.0-py3-none-any.whl
| Download URL | forgeo_cli-0.4.0-py3-none-any.whl |
|---|---|
| Size | 73.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e4a413eebcb6103b85a8160a94c92b31413ea6adc995979adaa3d948c2925a4d
|
|
BLAKE2b-256 checksum How to use checksums |
e1a2d8a79d3835c621c56273f5747a019f7cd12815ccfc2abf67bb936cc0483d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 10, 2026.
Transparency log