Autonomous development is now central
Open ACE can run issue-driven workflows with planning, execution, review, final code changes, batch issue navigation, and auto-merge controls.
Project
Project momentum without leaving the docs site.
Open ACE is moving quickly from a self-hosted AI coding workspace into an autonomous engineering control plane. This section turns repository state, roadmap planning, release history, and contribution entry points into a single public surface.
Recent product direction
The last three weeks of merged PRs show a clear product shape: autonomous development workflows, observable execution timelines, safer remote agents, and more reliable install/upgrade paths.
Timeline UX makes agent work inspectable
Recent timeline updates added compact milestone cards, summaries, full-text views, status semantics, deep links, and clearer failure/pause behavior.
Remote execution is expanding
ZCode support, app-server mode, token-based remote agent identity, and CLI adapter hardening broaden the execution layer beyond the original tool set.
Live repository signals
The site reads repository metadata at build time when GitHub API access is available, then falls back to committed project files so Pages builds remain deterministic.
Stars
4
Public adoption signal pulled from repository metadata when available.
Open issues
94
Current backlog volume for public product and engineering work.
Good first issues
3
Visible starter work for new external contributors.
What this phase adds
Phase 1 established the product homepage and bilingual docs shell. This phase adds project transparency pages so visitors can inspect momentum, release maturity, and contribution paths from the same domain.
Autonomous workflow story
- Issue-driven runs with plan, implementation, review, and final summary stages
- Batch issue support for operating multiple GitHub issues from one workflow
- Timeline cards that expose progress, failures, retries, and code changes
Remote execution story
- Remote Agent registration and token management for controlled machines
- CLI adapters for Claude Code, Qwen Code, Codex, OpenClaw, and ZCode
- Docker, package, macOS, and source install paths receiving active fixes
Project transparency story
- Roadmap, releases, community links, and GitHub signals stay visible from docs
- Build-time counters show issues, starter work, and repository metadata
- Docs are split from the application repo so product docs can evolve cleanly
Where to go next
Use these pages as the default project surface for roadmap, release, and contribution status.
RoadmapRead current priorities, next-stage work, and success signals.ReleasesInspect shipped capabilities, latest release metadata, and changelog structure.CommunityFind contribution links, public issue paths, and security reporting entry points.GitHub issuesJump into the live backlog when you need the canonical queue.