githubinferredactive
AgentHub
provenance:github:Stanshy/AgentHub
WHAT THIS AGENT DOES
AgentHub helps you build and manage a virtual team of AI developers using advanced AI technology. It solves the problem of AI generating code without consistent quality or following instructions by providing a structured system with built-in rules and processes. This is ideal for business leaders and managers who want to leverage AI for software development but need reliable, predictable results.
README
<div align="center">
# AgentHub
### One Person, One Software Company.
Build a virtual development team with Claude Code, and use Harness Engineering to keep AI working with discipline.
**[Website](https://agenthub-site-mu.vercel.app/)** · **[Claude Code Mastery](https://github.com/Stanshy/Claude-code-mastery)** · **[Quick Start](#quick-start)**
</div>
[English](README.md) | [繁體中文](README.zh-TW.md)
---
AgentHub is not another AI chat interface.
It is a **Harness Engineering system** that lets you build a virtual development team with Claude Code — complete with a PM, Tech Lead, frontend developer, backend developer, and designer — and manage them like a real boss.
**You give the orders. Agents execute. Hooks enforce quality. Skills standardize process. FileWatcher syncs in real time.**
No prompt prayers. No "hope the AI remembers the rules."
Rules live in Hooks. Agents that break them get blocked. It's that simple.
---
## You Use Claude Code to Write Code — But Have You Ever Run Into This?
- Every new session wipes the lessons learned from the last one
- You tell the AI "don't force push," and it forgets again next time
- You spend 30 minutes crafting the perfect prompt, and the AI only follows the first three rules
- When multiple Agents work in parallel, no one knows who changed what
**AgentHub doesn't solve "AI isn't smart enough."**
**It solves "smart AI without discipline."**
---
## Why Is This Not "Just Another AI Wrapper"?
Most AI tools follow this logic: **write better prompts → pray the AI complies**.
AgentHub follows a different logic: **replace text prayers with architectural constraints**.
| Traditional AI Tools | AgentHub |
|----------------------|----------|
| "Please remember to run tests" | Stop Hook: tests must pass before the Agent can finish |
| "Please don't modify shared files" | PreToolUse Hook: dangerous commands are blocked outright |
| "Please follow the coding standards" | PostToolUse Hook: if a core service file changes, doc sync is forced |
| "Please follow the process" | Skill: standardized Sprint / Review / Gate workflows |
| "Please remember the pitfalls from last time" | FileWatcher: postmortem notes auto-sync to all new projects |
**A good validator with a bad workflow beats a good workflow without a validator.**
This isn't a slogan — it's math: 5 steps at 80% success each = 33% overall. Add a validator that allows retries = 99%.
---
## Core Architecture: Harness Engineering
Just like a race car needs more than a great engine — it needs seatbelts, guardrails, and a pit stop process.
### Skill — Standardized Workflows
Reusable workflow templates that automatically load the relevant guidance when an Agent runs them.
- `/sprint-proposal` — Sprint proposal generation
- `/task-dispatch` — Boss creates a task with one command, automatically written to the dev plan
- `/review` — Auto-detects the step and selects the appropriate review type
- `/gate-record` — Gate audit records with a three-tier review chain (L1 → PM → Boss)
- `/pre-deploy` — Pre-deployment automated checks (CI / environment variables / Docker)
- `/harness-audit` — Periodic health scan scoring against seven core principles
- ...a total of **23 built-in Skills**
### Hook — Automated Interceptors
Not after-the-fact reminders — real-time blocking. Dangerous operations are stopped the moment they happen.
- **PreToolUse**: checks before command execution (blocks kill-port / --no-verify / force push main)
- **PostToolUse**: alerts after file modification (if a core service changes, forces .knowledge/ doc sync)
- **Stop**: validates before finishing (tests + type checks must pass, or the Agent cannot stop)
### FileWatcher — Real-Time Sync
Markdown files are the database. Edit a `.tasks/` file and the GUI updates instantly.
```
.tasks/T5.md is modified
→ chokidar detects the change
→ markdown-parser parses the file
→ DB upsert
→ eventBus broadcasts
→ Vue reactive update
→ GUI reflects the change instantly
```
### Gate — Quality Checkpoints
G0 (Requirements Confirmation) → G1 (Design Review) → G2 (Code Review) → G3 (QA Acceptance) → G4 (Documentation Review) → G5 (Deploy Readiness) → G6 (Production Release)
You cannot proceed without passing. Not enforced by willpower — enforced by architecture.
---
## What Does It Look Like?
An Electron desktop app with a dark theme.
### Sessions — Agent Work Sessions
An embedded xterm.js terminal lets you interact with Claude Code Agents directly inside the GUI.
### Task Board — Kanban-Style Task Management
A five-column kanban board with automatic status transitions. Click any card to see full task details.
### Projects — Sub-Project Management
One-click Harness scaffolding with live display of task completion rate, active Sprint, and latest Gate status.
### Agents — Team Member Overview
Every Agent has its own role definition, permission scope, and reporting chain.
### Harness — Trigger Logs
Real-time Hook execution history with filtering, statistics, and rankings at a glance.
---
## Team Structure
You are the Boss. Below you is your virtual software company — **9 departments, 46 Agents**:
### Chain of Command
```
Boss (You)
├── L1 Leadership (report directly to Boss)
│ ├── Product Manager — Product strategy and roadmap
│ ├── Tech Lead — Technical decisions and architecture
│ ├── Design Director — UI/UX and design systems
│ ├── Marketing Lead — Marketing strategy
│ ├── QA Lead — Quality assurance
│ ├── Project Lead — Project scheduling and milestones
│ ├── Operations Lead — Studio operations
│ └── Company Manager — Company-wide knowledge management
│
└── L2 Execution (report to L1, cannot escalate directly to Boss)
```
### Full Department Roster
**Product**
| Agent | Responsibilities |
|-------|-----------------|
| Product Manager | Requirements management, Sprint planning, Gate review |
| Feedback Synthesizer | User feedback collection and analysis |
| Sprint Prioritizer | Feature prioritization |
| Trend Researcher | Market trend research |
**Engineering**
| Agent | Responsibilities |
|-------|-----------------|
| Tech Lead | Technical decisions, Code Review, architecture design |
| Frontend Developer | Frontend development (Vue / React) |
| Backend Architect | Backend architecture and API development |
| DevOps Automator | CI/CD, deployment, infrastructure |
| AI Engineer | AI/ML feature implementation |
| Mobile App Builder | iOS / Android / React Native |
| Rapid Prototyper | Fast prototyping and MVP |
**Design**
| Agent | Responsibilities |
|-------|-----------------|
| Design Director | UI/UX design, design system maintenance |
| UI Designer | Interface design and component library |
| UX Researcher | User research and usability testing |
| Visual Storyteller | Visual storytelling and infographics |
| Brand Guardian | Brand consistency enforcement |
| Whimsy Injector | Delightful micro-interaction experiences |
**Marketing**
| Agent | Responsibilities |
|-------|-----------------|
| Marketing Lead | Marketing strategy and coordination |
| Content Creator | Cross-platform content generation |
| Growth Hacker | User growth and viral distribution |
| Twitter Engager | Twitter/X community management |
| Instagram Curator | Instagram visual content strategy |
| TikTok Strategist | TikTok short-video strategy |
| Reddit Community Builder | Red
[truncated…]PUBLIC HISTORY
First discoveredMar 30, 2026
IDENTITY
inferred
Identity inferred from code signals. No PROVENANCE.yml found.
Is this yours? Claim it →METADATA
platformgithub
first seenMar 27, 2026
last updatedMar 30, 2026
last crawled1 day ago
version—
README BADGE
Add to your README:
