智能工作流

Requirements

• macOS or Linux (tested on both)
• Windows (experimental): Native support via ConPTY (built-in on Windows 10+). Just npm install -g imcodes — no extra software needed. WSL also works.
• Node.js >= 22
• Terminal multiplexer: tmux (Linux/macOS). Windows uses ConPTY (auto-detected, built-in).
• At least one AI coding agent: Claude Code (CLI or SDK), Codex (CLI or SDK), Gemini CLI, OpenClaw, or Qwen

CI → agent: post-build trigger

imcodes send "Claude" "tests failed on main, check CI log at /tmp/ci.log and fix" --reply ```

Use cases: log monitoring → auto-fix, webhook-triggered code review, CI failure auto-diagnosis, scheduled data pipeline checks, custom approval workflows with output written to specific files for human review.

Install

npm install -g imcodes

One-Command Setup

Deploy server + daemon on a single machine. Requires Docker and a domain with DNS pointing to the server.

npm install -g imcodes
mkdir imcodes && cd imcodes
imcodes setup --domain imc.example.com

This generates all config, starts PostgreSQL + server + Caddy with automatic HTTPS, creates the admin account, and binds the local daemon — all in one step. Credentials are printed at the end.

To connect additional machines:

npm install -g imcodes
imcodes bind https://imc.example.com/bind/<api-key>

Manual Setup

If you prefer to configure manually:

git clone https://github.com/im4codes/imcodes.git && cd imcodes
./gen-env.sh imc.example.com        # generates .env with random secrets, prints admin password
docker compose up -d

The generated docker-compose.yml already uses pgvector/pgvector:pg18 for PostgreSQL.

Login at https://your-domain with admin and the printed password. Bind your dev machine with imcodes bind.

Install & Bind (Windows)

npm install -g imcodes
imcodes bind https://app.im.codes/bind/<api-key>

Quick Start

Self-hosting is strongly recommended. The shared instance at app.im.codes is for testing only — it comes with no uptime guarantees, may be rate-limited, and could be targeted. This is a personal project with no commercial support. For anything beyond evaluation, deploy the server on your own infrastructure.

Use app.im.codes for evaluation, or self-host for anything real.

imcodes bind https://app.im.codes/bind/<api-key>

This binds your machine, starts the daemon, registers it as a system service, and brings the machine into the web/mobile dashboard.

Screenshots

Troubleshooting (Windows)

If the daemon stops after an auto-upgrade, regenerate the launch chain:

imcodes repair-watchdog

This rewrites the watchdog script and scheduled task with the current Node.js and imcodes paths. Needed after Node.js version switches (nvm, fnm) or if the daemon won't restart after upgrade.

If imcodes is "not recognized as internal or external command" after upgrade, the npm global directory may not be on your PATH. Fix it:

npm prefix -g

Copy the output path and add it to your PATH:

setx PATH "<npm-prefix-path>;%PATH%"

Then open a new terminal window.

Check the daemon watchdog log for errors:

%USERPROFILE%\.imcodes\watchdog.log