Yeachan-Heo

Build a feature with one /autopilot command in Claude Code Driving Claude Code through plan, code and QA by hand takes a lot of prompts. oh-my-claudecode (OMC) is a plugin that adds multi-agent orchestration on top: describe a feature once and let staged agents work through it. This is how the README sets it up, and what to check before you trust the result. Install it as a Claude Code plugin These are Claude Code slash commands. Enter them one at a time, because pasting both lines at once fails, as the README warns: /plugin marketplace add https://github.com/Yeachan-Heo/oh-my-claudecode Then: /plugin install oh-my-claudecode Run the setup command inside the session: /omc-setup If you prefer the npm CLI path instead of the marketplace flow, the README gives: npm i -g oh-my-claude-sisyphus@latest npm may print a prebuild-install deprecation warning. The README says it comes from an upstream dependency and has no repo-side fix yet. Build a feature with /autopilot Give it a feature in your own words: /autopilot "build a REST API for managing tasks" Autopilot runs in stages: plan, build, check. If you want a fixed sequence, the README describes a plan-build-qa profile configured under autopilot.workflows in .claude/omc.jsonc. Whatever profile you pick, review the diff and run the tests before merging. An agent that checks its own work is still an agent checking its own work. A safer first run is to ask it to stop after the plan: Install Yeachan-Heo/oh-my-claudecode in Claude Code, run /omc-setup, then /autopilot to build <feature> in this repo. Stop after the plan so I can approve it before execution. Clarify the idea first with /deep-interview Agents that start from a vague prompt bake in assumptions you never agreed to. OMC includes a Socratic interview that asks questions and measures clarity across weighted dimensions: /deep-interview "I want to build a task management app" Answer the questions, then hand the clarified spec to /autopilot or /team. Run several agents in parallel The CLI can spawn tmux worker panes, including workers from other providers: omc team 2:codex "review auth module for security issues" omc team 1:claude "implement the payment flow" omc team status omc team shutdown Inside Claude Code the native version is /team 3:executor "fix all TypeScript errors". Native teams need CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS set to 1 in ~/.claude/settings.json. Without it, OMC falls back to non-team execution. Is it too much? The README itself says some people find OMC overkill and points to a lighter project by the same author, gajae-code. That is a useful signal. If you only need one agent on one small task, plain Claude Code is fine. OMC pays off when you repeatedly run the same plan, build and review loop, or want parallel reviewers. What we did not verify - We followed the README and have not run this end to end for this post. - You need Claude Code installed and a plan that covers the extra usage multi-agent runs consume. - Check the repo for newer instructions before you rely on these steps. The step-by-step version is on our use-case page: build a feature end to end with one /autopilot command. The repo overview is here. Want the setup commands for 50 AI repos people actually ship with? Get the free AI Repos That Actually Ship pack: dedupedai.com

I tried to rename my coding-agent plugin. Then I found another tool with almost the same name > After I wrote this, I settled on the name Dude Toldya. The repository is now dude-toldya and the command is duto. "Did you actually run the tests?" I've asked Claude Code and Codex versions of that question more than once. I built a plugin to save my corrections and show them again with later requests. I called it Off the Wall. The problem: the name doesn't tell you what it does. The README had a parrot, too. I didn't really want the tool to just repeat me like a parrot. I wanted it to bring my earlier correction back when the agent needed the context. So I started looking for a new name and a different character. The name part didn't go quite as planned. FFS Again? One idea was FFS Again. It captures the feeling of watching your coding agent make the same mistake again. But if you saw it in a plugin list, would you know it had anything to do with Claude Code or Codex? Probably not without a description. Then I considered dude-toldya. It sounded closer to what I was trying to say: dude, I already told you. Then I searched for it. There was already a toldya toldya is an existing tool that looks for repeated corrections in Claude Code history and writes selected ones into a rules file with the user's approval. My plugin takes a different approach: it keeps the original wording and shows selected quotes again rather than turning them into rules. But if I called it dude-toldya, I could see someone assuming it was another version of that tool. I haven't settled on the name. The GitHub README calls it a working title, and the install commands still use off-the-wall. I haven't completed a package-name or trademark check either. I made a sticky note, but it didn't look like AI I also tried changing the character. The first AI-generated idea was a crumpled sticky note. That made sense for storing old corrections, but it didn't really show the situation I had in mind: a coding agent doing something odd and me having to correct it again. I looked at Gajae Code's GitHub page. Its pixel character stands out in the README. I used the pixel-art and dark-background feel as a reference, not its character or logo. Then I thought of the Korean "Please be quiet!" meme. The next AI-generated draft was a confused little terminal robot getting a gentle bonk on the head. !AI-generated pixel-art terminal robot getting a gentle bonk That one felt closer to the frustration behind the project. Neither the name nor the mascot is final. A new name won't fix this part The plugin still has a problem: the selected quote isn't always relevant. I ran otw explain on a haiku request, and its preview selected unrelated coding corrections to attach. This is the tool's output from a fake repository with corrections made up for the demo. !A preview selects unrelated coding corrections for a haiku request, using a fake repository and made-up corrections Showing a correction again also doesn't mean the agent will follow it. I haven't measured whether real users need fewer repeated corrections. For now, the GitHub README has the new mascot. The name can wait a bit longer. I'd like one that doesn't get confused with another tool and still makes the problem recognizable. Originally published on my blog.

oh-my-claudecode: Multi-agent orchestration for Claude Code. Zero learning curve (40k stars) What it does All text below is quoted directly from the project README. >Teams-first Multi-agent orchestration for Claude Code Why oh-my-claudecode?: - Zero configuration required - Works out of the box with intelligent defaults - Team-first orchestration - Team is the canonical multi-agent surface - Natural language interface - No commands to memorize, just describe what you want - Automatic parallelization - Complex tasks distributed across specialized agents - Persistent execution - Won't give up until the job is verified complete - Cost optimization - Smart model routing saves 30-50% on tokens - Learn from experience - Automatically extracts and reuses problem-solving patterns - Real-time visibility - HUD statusline shows what's happening under the hood >/plugin marketplace add https://github.com/Yeachan-Heo/oh-my-claudecode Repository Yeachan-Heo/oh-my-claudecode Repository stats |Metric|Value| |:-|:-| |Stars|40,379| |Forks|3.6k| |Last release|v5.7.19 (2026-10-27)| |Languages|TypeScript 59.6%, JavaScript 39.4%, Other 1%| |Contributors|169| |AI contributor accounts (Claude / Codex / Cursor / Copilot)|@claude (1318 commits), @cursoragent (8 commits), @codex (6 commits)| |AI co-authored commits|Claude: 1351, Codex: 143, Cursor: 8| Main contributor |Field|Value| |:-|:-| |Name|Bellman| |GitHub|@Yeachan-Heo| |Commits to this repo|2,421 (top contributor)| |Company / Location|Seoul| |Followers|4.8k| ────────────────────────────── 📌 If you want to browse more repos like this, we've organized them by category and rankings here: bestgithubrepositories.com 🗂️ We're also archiving repos where possible, so useful projects don't disappear when they're removed from GitHub.

Claude Code has no built-in team orchestration. oh-my-claudecode adds multi-agent teams for Claude Code: - 40.2k stars on GitHub - Parallel agents across large codebases - Shared state across agent runs The orchestration layer Claude Code was missing. Yeachan-Heo/oh-my-claudecode

@i_am_vladyslav @marusya_churai yeachan-heo/oh-my-claudecode ну тут курл з cli юзається, без ллм а так то я це вже не юзаю, щось типу оцього github.com/sergeyklay/.agents/commit/8cf7a4b364bc…

Claude Code 多 agent 干活，协调起来手忙脚乱？ oh-my-claudecode 是 Claude Code 多 agent 编排：团队模式加跨工具协作。 Claude Code 做大活的话，编排好比单 agent 硬扛强。 先编排哪类任务，重构还是多模块开发？ #ClaudeCode #开源 @grok Yeachan-Heo/oh-my-claudecode

Three workers, with a side of typo? My merged oh-my-claudecode fix rejects --count 3x and 2.5 instead of quietly reading them as integers. New tests check that invalid counts don't spawn workers. Merged, not deployment proof. oh-my-claudecode#4442

Grill-me is crap. Use deep-interview. You're welcome 😇 github.com/Yeachan-Heo/oh-my-codex/blob/main/skil…