omarchy-multi-agent-kit

KO | EN

gitlite — search

#javascript #python #hacktoberfest #react #ai #typescript #llm #go #golang #android #machine-learning #rust #deep-learning #linux

omarchy-multi-agent-kit

★ 11 Open GitHub ↗

Dotfile snippets and runbooks for the Omarchy-based multi‑agent workflow I use at Minotaur Capital—worktree helpers, Codex briefs, dev-server automation, and optional

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Omarchy Multi-Agent Worktree Kit

> Building, guiding, and cleaning up parallel Codex agents on [Omarchy](https://omarchy.org/).

Set this up once and you can spin up a fresh worktree, brief Codex, launch isolated dev services, and unwind everything in under a minute.

I’m Thomas Rice, Co-Founder of [Minotaur Capital](https://minotaurcapital.com/). Our primary codebase is called “Taurient”, which is why the examples use `taurient` in paths and filenames. Swap those references for your own repo and directory structure as you copy the snippets across.

## How To Use This Repo
Follow the docs in order:

1. [Shell + Worktree Helpers](./01-shell-worktrees.md) – add aliases, `wt`/`dwt`, and the optional `newterm` launcher.
2. [Dev Server Automation](./02-dev-server.md) – create `~/dev.sh`, add the baseline `/etc/hosts` entry, and wire nginx to the generated configs.
3. [Agent Briefings](./03-agent-briefings.md) – keep reusable `AGENTS.md`, `PROJECT.md`, and `PROJECT_AI_NOTES.md` templates in every worktree.
4. *(Optional)* [UI Extras](./04-ui-extras.md) – Hyprland workspace labels, Waybar modules, and a voice-toggle binding.

Each document tells you exactly which file to edit, what to paste, and which bits are optional.

## Workflow In 60 Seconds
1. **Spawn a workspace:** `wt <name>` clones a Git worktree, seeds Poetry, and (optionally) renames the Hyprland workspace so Waybar shows the new label.
2. **Brief the agent:** Update `PROJECT.md`, keep long-lived guidance in `AGENTS.md`, then run `cproj` to launch Codex in high-reasoning mode.
3. **Launch infra:** `tdev` allocates a deterministic port, tags `/etc/hosts`, writes an nginx vhost, and opens a terminal for the Taurient app server.
4. **Develop:** Iterate on the brief while Codex and your dev servers do the work; toggle voice input with `SUPER+S` if you keep the optional binding.
5. **Clean up:** `dwt <name>` prunes the worktree, removes nginx + hosts artefacts, clears saved port metadata, and resets the workspace label.

## What You Get
- Deterministic hostname + port per worktree (`<branch>.t.com`, hashed port offsets) so parallel branches never collide.
- A repeatable agent briefing workflow—Codex always reads your stack rules and the current plan before it writes code.
- Optional desktop polish (Waybar, Hyprland, voice toggle) that makes multi-agent work visible at a glance.

## Make It Yours
- Replace the placeholder paths (e.g. `$HOME/minotaur/taurient`) with your own repo layout before running the scripts.
- Swap the terminal launcher (`newterm`) or the app entry points in `dev.sh` to match your toolchain.
- Skip any optional sections if you do not use Hyprland/Waybar or voice input—the core workflow only needs the shell helpers, `dev.sh`, and the briefing files.
- Add `PROJECT.md` and `PROJECT_AI_NOTES.md` to your `.gitignore` so the briefs and scratchpad never leave your workstation.

Once everything is wired up, the flow is:

```bash
wt my-new-feature
# edit PROJECT.md (and optionally PROJECT_AI_NOTES.md)
cproj
```

---
Questions or tweaks you’d like to see? Fork it, adapt it, and keep refining your multi-agent workflow.

omarchy-multi-agent-kit

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

omarchy-multi-agent-kit

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README