Autonomous development is now central
Open ACE can run issue-driven workflows with planning, execution, review, final code changes, batch issue navigation, fork flows, and auto-merge controls.
Project
Project momentum without leaving the docs site.
Open ACE is moving from a browser AI workspace into a self-hosted 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 current codebase shows a clear product shape: issue-driven autonomous development, inspectable execution timelines, broader remote-agent coverage, and governance features that stay close to runtime behavior.
Timeline UX makes agent work inspectable
Timeline updates added compact milestone cards, summaries, full-text views, status semantics, deep links, approvals, and clearer failure or pause behavior.
Remote execution is broader and safer
ZCode support, app-server mode, token-based remote agent identity, code-server proxying, and CLI adapter hardening broaden the execution layer beyond the original tool set.
Governance is closer to runtime
Quota enforcement, run provenance, API key proxying, audit surfaces, and cost visibility now connect more directly to how sessions and workflows are executed.
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
39
Public adoption signal pulled from repository metadata when available.
Open issues
73
Current backlog volume for public product and engineering work.
Good first issues
1
Visible starter work for new external contributors.
What this project surface shows
These pages are meant to show how Open ACE has evolved beyond a docs shell: into a product with autonomous workflows, remote execution, and governance features that can all be inspected from one public surface.
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, approvals, 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
- Browser terminal, code-server access, and ZCode app-server mode for longer-lived work
Governance story
- API Key Proxy keeps real model credentials on the server
- Quota, audit, anomaly, and compliance views stay tied to user and session activity
- SSO, multi-tenant controls, and org-sync integrations support team rollout
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.