Agenc

<div align="center"> <h1>AgenC: the CEO command center for your fleet of Claudes</h1> </div> </h1> <p align="center"> AgenC is an AI work factory focused on learning loops.</br> </br> <b>The idea:</b> Launch tons of parallel Claudes. They stumble. Turn friction → a smarter factory. Repeat.</br> </br> You spend your time building the factory; the Claudes do the rest.</br> </br> <a href="#why-agenc">Why AgenC</a> | <a href="#quickstart">Quickstart</a> | <a href="#how-it-works">How It Works</a> | <a href="https://discord.gg/x9Y8Se4XF3">Discord</a> </p> </p>

2026-02-16 demo

Why AgenC

If you're like most people, you use Claude like this:

Much better is John Rush's philosophy of Inputs, Not Outputs:

Each iteration makes all future outputs better.

But it doesn't scale.

The Claudes step on each other, you end up spawning heaps of side Claude windows, juggling the windows becomes a circus, and it's easy to forget what you even started working on.

AgenC tames this chaos. It provides:

• 📦 Claude session isolation in fully independent sandboxes (no Git worktrees, no merge queue - each agent is completely independent!)
• 🎨 Session management and command palette + hotkeys so launching new sessions, switching windows, stopping/resuming sessions, and rolling lessons back into your Claude config is a thought away
• 🔧 Palette customization so your top-used operations are easy

<!-- - 🔁 Cron jobs so your factory can work while you're away -->

• 🔐 1Password secrets injection
• 🏗️ Claude orchestration so one Claude can spawn and coordinate other Claude teammates
• 🤖 An AI assistant that knows how to configure & drive AgenC so you never have to use CLI commands

And of course, AgenC is built with AgenC.

⚠️ ADDICTION WARNING ⚠️

AgenC feels great to use, like painting with your mind. But you should know it has a videogame-like addictive quality.

Because it's so easy launch work, you get a "just one more mission" feeling.

I noticed while building AgenC that it's hard to switch off and go to sleep. My brain would always be buzzing with ideas, and I'd wake up in the middle of the night wanting to launch new work.

Please remember to take breaks and leave sufficient wind-down time before sleep!

Quickstart

Prerequisites

• MacOS (for now)
• Claude Code installed and in your PATH

Install

brew tap mieubrisse/agenc
brew install agenc

This automatically installs required dependencies (gh, fzf, tmux).

If you're not logged in to gh, use:

gh auth login

1. 🔧 Initialize

The AgenC directory defaults to ~/.agenc. Override with AGENC_DIRPATH if needed.

Run the following and answer the prompts:

agenc config init

I recommend "yes" to creating a config repo; AgenC will sync it to GitHub automatically.

The AgenC interface is tmux. Run this so you get the AgenC keybindings:

agenc tmux inject

If you haven't used tmux before, here's a starter ~/.tmux.conf:

set -g extended-keys on

# Ctrl-h goes to previous window
bind -n C-h previous-window

# Ctrl-l goes to next window
bind -n C-l next-window

# Ctrl-; toggles between panes inside a window
bind -n 'C-;' select-pane -t :.+

# Ctrl-shift-h moves a window to the left
bind -n C-S-h swap-window -t -1\; select-window -t -1

# Ctrl-shift-l moves a window to the right
bind -n C-S-l swap-window -t +1\; select-window -t +1

2. 🚀 Launch

AgenC's interface runs inside tmux. You can use it from any tmux session — agenc attach is just a convenience that creates or resumes a tmux session called agenc:

agenc attach

If you already have your own tmux workflow, you can skip agenc attach and use agenc commands directly from any tmux session. The command palette and keybindings work everywhere.

You'll be dropped into the repo selection screen. Select "Github Repo" and enter a repo you're working on.

AgenC will clone it, launch a new mission, and drop you into Claude to start your work.

Missions are the main primitive of AgenC: disposable self-contained workspaces with a fully independent copy of the Git repo (no merge queue needed - the agents figure it out, just like humans).

3. 🎨 Command Palette

Inevitably you'll want to do work on the side while Claude is grinding away.

Press ctrl-y to open the command palette and...

• 🐚 Open a side shell in your current mission's workspace ("Side Shell" or ctrl-p)

  💡 cmdk is amazing in the side shell

• 🚀 Launch a side mission ("New Mission" or ctrl-n, or "Side Claude" or "Quick Claude")
• 🔀 Switch between your running missions ("Switch Mission" or ctrl-m)
• 💬 Send me feedback about AgenC!

These commands are cheap; use them liberally. AgenC is designed to help you manage having 10+ threads going at once.

The command palette can be configured with custom hotkeys and custom commands.

The hard way to do this is through the CLI helpdocs the agenc config paletteCommand. For example, this is to quickly set up a new Github repo:

agenc config paletteCommand add newRepo \
    --title "🆕 New Repo" \
    --command "agenc mission new \
        --blank \
        --prompt 'I want to create a new GitHub repository. Please:
            1) Ask me what the repository name should be and whether I want it public or private
            2) Create it on GitHub using the gh CLI
            3) Initialize this blank mission directory as a git repo and set it up to track the newly created GitHub repository.'"

The easier way is through the Adjutant.

5. 🤖 Adjutant

AgenC has an AI assistant called Adjutant ("Adjutant" on the palette or ctrl-t for Side Adjutant) that knows how to configure AgenC, as well as launch and manage missions.

You can use the agenc config commands to configure stuff like palette commands... but now I just talk to the Adjutant for my AgenC configuration needs.

6. Mission Management

When you're done with a mission, you don't need to explicitly stop it — just detach and move on. Use "Detach Mission" (ctrl-i) on the command palette to unlink the current mission from your tmux window, or "Exit" to leave the AgenC tmux session entirely. Either way, your missions keep running in the background. After a period of inactivity, AgenC will automatically idle-kill them. You can always re-attach later with "Attach Mission" on the command palette, which will pick up right where you left off.

You can see all missions with agenc mission ls, and switch between missions with "Attach Mission" (ctrl-m) on the command palette.

If you want to explicitly stop a mission, you can use "Mission Stop" (ctrl-s) on the palette. Since each mission is an isolated workspace, no work is lost.

Full CLI docs: docs/cli/

6. 🔐 Secrets

If you create a .claude/secrets.env with 1Password CLI secret references in it, AgenC will resolve them on mission launch and inject them into Claude. This is useful for MCP server credentials.

For example:

.claude/secrets.env:

SUBSTACK_SESSION_TOKEN="op://Private/Substack Session Token/credential"
SUBSTACK_USER_ID="op://Private/Substack Session Token/username"

.mcp.json:

{
    "mcpServers": {
        "substack-api": {
            "command": "npx",
            "args": ["-y", "substack-mcp@latest"],
            "env": {
                "SUBSTACK_PUBLICATION_URL": "https://mieubrisse.substack.com/",
                "SUBSTACK_SESSION_TOKEN": "$SUBSTACK_SESSION_TOKEN",
                "SUBSTACK_USER_ID": "$SUBSTACK_USER_ID"
            }
        }
    }
}

<!-- ### 7. 🔁 Crons > ⚠️ Crons only work on MacOS for now! Crons let your factory work while you're away. AgenC runs scheduled headless missions — think "generate a daily report at 9am" or "take a tech debt cleanup pass at the codebase" or "process my inbox every morning". **Create a cron job:** The easiest way is through the Adjutant. Just ask: "Create a cron that runs daily at 9am to generate a status report." You can also use the CLI wizard: ```bash agenc cron new daily-report ``` The wizard asks for: - **Schedule** — Standard cron expression (e.g., `0 9 * * *` for 9am daily) - **Prompt** — What you want Claude to do - **Git repo** (optional) — Repository to clone into the workspace - **Timeout** (optional) — Max runtime (default: 1 hour) **What happens when a cron runs:** A headless mission gets spawned at the scheduled time. The mission is a regular mission, and runs in isolation with its own workspace like normal. Output is captured to a log file with automatic rotation. **View cron jobs:** ```bash agenc cron ls ``` Shows all crons with their schedules, enabled status, last run time, and next run time. **View cron output:** ```bash agenc cron logs daily-report ``` Shows output from the most recent run. Add `-f` to tail the log in real-time. **View run history:** ```bash agenc cron history daily-report ``` Shows past runs with start time, mission ID, status, and duration. **Manually trigger a cron:** ```bash agenc cron run daily-report ``` Runs the cron immediately as a headless mission. Useful for testing before committing to a schedule. **Disable/enable:** ```bash agenc cron disable daily-report agenc cron enable daily-report ``` **Delete:** ```bash agenc cron rm daily-report ``` **Cron expressions:** AgenC uses standard 5-field cron expressions: `minute hour day-of-month