AutoMaker-Org/automaker

Automaker is a desktop and web application that orchestrates AI agents to autonomously implement software features based on descriptions you provide on a...

View on GitHub ↗Jump to charts ↓Open shareable report →

AutoMaker-Org/automaker has 3k+ stars and 550+ forks on GitHub, is written in TypeScript, and was last pushed on May 22, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 54 minutes ago
Added to GitGenius on September 21st, 2026
Created on December 7th, 2025
Open Issues & Pull Requests: 10 (+0)
GitHub issues: Enabled
Number of forks: 595
Total Stargazers: 3,229 (+0)
Total Subscribers: 28 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 20.6 hours
Mean response time: 6.1 days
90th percentile: 24.9 days
Tracked items: 297

Maintainer activity

8 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 3% of issues opened in the past year have never received a reply. Work labelled "scope: ui" is answered fastest, typically in about 5 hours, while "type: feature" waits about 3 weeks. 97% of issues opened in the past year have since been closed. Three people close 83% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 8
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 157 days
Stale 30+ days: 8
Stale 90+ days: 8

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Bug (103)
  • Enhancement (66)
  • scope: ui (21)
  • type: feature (11)
  • New Issue (9)
  • Stale (8)
  • Refactor (7)
  • scope: mobile (4)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Automaker is a desktop and web application that orchestrates AI agents to autonomously implement software features based on descriptions you provide on a Kanban board.

The tool addresses the friction of manual code writing by letting developers describe features at a high level while AI agents handle implementation details. You define tasks on a Kanban board, approve plans generated by the agents, and watch as they execute the work across your codebase. The system uses git worktree isolation to keep agent work separate, supports real-time streaming of agent activity, and coordinates multiple agents on complex tasks. The underlying engine is powered by Claude Agent SDK, though the tool supports other providers including Codex, Copilot, Cursor, Gemini, and OpenCode.

Automaker suits teams and individual developers who want to accelerate feature development by delegating implementation to AI agents rather than writing code manually. It works best for projects where you can clearly articulate requirements and accept that AI-generated code requires review before merging. The tool is particularly valuable if you already use AI-assisted development workflows and want a more structured, agent-orchestrated approach. The README emphasizes that Automaker itself was built using agentic coding techniques, demonstrating the methodology it enables.

The project shows active development with a monorepo structure spanning frontend, backend, and shared libraries. The codebase is written primarily in TypeScript and built with React, Vite, Electron, and Express, indicating a mature technical foundation. The team maintains comprehensive documentation covering architecture, deployment, testing, and environment configuration, and provides both interactive TUI and graphical interfaces for users. Development includes testing infrastructure, linting standards, and production build processes, suggesting sustained engineering discipline.