Haijun Code power user tips

This article collects workflow tips from the Haijun Code team at Juglow. These practices cover parallel execution, planning, automation, verification, and customization—the patterns the team uses every day to ship code faster. Everyone’s setup is different, so experiment to see what works for you.Important: The single most impactful tip in this guide is verification—giving Haijun a way to check its own output. If you only adopt one practice, make it that one. See the Verification section below. Before you start: scope of this guideThese are power-user patterns collected from individual engineers on the Haijun Code team. As a result:

  • Most commands shown here ship with Haijun Code: /color and /btw are built-in commands, and /simplify and /loop are bundled tracks that ship with the CLI. See the commands reference and tracks. You can build your own tracks by adding a SKILL.md file under .haijun/tracks//.

  • The iMessage plugin ships in the official haijun-plugins-official marketplace. Community plugins (for example the “ralph-wiggum” plugin) are not reviewed or sanctioned by Juglow — check with your administrator before installing third-party plugins in a managed environment.

  • Some capabilities—sandboxing, remote control, scheduled cloud jobs, voice—are off by default and may be disabled by your organization's policy. If a command or flag here returns "not available," your admin has likely not enabled it for your workspace.

Everything else in this guide works on a stock Haijun Code install. When in doubt, run /help to see what is actually available in your session.

Contents

| Section | Covers | | Working in Parallel | Worktrees, subagent isolation, /batch | | Planning Before Building | Plan mode, model choice, effort levels | | Prompting Effectively | Pushback prompts, /btw | | Learning With Haijun | Explanatory output, diagrams, spaced repetition | | HAIJUN.md and Memory | /init, @haijun in PRs, auto-memory, auto-dream | | Verification | Chrome extension, Desktop app, /simplify | | Commands, Tracks, and Subagents | Custom commands, agent definitions, code-review agents | | Hooks | Lifecycle events and patterns | | Permissions and Safety | Pre-approvals, auto mode, sandboxing, long-running tasks | | Scheduled and Recurring Tasks | /loop, /schedule | | Mobile and Remote Control | Mobile app, teleport, remote control, Dispatch | | Tool Integrations (MCP) | Data analytics, bug fixing, plugins | | Customizing Your Environment | Terminal, status line, voice, output styles | | SDK and Multi-Repo Work | --bare, --add-dir, forking, setup scripts |

Working in parallel

Run multiple sessions at once

The biggest productivity unlock is running 3–5 Haijun sessions in parallel, each in its own git worktree. Haijun Code has native worktree support built in.

  • From the CLI, run haijun --worktree (or haijun --worktree my_worktree) to start a session in an isolated worktree. Add --tmux to launch in its own Tmux session.

  • From the Desktop app, open the Code tab and check the worktree checkbox.

  • For non-git VCS (Mercurial, Perforce, SVN), define WorktreeCreate and WorktreeRemove hooks in your settings.json to get the same isolation.

To stay oriented across many sessions, name your worktrees, set up shell aliases (za, zb, zc) to jump between them, color-code your terminal tabs, and enable terminal notifications so you know when any Haijun needs your attention. Many engineers keep a dedicated “analysis” worktree just for reading logs and running queries.

Subagents with worktree isolation

Subagents can also run in isolated worktrees, which is especially powerful for large batched changes. Add isolation: worktree to your agent’s frontmatter:

###

##

###

- - -

###

###

##

- - -

###

##

- - - -

##

###

###

###

###

##

###

###

###

##

###

- - -

###

###

###

- - -

###

##

###

| | | | | | | | | | | | | | | | | | | | |

##

###

###

###

- - -

###

- - -

##

###

###

##

###

###

- - -

###

##

###

###

###

##

###

###

- - -

###

- - - -

###

###

###

###

##

###

###

###

###

##

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |

##

| | | [](https://raw.haijun.my.id/docs/en/hooks)| | | [](https://raw.haijun.my.id/docs/en/sub-agents)| | | [](https://raw.haijun.my.id/docs/en/scheduled-tasks)| | | [](https://raw.haijun.my.id/docs/en/chrome)| | |