claude-work-mode plugin

A Claude Code plugin that switches session modes with /work-mode: autonomous work, delegation and converging wrap-up.

  • 177 ★ on the repository
  • Last commit
  • MIT
Plugin

Extended access

Why this level

  • In `auto` the model takes local decisions and commits without asking and postpones hard stops.
  • The hook gates can block `git commit` commands and file writes.
All reasons and checks

danyuchn/claude-work-mode

Install

Works in

Manual install

/plugin install work-mode --marketplace danyuchn/claude-work-mode

Answer `y` to adding the marketplace and pick a scope. Claude Code 2.1.314 or newer is required.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • In `auto` the model takes local decisions and commits without asking and postpones hard stops.
  • The hook gates can block `git commit` commands and file writes.

This is third-party code. Review the repository files before installing.

What it does

claude-work-mode adds three session modes to Claude Code. In `auto` the model does not stop at internal reversible steps such as local files, commits and tests. Hard stops such as outgoing messages, installs, secrets, unrecoverable deletes, payments and permission changes go to a list shown once at the end. In `out` batch work that a spot check can verify is handed to a background subagent or an external CLI while the main thread verifies the result. `wrap` converges the work: no new branches open and only new or changed decisions are listed with a recommendation. Modes are per session and combine, for example `/work-mode auto wrap`. The mode text reaches the model once and repeats after context compaction or resume. A bare command opens a picker. A separate `work-mode-gates` plugin adds hooks: a guard against stray report files, a `git commit` check and a label check on decisions.

Who it is for. People who run long Claude Code sessions and are tired of answering small confirmations or receiving a sprawling finale.

Good fit when

  • The task is large but its steps are local and reversible, and the model should not interrupt with questions.
  • Bulk extraction, classification or review is delegated to a background subagent while the main thread only verifies.
  • The session is ending and open items have to be closed with a short list of decisions.
  • Hooks should not ask needlessly: in `auto` the gates deny and tell the model a workable path.

Not a fit when

  • You need tight human control of every step: `auto` postpones questions until the end.
  • The Claude Code version is older than 2.1.314: the plugin needs function hooks.
  • The environment lacks `bash`, `jq`, `git` or `python3`, which the gates need.

Example request

Enable `/work-mode auto wrap`, finish the test migration and show the deferred hard stops and new decisions at the end.

Limitations

You need Claude Code 2.1.314 or newer with function-hook support. The gates require `bash`, `jq`, `git` and `python3`. Modes are written to `~/.claude/state/tempo/<session_id>` so shell hooks can read them. In `auto` hard stops do not vanish but accumulate until the end, so judge which actions you are ready to approve as a batch. Prompt language follows `WORK_MODE_LOCALE`, the Claude Code language setting and the system locale, with English and Traditional Chinese available.

How to disable. Disable the plugins through `/plugin` and delete `~/.claude/state/tempo`. The optional config lives in `~/.config/work-mode/config.json`.

FAQ

How do I install claude-work-mode?

Run `/plugin install work-mode --marketplace danyuchn/claude-work-mode`, agree to adding the marketplace and pick a scope. Gates install separately with `/plugin install work-mode-gates --marketplace danyuchn/claude-work-mode`.

What does auto mode do?

The model does not stop at internal reversible steps. External actions, installs, secrets and payments go to a pending list reported once at the end. Calls that will raise a confirmation prompt are run last, back to back.

Can modes be combined?

Yes, for example `/work-mode auto wrap`. With `out wrap` only already open work is delegated and the wrap waits until delegated results are verified.

What is in work-mode-gates?

Three gates: a guard against new `SUMMARY*`, `REPORT*` and similar files, a check on `git commit` with paths and a label check on decisions in a reply. In `auto` a gate denies with a hint instead of asking.

How do I turn a mode off?

`/work-mode off` returns normal behavior. Modes apply only within a session.

Discussion

No questions or reviews yet.

Plugins

A personal Claude Code setup: four loading layers, an advisor model mode, ten hooks and working commands

WorkflowExtended access156Repository stars

Workflows for Claude Code: /do, /omo, /bmad-pilot and more commands, with Codex, Gemini or OpenCode writing the code through codeagent-wrapper

PluginBroad access2.8KRepository stars

claude-mods adds 112 skills, 3 agents and 3 commands to Claude Code: stacks, agent operation, defense, session continuity.

PluginBroad access81Repository stars

Claude Code plugin that runs complex tasks as step-by-step workflows with quality gates and reviews changes against project rules.

PluginExtended access51Repository stars

Claudette runs several Claude Code sessions in parallel, each in its own git worktree, from a window or the console

CLIBroad access87Repository stars

A plugin that turns one Claude Code session into a controller handing tasks to workers in tmux and collecting their results.

PluginBroad access114Repository stars

README in short

The plugin consists of TypeScript modes and hooks, and an optional second plugin adds shell gates. Language, name and nudge threshold are configured in a JSON file.

README badge

Report a problem