cc-agent-messenger 0.1.0__tar.gz

cc_agent_messenger-0.1.0/.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# Default reviewer for all changes (single maintainer).
+*       @noboru2000

cc_agent_messenger-0.1.0/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,92 @@
+name: 🐞 Bug report
+description: Something doesn't work as documented
+labels: ["bug", "needs-triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for the report. Before filling this in:
+
+        - **Not a security issue?** Vulnerabilities go through a private
+          [Security Advisory](https://github.com/noboru2000/cc-agent-messenger/security/advisories/new),
+          not a public issue (see SECURITY.md).
+        - **Redact secrets.** Never paste Slack tokens (`xoxb-…`, `xapp-…`), IDs,
+          or anything from `.cc-agent-messenger/config.toml` into this issue.
+  - type: checkboxes
+    id: preflight
+    attributes:
+      label: Pre-submission checks
+      options:
+        - label: I searched existing issues and this isn't a duplicate.
+          required: true
+        - label: This is a bug, not a security vulnerability or a usage question.
+          required: true
+        - label: I have removed all tokens / secrets / private IDs from this report.
+          required: true
+  - type: input
+    id: version
+    attributes:
+      label: Version
+      description: Output of `cc-agent-messenger --version`.
+      placeholder: cc-agent-messenger 0.1.0
+    validations:
+      required: true
+  - type: dropdown
+    id: install
+    attributes:
+      label: How did you install it?
+      options:
+        - uv tool install (PyPI)
+        - pipx install (PyPI)
+        - pip install (PyPI)
+        - from git (uv tool install git+…)
+        - from source / editable
+    validations:
+      required: true
+  - type: dropdown
+    id: mode
+    attributes:
+      label: Agent / mode in use
+      options:
+        - Claude Code — live session (C0)
+        - Claude Code — headless (C1)
+        - Codex (C1)
+        - Copilot (C1)
+        - Not applicable / setup-only
+    validations:
+      required: true
+  - type: input
+    id: env
+    attributes:
+      label: OS + Python
+      description: e.g. macOS 15.5 / Python 3.12 (and WSL if applicable).
+      placeholder: macOS 15.5, Python 3.12
+    validations:
+      required: true
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened
+      description: What you did, what you expected, and what actually happened.
+    validations:
+      required: true
+  - type: textarea
+    id: repro
+    attributes:
+      label: Steps to reproduce
+      placeholder: |
+        1. cc-agent-messenger init
+        2. …
+        3. Send `@bot !status` from Slack
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant output (redacted)
+      description: >-
+        `cc-agent-messenger doctor` output and any daemon error lines. Double-check
+        there are no tokens or IDs before pasting — this will be rendered as code.
+      render: shell
+    validations:
+      required: false

cc_agent_messenger-0.1.0/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,14 @@
+# Force contributors through a template; route security + questions elsewhere.
+blank_issues_enabled: false
+contact_links:
+  - name: 🔐 Security vulnerability (do NOT open a public issue)
+    url: https://github.com/noboru2000/cc-agent-messenger/security/advisories/new
+    about: >-
+      This tool runs commands in response to Slack messages. Report security
+      issues privately via a GitHub Security Advisory (or email the maintainer).
+      See SECURITY.md.
+  - name: 💬 Questions & usage help
+    url: https://github.com/noboru2000/cc-agent-messenger/discussions
+    about: >-
+      Ask how-to / setup / usage questions in Discussions. The issue tracker is
+      for actionable bug reports and feature requests only.

cc_agent_messenger-0.1.0/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,61 @@
+name: ✨ Feature request
+description: Propose a change or new capability
+labels: ["enhancement", "needs-triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        This is a small, security-sensitive tool maintained by one person.
+        **Significant changes should start as a discussion** so we agree on the
+        approach before any PR. Please open or link a
+        [Discussion](https://github.com/noboru2000/cc-agent-messenger/discussions)
+        for non-trivial proposals.
+  - type: checkboxes
+    id: preflight
+    attributes:
+      label: Pre-submission checks
+      options:
+        - label: I searched existing issues / discussions and this isn't a duplicate.
+          required: true
+        - label: I understand that PRs for non-trivial changes should be discussed first.
+          required: true
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem / motivation
+      description: What are you trying to do, and why is it hard today?
+    validations:
+      required: true
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed solution
+      description: What would you like to see? Sketch the CLI / config / behavior.
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+    validations:
+      required: false
+  - type: dropdown
+    id: security-impact
+    attributes:
+      label: Does this touch the security model?
+      description: >-
+        e.g. authorization (NN4), kill switch, audit, token handling, the closed
+        command set, or running new commands. See SECURITY.md.
+      options:
+        - "No — UX / docs / non-security change"
+        - "Maybe — not sure, needs discussion"
+        - "Yes — it changes the security model"
+    validations:
+      required: true
+  - type: checkboxes
+    id: contribution
+    attributes:
+      label: Contribution
+      options:
+        - label: I'd be willing to open a PR after the approach is agreed.
+          required: false

cc_agent_messenger-0.1.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,38 @@
+<!--
+Thanks for contributing! This is a small, security-sensitive tool.
+For anything non-trivial, please open an issue / discussion FIRST so the
+approach is agreed before review. PRs are squash-merged.
+-->
+
+## Summary
+
+<!-- What does this change and why? Keep PRs small and reviewable. -->
+
+## Linked issue / discussion
+
+<!-- Required for non-trivial changes. e.g. Closes #123 -->
+Closes #
+
+## Type
+
+<!-- Conventional Commits — the PR title should match (e.g. `fix: …`, `feat: …`). -->
+- [ ] `fix` — bug fix
+- [ ] `feat` — new feature
+- [ ] `docs` — documentation only
+- [ ] `refactor` / `test` / `chore` — internal change
+
+## Security impact
+
+<!-- Does this touch authorization (NN4), kill switch, audit, token handling,
+     the closed command set, or run new commands? If yes, explain. -->
+- [ ] This change does **not** weaken the security model (SECURITY.md).
+
+## Checklist
+
+- [ ] The PR title follows Conventional Commits.
+- [ ] For a non-trivial change, it was discussed in an issue / discussion first.
+- [ ] Tests added or updated for every behavior change.
+- [ ] `uv run pytest` passes locally.
+- [ ] No secrets, tokens, or host-specific paths are committed.
+- [ ] Docs updated (README / SETUP / USAGE / CHANGELOG) where relevant.
+- [ ] The change is small and focused (split large changes into multiple PRs).

cc_agent_messenger-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,23 @@
+name: CI
+
+on:
+  push:
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Sync
+        run: uv sync --extra dev
+      - name: Test
+        run: uv run pytest -q

cc_agent_messenger-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,48 @@
+name: Publish to PyPI
+
+# Publishes to PyPI when a GitHub Release is published.
+#
+# Uses PyPI Trusted Publishing (OIDC) — no API token stored. Before the first
+# run, configure a Trusted Publisher on PyPI:
+#   pypi.org → (your project, or "pending publisher" for a new name) → Publishing →
+#   Add a GitHub publisher:
+#     owner:        noboru2000
+#     repository:   cc-agent-messenger
+#     workflow:     release.yml
+#     environment:  pypi
+# Optionally create a GitHub environment named "pypi" with protection rules.
+# To dry-run first, point at TestPyPI (configure a publisher on test.pypi.org and
+# set `repository-url: https://test.pypi.org/legacy/` on the publish step).
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  contents: read
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/cc-agent-messenger
+    permissions:
+      id-token: write # required for Trusted Publishing (OIDC)
+    steps:
+      - uses: actions/checkout@v4
+      - name: Verify tag matches package version
+        run: |
+          TAG="${GITHUB_REF_NAME#v}"
+          VER="$(grep -m1 '^version' pyproject.toml | sed -E 's/.*"([^"]+)".*/\1/')"
+          echo "release tag: ${GITHUB_REF_NAME} (-> ${TAG}); pyproject version: ${VER}"
+          if [ "$TAG" != "$VER" ]; then
+            echo "::error::release tag '${TAG}' does not match pyproject version '${VER}'"
+            exit 1
+          fi
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+      - name: Build sdist + wheel
+        run: uv build
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

cc_agent_messenger-0.1.0/.gitignore

@@ -0,0 +1,29 @@
+# Python
+.venv/
+venv/
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+build/
+dist/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+
+# Secrets & local runtime (never commit) ------------------------------------
+.cc-agent-messenger/
+tmp/
+*.sock
+.env
+.env.*
+*.token
+*.secret
+
+# Claude Code local (per-user) settings — keep skills, drop local overrides.
+.claude/settings.local.json
+
+# OS / editor
+.DS_Store
+*.swp

cc_agent_messenger-0.1.0/CHANGELOG.md

@@ -0,0 +1,40 @@
+# Changelog
+
+All notable changes to this project are documented here. The format is based on
+[Keep a Changelog](https://keepachangelog.com/), and this project adheres to
+semantic versioning.
+
+## [Unreleased]
+
+## [0.1.0] - 2026-06-20
+
+First public release.
+
+### Added
+- Resident Slack bot daemon (Bolt + Socket Mode) with a single egress chokepoint:
+  kill switch → destination authorization → outbound filter/split → audit → post.
+  The Slack bot token stays inside the daemon only.
+- Unix-domain-socket send API + unified CLI: `init`, `uninstall`, `daemon`, `send`,
+  `ping`, `status`, `stop`, `kill`, `doctor`, plus `--version`.
+- **Explicit command prefix** (`command_prefix`, default `!`): `@bot !status`,
+  `!select 2`, `!doctor`, … — deterministic, exactly-resolved commands needing
+  **no Slack slash registration** (and dodging reserved-word slashes like
+  `/status`). Configurable (`!` / `$` / `^`). Free-text `@mention`, Block Kit
+  buttons, and emoji reactions are also supported; native `/slash` commands are
+  opt-in (the shipped `slash_map` is empty).
+- **Upgrade-safe `init`**: re-running refreshes the skill while preserving
+  `config.toml` (tokens/owner/channel) and `profile.json`; `--refresh-profile`
+  regenerates the profile (backing the old one up to `.bak`) with a migration hint.
+  See SETUP.md §10 (Update / upgrade).
+- Claude Code skill (C0 live-session monitor mode), config/profile templates, and
+  the `init` scaffolder; `uninstall` (with `--purge`) reverses it.
+- Multi-agent C1 skeleton (`AgentRunner`, `Router`) — Claude / Codex / Copilot C1
+  PoC-verified; daemon wiring is a later increment.
+- Author/contact/copyright metadata: pyproject author + maintainer email,
+  `__author__`/`__email__`/`__license__`/`__copyright__`, per-file SPDX headers.
+- Project hygiene: issue/PR templates + contribution policy (CONTRIBUTING),
+  security policy (SECURITY), CI across Python 3.11–3.13, and a PyPI
+  Trusted-Publishing release workflow.
+
+[Unreleased]: https://github.com/noboru2000/cc-agent-messenger/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/noboru2000/cc-agent-messenger/releases/tag/v0.1.0

cc_agent_messenger-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,74 @@
+# Contributing
+
+Thanks for your interest. This is a small, **security-sensitive** tool maintained
+by one person, so the workflow favors agreeing on an approach before code lands.
+Please keep changes small and reviewable, and add or update tests for every
+behavior change.
+
+## Reporting bugs
+
+Open a **Bug report** issue (the blank issue option is disabled — pick a template).
+Include the version (`cc-agent-messenger --version`), install method, OS/Python,
+and steps to reproduce.
+
+- **Security vulnerabilities** do **not** go in public issues. Report them
+  privately via a [Security Advisory](https://github.com/noboru2000/cc-agent-messenger/security/advisories/new)
+  or email the maintainer — see [SECURITY.md](SECURITY.md).
+- **Redact secrets.** Never paste Slack tokens (`xoxb-…`, `xapp-…`), IDs, or
+  `.cc-agent-messenger/config.toml` contents.
+
+## Questions & usage help
+
+Use [Discussions](https://github.com/noboru2000/cc-agent-messenger/discussions),
+not the issue tracker — the tracker is for actionable bugs and feature requests.
+
+## Proposing changes (pull requests)
+
+1. **Discuss first.** For anything non-trivial, open a **Feature request** issue or
+   a Discussion so we agree on the approach before you invest in a PR. Trivial
+   fixes (typos, small doc fixes, obvious bugs) can go straight to a PR.
+2. **Branch & PR.** Work on a branch; open a PR against `main` and fill in the PR
+   template. Link the issue/discussion (`Closes #NN`).
+3. **Keep it small and focused.** Split large changes into multiple PRs.
+4. **Tests + CI.** Add/adjust tests; `uv run pytest` must pass (CI runs it).
+5. **Review & merge.** The maintainer reviews; PRs are **squash-merged**, so the PR
+   title becomes the commit — make it a good Conventional Commit (below).
+6. By contributing you agree your contribution is licensed under the project's
+   [MIT License](LICENSE).
+
+## Development setup
+
+    git clone https://github.com/noboru2000/cc-agent-messenger
+    cd cc-agent-messenger
+    uv sync --extra dev
+    uv run pytest
+
+The test suite runs offline (Slack is mocked). You can also run it without `uv`:
+
+    PYTHONPATH=src python -m unittest discover -s tests
+
+## Commit messages
+
+Use [Conventional Commits](https://www.conventionalcommits.org/): a `type(scope):`
+prefix and an imperative summary. Common types: `feat`, `fix`, `docs`, `refactor`,
+`test`, `chore`, `ci`. Examples:
+
+    feat(commands): add the `!` command prefix
+    fix(ingress): avoid double-ingestion of bot-mentioned thread replies
+    docs(setup): add the update/upgrade section
+
+## Code guidelines
+
+- Type-annotate public functions; avoid OS-specific assumptions and hard-coded
+  machine paths (use config).
+- Never commit secrets or host-specific values — keep them under
+  `.cc-agent-messenger/` (gitignored).
+- Keep the security model intact (see [SECURITY.md](SECURITY.md)): single
+  operator, authorization, kill switch, audit, local-only token handling.
+- The inbound command set is a **closed allowlist**; destructive/irreversible
+  actions stay behind explicit in-Slack approval (NN5).
+
+## Labels (maintainer reference)
+
+`bug`, `enhancement`, `docs`, `question`, `security`, `needs-triage`,
+`good first issue`, `wontfix`, `duplicate`.

cc_agent_messenger-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Noboru Harada
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

cc_agent_messenger-0.1.0/PKG-INFO

@@ -0,0 +1,125 @@
+Metadata-Version: 2.4
+Name: cc-agent-messenger
+Version: 0.1.0
+Summary: Slack message-turn bridge to AI coding agents (Claude Code / Codex / Copilot) running on your Mac
+Project-URL: Homepage, https://github.com/noboru2000/cc-agent-messenger
+Project-URL: Issues, https://github.com/noboru2000/cc-agent-messenger/issues
+Author-email: Noboru Harada <noboru@ieee.org>
+Maintainer-email: Noboru Harada <noboru@ieee.org>
+License: MIT
+License-File: LICENSE
+Keywords: ai-agent,bot,claude-code,codex,copilot,slack,socket-mode
+Classifier: Development Status :: 3 - Alpha
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Topic :: Communications :: Chat
+Requires-Python: >=3.11
+Requires-Dist: slack-bolt>=1.18
+Requires-Dist: slack-sdk>=3.27
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == 'dev'
+Description-Content-Type: text/markdown
+
+<p align="center">
+  <img src="docs/images/logo.png" alt="cc-agent-messenger logo" width="160">
+</p>
+
+# cc-agent-messenger
+
+**English** | [日本語](README.ja.md)
+
+[![PyPI](https://img.shields.io/pypi/v/cc-agent-messenger.svg)](https://pypi.org/project/cc-agent-messenger/)
+[![Python](https://img.shields.io/pypi/pyversions/cc-agent-messenger.svg)](https://pypi.org/project/cc-agent-messenger/)
+[![CI](https://github.com/noboru2000/cc-agent-messenger/actions/workflows/ci.yml/badge.svg)](https://github.com/noboru2000/cc-agent-messenger/actions/workflows/ci.yml)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
+
+Reply to your AI coding agents from **Slack on your phone**, while they keep
+working in VS Code on your Mac. A small resident bot bridges a Slack channel to
+the live Claude Code session (and, headlessly, to Codex / Copilot), so you can
+ask for status, choose the next step, or get pinged when a long job finishes —
+as **complete message turns**, not live terminal mirroring.
+
+> ⚠️ **Security & responsibility.** This tool runs commands in response to Slack
+> messages (RCE-adjacent). It is built for a **single trusted operator** on a
+> trusted machine. Enabling hands-free auto-reply grants auto-execution of the
+> reply command — a conscious risk you accept. No warranty; use at your own risk.
+> See [SECURITY.md](SECURITY.md).
+
+```text
+iPhone Slack ──(@bot !status)──► resident bot (Bolt + Socket Mode)
+                                       │ authorize (NN4) + match command
+                                       ▼
+                               tmp/.slack_message  ◄── tail -f Monitor (live Claude session)
+          iPhone push ◄── bot chat.postMessage ◄── cc-agent-messenger send (Unix-socket send API)
+```
+
+## What it does
+
+- **Inbound:** a Slack message in your private channel is authorized and appended
+  to a local file; your live Claude Code session (watching it with `tail -f`)
+  wakes, interprets the command, and replies.
+- **Outbound:** the reply is posted by the project's own bot, @-mentioning you, so
+  your phone gets a push.
+- **Agents:** Claude Code via the **live session (C0)**; Codex and Copilot via
+  **headless CLIs (C1)**. (C1 is also available for Claude.)
+
+## Requirements
+
+- macOS or Linux/WSL, VS Code + the Claude Code extension, Python ≥ 3.11, `uv`.
+- A Slack workspace + one **private** channel, and a Slack app (Socket Mode).
+- For Codex/Copilot: their own CLIs installed + authenticated (`codex`,
+  `@github/copilot`). Claude via C0 needs no extra CLI.
+
+## Install
+
+    uv tool install cc-agent-messenger
+    # or from source:
+    uv tool install git+https://github.com/noboru2000/cc-agent-messenger
+
+## Quickstart
+
+    cd your-project
+    cc-agent-messenger init          # scaffolds the skill, config template, gitignore, allowlist
+    # 1) create a Slack app (Socket Mode + scopes + Event Subscriptions); see docs/SETUP.md
+    # 2) fill .cc-agent-messenger/config.toml with your tokens + channel id
+    cc-agent-messenger daemon        # run the resident bot
+
+    # verify the return path:
+    cc-agent-messenger ping          # -> {"status":"alive"}
+    cc-agent-messenger send --text "test"   # -> posts to your channel; phone gets a push
+
+Then, in your VS Code Claude Code session, invoke the **`cc-agent-messenger`** skill
+to start watching the channel and replying. Add the printed allow-rule to
+`.claude/settings.json` to make replies hands-free.
+
+## Commands
+
+`cc-agent-messenger <init | uninstall | daemon | send | ping | status | stop | kill on|off | doctor>`
+— see `cc-agent-messenger --help`. From Slack, `@bot` the bot with either an
+explicit command — `!status`, `!options`, `!select 2`, `!continue`, `!doctor`,
+`!help` (a leading `!` is deterministic and needs no Slack slash registration) —
+or plain words (`状況は?`, `status`). Full reference in
+[docs/USAGE.md](docs/USAGE.md).
+
+## Limitations
+
+- **Session-bound:** the live (C0) bridge works only while VS Code and the Mac are
+  awake and the skill's monitor is armed. It is not a 24/7 service.
+- Copilot/Codex replies come from a **headless CLI turn**, separate from their
+  VS Code GUI panels.
+
+## Docs
+
+- [docs/SETUP.md](docs/SETUP.md) — Slack app creation, invite, config, run, E2E,
+  troubleshooting.
+- [docs/USAGE.md](docs/USAGE.md) — Slack command reference (`!status`, `!options`,
+  …), keywords, and expected behavior once it is running.
+- [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md) — the C0 loop, the egress
+  chokepoint, the four input surfaces, the security model.
+
+## License & author
+
+[MIT](LICENSE) © 2026 Noboru Harada.
+
+**Author / maintainer:** Noboru Harada &lt;noboru@ieee.org&gt;. Security reports:
+see [SECURITY.md](SECURITY.md). Bugs / features: [open an issue](https://github.com/noboru2000/cc-agent-messenger/issues).

cc_agent_messenger-0.1.0/README.ja.md

@@ -0,0 +1,96 @@
+<p align="center">
+  <img src="docs/images/logo.png" alt="cc-agent-messenger logo" width="160">
+</p>
+
+# cc-agent-messenger
+
+[English](README.md) | **日本語**
+
+[![PyPI](https://img.shields.io/pypi/v/cc-agent-messenger.svg)](https://pypi.org/project/cc-agent-messenger/)
+[![Python](https://img.shields.io/pypi/pyversions/cc-agent-messenger.svg)](https://pypi.org/project/cc-agent-messenger/)
+[![CI](https://github.com/noboru2000/cc-agent-messenger/actions/workflows/ci.yml/badge.svg)](https://github.com/noboru2000/cc-agent-messenger/actions/workflows/ci.yml)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
+
+Mac の VS Code で AI コーディングエージェントが作業を続けている間に、**iPhone の
+Slack** から状況確認・次の選択・完了通知などをやり取りできるツールです。常駐 bot が
+Slack チャネルと**ライブの Claude Code セッション**(および Codex / Copilot のヘッド
+レス CLI)を橋渡しします。**完結したメッセージ単位**のやり取りで、ターミナルのライブ
+ミラーリングではありません。
+
+> ⚠️ **セキュリティと自己責任。** 本ツールは Slack メッセージに応じてコマンドを実行
+> します(RCE 隣接)。**単一の信頼できるオペレータ**が信頼できるマシンで使う前提です。
+> ハンズフリー自動返信を有効化すると、返信コマンドの自動実行を許可することになります
+> (意識的に受け入れるリスク)。無保証・自己責任。[SECURITY.md](SECURITY.md) 参照。
+
+```text
+iPhone Slack ──(@bot / /status)──► 常駐 bot (Bolt + Socket Mode)
+                                       │ 認可(NN4)+ コマンド照合
+                                       ▼
+                               tmp/.slack_message  ◄── tail -f Monitor(ライブ Claude セッション)
+          iPhone プッシュ ◄── bot chat.postMessage ◄── cc-agent-messenger send(Unix socket 送信 API)
+```
+
+## 何ができるか
+
+- **受信:** プライベートチャネルのメッセージを認可しローカルファイルに追記。`tail -f`
+  で監視中のライブ Claude Code セッションが起床し、コマンドを解釈して返信。
+- **送信:** 返信は**自前 bot** があなたを `@mention` して投稿 → スマホにプッシュ。
+- **エージェント:** Claude Code は**ライブセッション(C0)**、Codex/Copilot は**ヘッド
+  レス CLI(C1)**。Claude も C1 可。
+
+## 必要環境
+
+- macOS または Linux/WSL、VS Code + Claude Code 拡張、Python ≥ 3.11、`uv`。
+- Slack ワークスペース + あなた専用の**プライベートチャネル**、Socket Mode の Slack アプリ。
+- Codex/Copilot を使う場合は各 CLI の導入+認証(`codex`、`@github/copilot`)。Claude の
+  C0 は追加 CLI 不要。
+
+## インストール
+
+    uv tool install cc-agent-messenger
+    # ソースから:
+    uv tool install git+https://github.com/noboru2000/cc-agent-messenger
+
+## クイックスタート
+
+    cd your-project
+    cc-agent-messenger init          # skill / 設定テンプレ / .gitignore / allowlist を配置
+    # 1) Slack アプリ作成(Socket Mode + スコープ + Event Subscriptions);docs/SETUP.md
+    # 2) .cc-agent-messenger/config.toml にトークン + チャンネル ID を記入
+    cc-agent-messenger daemon        # 常駐 bot 起動
+
+    cc-agent-messenger ping          # -> {"status":"alive"}
+    cc-agent-messenger send --text "テスト"   # -> チャネルに投稿、スマホにプッシュ
+
+その後、VS Code の Claude Code セッションで **`cc-agent-messenger`** スキルを起動して
+待ち受け開始。`init` が表示する allow ルールを `.claude/settings.json` に貼ると
+ハンズフリーになります。
+
+## コマンド
+
+`cc-agent-messenger <init | uninstall | daemon | send | ping | status | stop | kill on|off | doctor>`
+— 詳細は `cc-agent-messenger --help`。Slack からは `/help`、`/status`、`/options`、
+`/continue`、`/doctor`、または `@bot <メッセージ>` — 全コマンドは
+[docs/USAGE.md](docs/USAGE.md) を参照。
+
+## 制限
+
+- **セッション束縛:** ライブ(C0)ブリッジは VS Code と Mac が起きていてスキルの監視が
+  動いている間のみ。24/7 サービスではありません。
+- Copilot/Codex の返信は**ヘッドレス CLI ターン**で、VS Code の GUI パネルとは別文脈です。
+
+## ドキュメント
+
+- [docs/SETUP.md](docs/SETUP.md) — Slack アプリ作成・招待・設定・起動・E2E・トラブルシュート。
+- [docs/USAGE.ja.md](docs/USAGE.ja.md) — Slack コマンドリファレンス(`/help`・`/status` 等)・
+  キーワード・起動後の期待動作。
+- [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md) — C0 ループ・egress chokepoint・4入力面・
+  セキュリティモデル。
+
+## ライセンス・作者
+
+[MIT](LICENSE) © 2026 Noboru Harada。
+
+**作者・メンテナ:** Noboru Harada &lt;noboru@ieee.org&gt;。脆弱性報告は
+[SECURITY.md](SECURITY.md)、不具合・要望は
+[Issue](https://github.com/noboru2000/cc-agent-messenger/issues) へ。