@logicseek/hello-cc 0.1.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,462 @@
+# hello-cc
+
+<p align="center">
+  <img src="assets/logo.svg" width="160" alt="hello-cc logo">
+</p>
+
+<p align="center">
+  <a href="https://github.com/Dullne/hello-cc"><img src="https://img.shields.io/github/stars/Dullne/hello-cc?style=flat-square&color=40c4aa" alt="GitHub stars"></a>
+  <a href="https://nodejs.org"><img src="https://img.shields.io/badge/node-%3E%3D24.0.0-brightgreen?style=flat-square" alt="node >=24"></a>
+  <a href="./LICENSE"><img src="https://img.shields.io/badge/license-Apache%202.0-blue?style=flat-square" alt="license Apache 2.0"></a>
+</p>
+
+<p align="center"><b>English</b> | <a href="README.zh-CN.md">中文</a></p>
+
+`hello-cc` connects Claude Code, Codex, and other coding CLI sessions into a
+project-local peer mesh. The command is `hcc`.
+
+The default model is a flat peer mesh, not a fixed main/worker topology. Every
+terminal session is a named peer that can see open tasks, receive directed
+messages, hold locks, hand off progress, and be observed or operated from the
+web console.
+
+```text
+<project>/.hello-cc/mesh.db
+```
+
+## Install
+
+**Node 24+ is required** because hello-cc uses built-in `node:sqlite`.
+
+Install the CLI globally from npm:
+
+```bash
+npm install -g @logicseek/hello-cc
+```
+
+Or run it without a global install:
+
+```bash
+npx @logicseek/hello-cc web
+```
+
+For local development, run the CLI directly from the checkout:
+
+```bash
+node ./bin/hcc.mjs web
+```
+
+After a global install, both `hcc` and `hello-cc` are available. The examples
+below use `hcc`.
+
+## Default Entry
+
+Run one command in the project directory:
+
+```bash
+cd /path/to/project
+hcc web
+```
+
+`hcc web` is the default entrypoint. It automatically:
+
+1. Initializes `.hello-cc/mesh.db` in the current directory
+2. Writes bounded guidance blocks: `.hello-cc/HCC.md`, `CLAUDE.md`, `AGENTS.md`
+3. Installs or refreshes Claude Code hooks: `~/.claude/settings.json`
+4. Installs or refreshes Codex hooks: `~/.codex/hooks.json`
+5. Installs `~/.hcc-shims/claude` and `~/.hcc-shims/codex`
+6. Adds `~/.hcc-shims` to the shell PATH
+7. Ensures `tmux` is available, with best-effort automatic install and a clear
+   install command if that fails
+8. Starts or reuses the global web console, registers the current project,
+   prints URL/PID/runtime/log, then returns the terminal to you
+
+Example output:
+
+```text
+hello-cc web started in background
+pid: 12345
+project: /path/to/project
+database: /path/to/project/.hello-cc/mesh.db
+runtime: /path/to/project/.hello-cc/runtime.json
+log: /path/to/project/.hello-cc/web.log
+open: http://<machine-ip>:8787/?project=%2Fpath%2Fto%2Fproject
+local: http://127.0.0.1:8787/?project=%2Fpath%2Fto%2Fproject
+shims: installed claude, codex
+PATH updated in ~/.bashrc; open a new terminal or source it
+stop: hcc down
+```
+
+`hcc web` uses a single global web runtime. Running `hcc web` again from
+another project directory does not open another port; it registers that project
+with the same web console. The frontend Project selector switches between
+registered roots. Each project still keeps its own `.hello-cc/mesh.db`, so
+tasks, messages, locks, and peers stay isolated.
+
+After the first shim install, open a new terminal or run:
+
+```bash
+source ~/.bashrc
+```
+
+Then direct project-local commands are wrapped automatically:
+
+```bash
+claude
+codex
+claude --resume <session-id>
+codex resume <session-id>
+```
+
+The wrappers create or reuse **local persistent tmux terminals**:
+
+- The local terminal attaches to the same tmux session and remains usable.
+- The web console controls the same tmux pane, not a temporary browser-only
+  terminal.
+- `hcc down` stops only the web runtime. It does not kill tmux sessions.
+- Running `hcc web` again reattaches live recorded tmux panes.
+
+For local coordination without Web or shims, use the lower-level command:
+
+```bash
+hcc up
+```
+
+Most users should start with `hcc web`.
+
+## Project Boundary
+
+By default, the project boundary is the **current working directory**. If the
+current directory has no `.hello-cc/mesh.db`, hello-cc creates one on first use:
+
+```text
+/repo-a/.hello-cc/mesh.db
+/repo-a/subdir/.hello-cc/mesh.db
+```
+
+Those are two different projects by default. Sessions communicate naturally
+when they start from the same project path.
+
+To share one bus across paths or worktrees, opt in explicitly:
+
+```bash
+hcc --root /path/to/project web
+export HCC_ROOT=/path/to/project
+export HCC_DB=/path/to/project/.hello-cc/mesh.db
+```
+
+hello-cc does not automatically inherit a parent directory's bus. That avoids
+subdirectory sessions joining a broader project by accident.
+
+## Communication Model
+
+hello-cc is not point-to-point CLI messaging and does not require MCP. The core
+is a project-local SQLite WAL bus:
+
+```text
+Claude/Codex/plain shell
+  -> hooks / hcc commands / web runtime
+  -> .hello-cc/mesh.db
+  -> peers / tasks / messages / locks / handoffs / events
+  -> tmux-backed terminal control
+```
+
+Tasks and messages have different read semantics:
+
+- **Tasks** are project facts. Every peer sees tasks until they become `done`
+  or `abandoned`. A task does not disappear because one terminal read it.
+- **Messages** are addressed mailbox items. `hcc msg inbox` defaults to unread
+  messages for the current peer, and `hcc msg ack` records per-peer read state.
+- `ask` and `broadcast` write durable messages. With `--inject`, they also send
+  live input to runtime-attached terminals.
+- Locks use SQLite transactions and TTLs. They are coordination locks, not a
+  filesystem sandbox.
+
+## How Claude/Codex Knows Other Sessions
+
+The primary path is hook injection, not `CLAUDE.md`.
+
+`hcc web` installs Claude Code and Codex hooks. On session start, user prompt
+submit, tool events, and idle events, hooks inject the current hello-cc snapshot
+into the model context:
+
+- current peer identity
+- active peer list
+- open tasks
+- unread messages for the current peer
+- active locks
+- suggested commands such as `hcc status`, `hcc peers`, `hcc task list`,
+  `hcc msg inbox`, and `hcc lock list`
+
+So when an attached Claude/Codex session is asked what other sessions are doing,
+it should answer from the latest hello-cc state instead of generic isolation
+knowledge.
+
+If a session still says it cannot know, likely causes are:
+
+- `hcc web` has not been run in the project directory
+- the terminal has not loaded `~/.hcc-shims` into PATH
+- Codex hooks are not enabled or the installed hook has not been trusted in
+  Codex's hook review flow
+- the CLI was started in a different project directory
+- the session was an already-open raw terminal before hello-cc was installed
+- the provider CLI version did not fire the expected hook
+
+To verify Claude Code hook injection directly, run a one-shot debug call from
+the same project:
+
+```bash
+claude -p 'Do you see hello-cc open tasks?' --debug hooks --debug-file /tmp/hcc-claude-hooks.log
+```
+
+The debug log should contain `Hook UserPromptSubmit ... provided
+additionalContext` and the `hello-cc coordination` block. If that is present but
+the model still answers from generic isolation knowledge, restart/resume the
+session through the shim and ask again; hello-cc injects a stronger instruction
+on every new user prompt.
+
+## Web Console
+
+Start local and LAN-visible control:
+
+```bash
+hcc web
+```
+
+Use a token only when you want one:
+
+```bash
+HCC_WEB_TOKEN='choose-a-long-token' hcc web --host 0.0.0.0 --port 8787
+```
+
+Open from another machine on the same network:
+
+```text
+http://<machine-ip>:8787/
+```
+
+The web console can:
+
+- switch between multiple registered project roots on one port
+- register another project path from the browser and switch to it without
+  starting another web server
+- show project state: peers, tasks, messages, locks, handoffs, events
+- operate local terminals: start Claude/Codex/shell, send keyboard input, view
+  output, detach runtime control
+- start a new session by choosing only its kind; the browser form generates the
+  next project-local alias, uses the selected Project root as the working
+  directory, and runs the default command for that kind
+
+Browser-controlled sessions are local tmux terminals:
+
+- sessions started by the web form: tmux-backed
+- sessions started by `hcc peer start`: tmux-backed
+- direct `claude` / `codex` sessions started through shims: tmux-backed
+- existing tmux panes attached with `hcc peer attach`: tmux-backed
+
+Already-open raw terminals cannot be captured or controlled unconditionally
+unless they started under tmux, screen, or a hello-cc shim. They can still
+participate in tasks, messages, and locks through hooks and `hcc` commands.
+
+## Common Commands
+
+```text
+# Default entry
+hcc web [--host HOST] [--port N] [--token TEXT] [--local] [--no-discover] [--no-guidance]
+hcc down
+
+# Local coordination without Web
+hcc up [--no-discover] [--no-guidance]
+
+# Peers and status
+hcc peers
+hcc status [--peer ID]
+hcc scan [--register]
+hcc prompt --peer ID [--kind codex|claude|shell|other] [--role ROLE]
+hcc join --peer ID [--kind codex|claude|shell|other] [--role ROLE]
+hcc env --peer ID
+hcc heartbeat [--peer ID] [--renew-locks --ttl 900]
+hcc run --peer ID --kind codex|claude|shell --role ROLE -- COMMAND [ARGS...]
+
+# Browser-controllable terminals
+hcc peer list
+hcc peer start PEER [--kind K] [--role R] [--cwd DIR] [--restart-env] -- COMMAND [ARGS...]
+hcc peer start PEER --kind codex --resume SESSION_ID [--restart-env]
+hcc peer start PEER --kind codex --last
+hcc peer start PEER --kind claude --resume SESSION_ID [--restart-env]
+hcc peer start PEER --kind claude --continue
+hcc peer attach PEER [--pane PANE] [--kind K] [--role R] [--cwd DIR]
+hcc peer stop PEER
+hcc inject PEER TEXT [--no-enter]
+
+# Messages
+hcc msg send [--from ID] [--to ID|all] --body TEXT [--task N] [--kind note|task|handoff]
+hcc msg inbox [--peer ID] [--wait SEC] [--all] [--limit N]
+hcc msg ack [--peer ID] --id N
+hcc ask PEER MESSAGE [--from ID] [--task N] [--inject]
+hcc broadcast MESSAGE [--from ID] [--task N] [--inject]
+
+# Tasks
+hcc task create --title TEXT [--body TEXT] [--from ID] [--to ID] [--priority N]
+hcc task list [--status S] [--peer ID] [--all]
+hcc task claim [--peer ID] --id N
+hcc task next [--peer ID]
+hcc task update [--peer ID] --id N --status running|review|blocked|done|abandoned [--summary TEXT] [--body TEXT] [--to ID]
+hcc task done [--peer ID] --id N --summary TEXT
+
+# Locks and handoffs
+hcc lock acquire [--peer ID] --resource PATH [--task N] [--ttl SEC] [--reason TEXT]
+hcc lock renew [--peer ID] --resource PATH [--ttl SEC]
+hcc lock release [--peer ID] --resource PATH [--force]
+hcc lock list [--all]
+hcc handoff create [--from ID] --summary TEXT [--task N] [--to ID] [--changed-files JSON_OR_CSV] [--tests TEXT] [--risks TEXT]
+hcc handoff list [--task N] [--limit N]
+hcc event tail [--limit N]
+hcc gc [--older-than DAYS] [--yes]
+```
+
+## Stable Peer Identity
+
+hello-cc tries to keep peer IDs stable across resumed sessions:
+
+| Launch pattern | Peer ID |
+|---|---|
+| `claude --resume abc12345...` | `claude-abc12345` |
+| `claude --session-id abc12345...` | `claude-abc12345` |
+| `claude --continue` | terminal-derived ID first, then hooks record real session metadata |
+| `claude --fork-session --resume abc12345...` | terminal-derived ID first, then hooks record new session metadata |
+| `codex resume abc12345...` | `codex-abc12345` |
+| `codex resume --last` | terminal-derived ID first, then discovery records real session metadata |
+| plain shell | `shell-<terminal>` |
+| manual `HCC_PEER=xxx` | uses `xxx` |
+
+Known resume IDs keep the same peer ID after restart. Launch modes that do not
+expose the real provider session ID before startup use a terminal-derived ID
+first, then record provider metadata after hooks or discovery run.
+
+## Typical Workflow
+
+Create a task:
+
+```bash
+hcc task create --title "Refactor router diagnostics" \
+  --body "Keep changes scoped." --priority 20
+```
+
+Claim and lock:
+
+```bash
+hcc task next
+hcc lock acquire --resource vllm/router --ttl 900 --reason "implement diagnostics"
+```
+
+Message or inject:
+
+```bash
+hcc msg send --to claude-a --body "Implementation is ready for review."
+hcc ask claude-a "Please review the current implementation." --inject
+hcc broadcast "Pause edits under vllm/router until this task finishes." --inject
+```
+
+Finish with a handoff:
+
+```bash
+hcc handoff create --to claude-a \
+  --summary "Implemented router diagnostics changes." \
+  --tests "pytest tests/router" \
+  --risks "Full benchmark not run"
+
+hcc task done --id 1 --summary "Done and handed off."
+hcc lock release --resource vllm/router
+```
+
+## Stack
+
+```text
+Node.js >= 24
+node:sqlite + SQLite WAL
+Node HTTP server
+ws WebSocket
+xterm.js
+tmux create/capture/send
+Claude Code hooks
+Codex hooks
+shell shim wrappers
+```
+
+A2A and MCP are not required for the core. A2A is better suited to remote agent
+interoperability, and MCP can be added later as a tool layer. Local multi-CLI
+coordination uses hooks + SQLite + tmux.
+
+## Testing
+
+```bash
+npm test
+```
+
+The regression creates a temporary project, temporary `HOME`, fake
+`claude`/`codex` binaries, a temporary runtime port, and temporary tmux
+sessions. It covers `hcc web` bootstrap, single-port multi-project
+registration, hooks/shims, SQLite coordination, tmux-backed `peer start`
+creation and restore, shim-launched tmux peers, tmux attach, WebSocket terminal
+streaming, terminal injection, runtime shutdown, package dry-run, and old-name
+scanning.
+
+## Architecture
+
+```text
+hcc CLI
+  ├── lib/discover.mjs    Claude/Codex session discovery
+  ├── lib/setup.mjs       hooks, shims, PATH installation
+  ├── bin/hcc.mjs         CLI, SQLite, web runtime, tmux control
+  └── .hello-cc/
+        ├── mesh.db       coordination state
+        ├── HCC.md        project guidance rules
+        ├── runtime.json  web runtime discovery file
+        └── web.log       web runtime log
+```
+
+## Environment Variables
+
+| Variable | Purpose |
+|---|---|
+| `HCC_PEER` | default peer identity |
+| `HCC_ROOT` | override project root |
+| `HCC_DB` | override database path |
+| `HCC_WEB_TOKEN` | optional token for web access |
+| `HCC_RUNTIME_URL` | direct runtime URL |
+| `HCC_NO_AUTO_INSTALL_TMUX=1` | disable tmux auto-install, mainly for tests |
+
+The `claude` / `codex` shims and `hcc peer start` create tmux-backed sessions
+from the environment of the **local terminal that launched them**, not from the
+older environment of the background web runtime. This lets you open a new
+terminal, export provider variables such as `ANTHROPIC_*` or
+`CLAUDE_CODE_*`, then run `claude` / `codex`.
+
+An already-running CLI process cannot have its environment changed in place by
+the operating system. The `claude` / `codex` shims call `hcc peer start` with
+`--restart-env`, so hello-cc records a launch environment fingerprint for the
+same resume/session peer. If you start that peer again from a new terminal and
+the environment changed, hello-cc automatically restarts the tmux session with
+the new environment when there are no attached tmux clients or Web clients. If
+the session is actively attached, hello-cc asks you to detach/close Web clients
+or run `hcc peer stop <peer>` before starting it again.
+
+When you call `hcc peer start` directly, add `--restart-env` if you want the
+same restart-on-environment-change behavior.
+
+The shims only manage interactive terminal sessions. Metadata and maintenance
+commands pass through to the real provider CLI, including `claude --help`,
+`claude --version`, `claude --print`, `claude --bare`, `claude --safe-mode`,
+`codex --help`, `codex --version`, and non-interactive Codex subcommands such as
+`codex exec`, `codex review`, `codex doctor`, and `codex mcp`. Interactive
+`claude`, `claude --resume ...`, `codex`, `codex resume ...`, and `codex fork
+...` are tmux-backed and visible in the Web console.
+
+---
+
+<p align="center">
+  <a href="https://star-history.com/#Dullne/hello-cc&Date">
+    <img src="https://api.star-history.com/svg?repos=Dullne/hello-cc&type=Date" width="600" alt="Star History Chart">
+  </a>
+</p>