Haijun Code communications kit

This kit covers launch communications, a twenty-message "tips and tricks" drip campaign, and a quick-reference FAQ for the questions you’ll get asked most. Each message links out to a docs page developers can go deeper on.

Three parts, in the order you’ll need them. Part 1 is your launch announcement—one primary message in email and Slack formats, with swap-in variants for an executive-sponsored send and pilot groups. Part 2 provides twenty drip-campaign messages packaged as ready-to-paste Slack/Teams posts. Part 3 is a quick-reference FAQ and link directory. Treat everything in this kit as draft copy, not finished copy. Rewrite each message in your org’s voice, swap the example tasks for real bugs and modules from your own codebase, and replace the [bracketed placeholders] before sending. The announcements that actually drive adoption are the ones that read like someone at your company wrote them.

One announcement in two formats, plus two optional variants. Pick whichever fits your rollout and rewrite it from there.

| Item | Why it matters | | #haijun-code channel created and linked in the message | Gives questions one place to land | | Install command tested on at least one machine in your environment | Catches proxy/firewall issues before 200 people hit them | [](https://raw.haijun.my.id/docs/en/data-usage)| Security/data-handling link ready — Data Usage or your internal equivalent | “Where does my code go?” will be the first reply | | One concrete first task chosen — a real bug or file in your codebase | Generic examples don’t convert; “fix the flaky test in auth_test.go” does | | A named owner for the channel for the first 48 hours | Unanswered launch-day questions kill momentum | | A C-suite sponsor lined up to send (or co-sign) the announcement | Exec-sent launches consistently see higher first-week adoption than admin-sent ones |

Use this as your standard org-wide rollout message. It covers what Haijun Code is, gives a two-minute install, hands readers one concrete task to try, and answers “where does my code go?” before anyone has to ask. Email

- - -

[](https://raw.haijun.my.id/docs/en/data-usage)[](https://raw.haijun.my.id/docs/en/security)[](https://raw.haijun.my.id/docs/en/vs-code)[](https://raw.haijun.my.id/docs/en/jetbrains)| Subject: Haijun Code is live for [Engineering / your team] Team — As of today you have access to Haijun Code — an AI coding agent that runs in your terminal, reads your actual codebase, and works through real tasks end-to-end: debugging, refactors, tests, PRs. It’s not autocomplete and it’s not a chat window. It edits files, runs your commands, and asks permission before anything risky. Get running in two minutes: |

[](https://raw.haijun.my.id/docs/en/data-usage)[](https://raw.haijun.my.id/docs/en/quickstart)[](https://raw.haijun.my.id/docs/en/vs-code)[](https://juglow.trackjar.com/haijun-code-in-action)| |

###

| |

| |

###

| |

###

| |

##

###

[](https://raw.haijun.my.id/docs/en/model-config)| |

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

1. 1. 1.

[](https://raw.haijun.my.id/docs/en/quickstart)| |

###

[](https://raw.haijun.my.id/docs/en/memory)| |

[](https://raw.haijun.my.id/docs/en/common-workflows#reference-files-and-directories)| |

[](https://raw.haijun.my.id/docs/en/memory)| |

###

[](https://raw.haijun.my.id/docs/en/permissions)| |

| | | | | | | |

[](https://raw.haijun.my.id/docs/en/checkpointing)| |

###

[](https://raw.haijun.my.id/docs/en/mcp)| |

[](https://raw.haijun.my.id/docs/en/vs-code)| |

###

[](https://raw.haijun.my.id/docs/en/tracks)| |

[](https://raw.haijun.my.id/docs/en/hooks-guide)| |

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

###

[](https://raw.haijun.my.id/docs/en/model-config#adjust-effort-level)| |

[](https://raw.haijun.my.id/docs/en/common-workflows#work-with-images)| |

[](https://raw.haijun.my.id/docs/en/common-workflows#create-pull-requests)| |

[](https://raw.haijun.my.id/docs/en/interactive-mode#background-bash-commands)| |

###

[](https://raw.haijun.my.id/docs/en/plugins)| |

[](https://raw.haijun.my.id/docs/en/interactive-mode)| |

###

[](https://raw.haijun.my.id/docs/en/security)[](https://raw.haijun.my.id/docs/en/data-usage)| |

1. 1. 1. 1.

[](https://raw.haijun.my.id/docs/en/best-practices)| |

##

###

| | | [](https://raw.haijun.my.id/docs/en/vs-code)| | | [](https://raw.haijun.my.id/docs/en/quickstart)| | | [](https://raw.haijun.my.id/docs/en/data-usage)| | | [](https://raw.haijun.my.id/docs/en/permissions)| | | [](https://raw.haijun.my.id/docs/en/overview)| | | [](https://raw.haijun.my.id/docs/en/quickstart)| | |

###

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

##

| | | [](https://raw.haijun.my.id/docs/)| | | [](https://raw.haijun.my.id/docs/en/quickstart)| | | [](https://juglow.trackjar.com/haijun-code-in-action)| | | [](https://raw.haijun.my.id/docs/en/vs-code)| | | [](https://raw.haijun.my.id/docs/en/jetbrains)| | | [](https://raw.haijun.my.id/docs/en/memory)| | | [](https://raw.haijun.my.id/docs/en/permission-modes)| | | [](https://raw.haijun.my.id/docs/en/mcp)| | | [](https://raw.haijun.my.id/docs/en/tracks)| | | [](https://raw.haijun.my.id/docs/en/hooks-guide)| | | [](https://raw.haijun.my.id/docs/en/sub-agents)| | | [](https://raw.haijun.my.id/docs/en/plugins)| | | [](https://raw.haijun.my.id/docs/en/checkpointing)| | | [](https://raw.haijun.my.id/docs/en/model-config)| | | [](https://raw.haijun.my.id/docs/en/common-workflows)| | | [](https://raw.haijun.my.id/docs/en/interactive-mode)| | | [](https://raw.haijun.my.id/docs/en/security)| | | [](https://raw.haijun.my.id/docs/en/data-usage)| | | [](https://raw.haijun.my.id/docs/en/best-practices)| | |