By GxFn
Unattended control loops for multi-window agent work: controller state roots, task packages, direct-session delivery, evidence review, and Design/Test intake for Claude Code desktop and terminal.
Health-check an existing Wakeflow workspace and converge missing or outdated Claude Code surfaces
Prepare and send one Wakeflow delivery to a target window session (controller only)
Initialize the current workspace as a Wakeflow control workspace (dry-run first, apply after confirmation)
Review Wakeflow target results with raw evidence and record an explicit controller decision
Show Wakeflow workspace status — demands, eligible work, deliveries, and window readiness
Use when Wakeflow total control starts or resumes Wakeflow Delivery Loop in Claude Code, reviews target result envelopes, creates dispatch packets, builds delivery envelopes, sends deliveries to tmux-resident window sessions with the wakeflow-claude-host helper, decides acceptance / rework / block / next wave, or stops unattended automation.
Use when working inside Wakeflow on workspace initialization / setup, CLAUDE.md / skill layering, TODO / Backlog intake, Design handoff intake, idle-window scheduling, window coverage, task-package dispatch, producer/consumer sequencing, unified dispatch prompts, test handoffs, validation boundaries, or workspace script pipelines. This skill supplements CLAUDE.md and must not override its hard boundaries.
Use when a tmux-resident target Claude Code window session receives a Wakeflow Delivery Loop direct-thread delivery in its tmux pane, executes only its assigned dispatch packet, reports a TargetResultEnvelope, sends the controller-return with the wakeflow-claude-host helper, or enforces target-window boundaries without claim / finish / chain-next state.
Admin access level
Server config contains admin-level keywords
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Unattended control loops for multi-window agent work.
Wakeflow turns a local Codex workspace into a disciplined controller system: one controller window, focused repository windows, explicit state roots, compact direct-thread delivery, and evidence-based acceptance.
Large agent-assisted work rarely lives in one repository or one conversation. A single goal may require a controller, product repositories, a design window, and a real-scenario test window. Without a shared operating model, the work degrades into scattered prompts, copied status tables, unclear ownership, and unfinished evidence review.
Wakeflow provides the missing control layer:
Wakeflow is not a command launcher with nicer names. It is a reusable workflow capability for keeping multi-window agent work legible, bounded, and resumable.
flowchart TD
User["User goal"] --> Controller["Controller Codex window"]
Controller --> Gates["AGENTS.md gates<br/>goal, boundary, evidence, stop rules"]
Controller <--> StateRoot["State root<br/>.workspace-active/..."]
StateRoot --> Tasks["Task packages"]
Tasks --> Delivery["Delivery envelopes"]
LocalRuntime[".workspace-local<br/>thread registry + derived window config"] -. "lookup" .-> Delivery
Delivery --> Host["Codex host thread tools"]
Host --> Targets["Repository / Design / Test windows"]
Targets --> Repos["Responsibility roots"]
Targets --> Results["TargetResultEnvelope<br/>with evidence refs"]
Results --> Controller
Controller --> Ledger["wakeflow-ledger<br/>durable project records"]
The controller is the only acceptance authority. Scripts and MCP tools create, validate, summarize, and record machine data, but they do not widen scope, decide product behavior, or declare a task complete.
Wakeflow uses the same two-layer marketplace shape as Lark Remote: the
repository root is the development workspace, and the installable plugin
artifacts live under plugins/. The repository ships two host editions built
from one shared core:
| Host | Artifact | Catalog |
|---|---|---|
| Codex | plugins/codex-wakeflow/ | .agents/plugins/marketplace.json |
| Claude Code | plugins/claude-code-wakeflow/ | .claude-plugin/marketplace.json |
Install the Claude Code edition from inside Claude Code:
/plugin marketplace add GxFn/Wakeflow
/plugin install wakeflow@gxfn
The Claude Code edition is terminal-only: every Wakeflow window (controller
included) is a tmux-resident interactive claude session in the wakeflow
tmux server session, and a Wakeflow thread id is the window's Claude Code
session id (stable across resumes). See
plugins/claude-code-wakeflow/README.md
for the full Claude Code guide.
Install the public Codex plugin artifact:
npx codex-marketplace add GxFn/Wakeflow/plugins/codex-wakeflow --plugin
For a pinned release after the matching tag exists:
npx codex-marketplace add https://github.com/GxFn/Wakeflow/tree/v0.1.2/plugins/codex-wakeflow --plugin
If the Codex dialog separates source, ref, and sparse path, use the repository
URL, the desired ref, and plugins/codex-wakeflow as the sparse path.
For local development, register this checkout as its own local marketplace:
[marketplaces.gxfn]
source_type = "local"
source = "/absolute/path/to/Wakeflow"
[plugins."wakeflow@gxfn"]
enabled = true
npx claudepluginhub gxfn/wakeflow --plugin wakeflowLocal-first project memory, Recipes, Guard checks, and recoverable bootstrap jobs.
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Browser automation and end-to-end testing MCP server by Microsoft. Enables Claude to interact with web pages, take screenshots, fill forms, click elements, and perform automated browser testing workflows.
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
A growing collection of Claude-compatible academic workflow bundles. Covers scientific figures, manuscript writing and polishing, reviewer assessment, citation retrieval, data availability, paper reading, literature search, response letters, paper-to-PPTX conversion, and evidence-grounded Chinese invention patent drafting. Rules are organized as reusable skill folders with explicit workflows and quality checks.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.