ai-agent-bridge 0.1.0__tar.gz

ai_agent_bridge-0.1.0/.dockerignore

@@ -0,0 +1,7 @@
+.git
+.venv
+.env
+.pytest_cache
+__pycache__
+*.pyc
+sessions.json

ai_agent_bridge-0.1.0/.env.example

@@ -0,0 +1,23 @@
+# Slack Bot Token (xoxb-...)
+SLACK_BOT_TOKEN=
+
+# Slack App-Level Token for Socket Mode (xapp-...)
+SLACK_APP_TOKEN=
+
+# Anthropic API Key (required for Docker / non-interactive environments)
+ANTHROPIC_API_KEY=
+
+# Directory where Claude Code will operate
+CLAUDE_WORK_DIR=.
+
+# Claude Code permission mode: acceptEdits, dangerously-skip-permissions, default, plan
+CLAUDE_PERMISSION_MODE=acceptEdits
+
+# Path to session store JSON file
+SESSION_STORE_PATH=./sessions.json
+
+# Session TTL in hours (sessions inactive longer than this are expired)
+SESSION_TTL_HOURS=72
+
+# Timeout for a single Claude invocation in seconds
+CLAUDE_TIMEOUT_SECONDS=300

ai_agent_bridge-0.1.0/.gitignore

@@ -0,0 +1,210 @@
+# Agent Bridge runtime data
+sessions.json
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+#poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+#pdm.lock
+#pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+#pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# Abstra
+# Abstra is an AI-powered process automation framework.
+# Ignore directories containing user credentials, local state, and settings.
+# Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#  Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#  that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#  and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#  you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Cursor
+#  Cursor is an AI-powered code editor. `.cursorignore` specifies files/directories to
+#  exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
+#  refer to https://docs.cursor.com/context/ignore-files
+.cursorignore
+.cursorindexingignore
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/

ai_agent_bridge-0.1.0/Dockerfile

@@ -0,0 +1,38 @@
+FROM python:3.12-slim
+
+# Install Node.js (required for Claude Code CLI)
+RUN apt-get update && \
+    apt-get install -y --no-install-recommends curl git && \
+    curl -fsSL https://deb.nodesource.com/setup_22.x | bash - && \
+    apt-get install -y --no-install-recommends nodejs && \
+    apt-get clean && rm -rf /var/lib/apt/lists/*
+
+# Install Claude Code CLI globally
+RUN npm install -g @anthropic-ai/claude-code
+
+# Install uv
+COPY --from=ghcr.io/astral-sh/uv:latest /uv /uvx /bin/
+
+# Set up workspace
+WORKDIR /app
+
+# Install dependencies first (cache layer)
+COPY pyproject.toml uv.lock ./
+RUN uv sync --frozen --no-dev --no-install-project
+
+# Copy source code (tests excluded from production image)
+COPY src/ src/
+RUN uv sync --frozen --no-dev
+
+# Claude Code work directory (mount your project here)
+RUN mkdir -p /workspace
+VOLUME /workspace
+
+# Session store persistence
+VOLUME /app/data
+
+ENV CLAUDE_WORK_DIR=/workspace \
+    SESSION_STORE_PATH=/app/data/sessions.json \
+    CLAUDE_PERMISSION_MODE=acceptEdits
+
+CMD ["uv", "run", "agent-bridge"]

ai_agent_bridge-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 htkuan
+
+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.

ai_agent_bridge-0.1.0/PKG-INFO

@@ -0,0 +1,247 @@
+Metadata-Version: 2.4
+Name: ai-agent-bridge
+Version: 0.1.0
+Summary: Modular bridge between chat platforms and AI agents
+Project-URL: Repository, https://github.com/htkuan/agent-bridge
+Author: htkuan
+License-Expression: MIT
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Communications :: Chat
+Classifier: Topic :: Software Development :: Libraries :: Application Frameworks
+Requires-Python: >=3.12
+Requires-Dist: python-dotenv>=1.0.0
+Provides-Extra: all
+Requires-Dist: aiohttp>=3.9.0; extra == 'all'
+Requires-Dist: slack-bolt>=1.21.0; extra == 'all'
+Provides-Extra: slack
+Requires-Dist: aiohttp>=3.9.0; extra == 'slack'
+Requires-Dist: slack-bolt>=1.21.0; extra == 'slack'
+Description-Content-Type: text/markdown
+
+# Agent Bridge
+
+Modular bridge service that connects **chat platforms** to **AI agents**. The architecture cleanly separates platform concerns from agent concerns, making it easy to add new platforms or agents.
+
+Currently supports **Slack** as the chat platform and **Claude Code** as the AI agent backend.
+
+## Architecture
+
+```
+┌─────────────────────────┐
+│  Platform (Slack)       │  Defines session semantics (thread = session)
+│  platforms/slack/       │  Manages per-session locking & flow control
+│  - adapter.py           │  Renders agent events (stream updates, final reply)
+│  - config.py            │
+└──────────┬──────────────┘
+           │ session_key, text, context
+           ▼
+┌─────────────────────────┐
+│  Bridge                 │  Pure routing — no platform or agent knowledge
+│  bridge.py              │  session_key → session_id (via SessionManager)
+│  session.py             │  Forwards to agent, yields BridgeEvents back
+│  events.py              │  TextDelta | StatusUpdate | Completion
+│  protocols.py           │  AgentController + PlatformAdapter protocols
+└──────────┬──────────────┘
+           │ session_id, prompt, is_new, context
+           ▼
+┌─────────────────────────┐
+│  Agent (Claude Code)    │  Purely invoked: load session + input → output
+│  agents/claude/         │  Translates Claude stream-json → BridgeEvents
+│  - controller.py        │  Does not define sessions or care about rendering
+│  - events.py            │
+│  - config.py            │
+└─────────────────────────┘
+```
+
+### Design Principles
+
+**Platform defines session semantics.** A Slack thread is a session. A Discord channel might be a session. This is platform knowledge — the bridge and agent don't care how sessions are defined.
+
+**Agent is purely invoked.** It receives `(session_id, prompt, is_new, context)`, loads the session, executes, and yields events. It doesn't know where the session came from or how results will be rendered.
+
+**Bridge is pure routing.** It resolves session keys to session IDs and forwards requests/events. No platform-specific or agent-specific logic.
+
+### Generic Event Model
+
+Platforms consume three event types — the common language between any agent and any platform:
+
+| Event | Description |
+|-------|-------------|
+| `TextDelta` | Incremental text from the agent |
+| `StatusUpdate` | Agent is performing an action (tool use, thinking, etc.) |
+| `Completion` | Agent finished responding (with cost, duration, error status) |
+
+Agent-internal events (init, thinking, tool results) are translated to these generic types within each agent module.
+
+### Data Flow
+
+1. User sends a message in Slack (via `@mention` in channel or direct message)
+2. **Slack Adapter** receives the event, constructs a session key (`slack:{channel}:{thread_ts}`)
+3. **Slack Adapter** acquires per-session lock (prevents concurrent processing)
+4. **Bridge** resolves session key → session ID via **SessionManager**
+5. **Agent (Claude Controller)** spawns `claude -p` with the session, yields `BridgeEvent`s
+6. **Slack Adapter** renders events as real-time message updates (throttled to avoid rate limits)
+
+### Session Management
+
+- Each Slack thread maps to one agent session (defined by the platform)
+- The bridge stores the mapping: `session_key → {session_id, created_at, last_used}`
+- Mappings are persisted in a JSON file
+- Sessions have a configurable TTL (default 72 hours) — expired sessions are automatically purged
+
+## Tech Stack
+
+| Component | Choice | Reason |
+|-----------|--------|--------|
+| Language | Python 3.12+ | Type union syntax (`X \| Y`), `match` statements, modern asyncio |
+| Package manager | uv | Fast, supports pyproject.toml natively |
+| Slack SDK | [slack-bolt](https://github.com/slackapi/bolt-python) | Official Slack SDK, async support, Socket Mode |
+| Async HTTP | aiohttp | Required by slack-bolt for async Socket Mode |
+| Env config | python-dotenv | Load `.env` files |
+| Testing | pytest + pytest-asyncio | Standard Python testing |
+| Claude CLI | `claude -p` with `--output-format stream-json` | Non-interactive mode with real-time streaming |
+
+## Project Structure
+
+```
+agent-bridge/
+├── pyproject.toml
+├── .env.example
+├── src/
+│   └── agent_bridge/
+│       ├── __init__.py             # Entry point: wires platform + bridge + agent
+│       ├── config.py               # BridgeConfig (session store, TTL)
+│       ├── bridge.py               # Pure routing: session resolve → agent call
+│       ├── events.py               # TextDelta, StatusUpdate, Completion
+│       ├── session.py              # SessionManager (key → session_id mapping)
+│       ├── protocols.py            # AgentController + PlatformAdapter protocols
+│       ├── agents/
+│       │   └── claude/
+│       │       ├── config.py       # ClaudeConfig (work_dir, permissions, timeout)
+│       │       ├── controller.py   # Claude Code subprocess controller
+│       │       └── events.py       # Claude stream-json parser + BridgeEvent converter
+│       └── platforms/
+│           └── slack/
+│               ├── config.py       # SlackConfig (bot_token, app_token)
+│               └── adapter.py      # Slack adapter (session def, locking, rendering)
+└── tests/
+    ├── test_events.py              # Claude event parsing + BridgeEvent conversion
+    └── test_session.py             # Session manager tests
+```
+
+## Setup
+
+### Prerequisites
+
+- Python 3.12+
+- [uv](https://docs.astral.sh/uv/)
+- [Claude Code CLI](https://docs.anthropic.com/en/docs/claude-code) installed and authenticated
+
+### Install
+
+```bash
+git clone <repo-url>
+cd agent-bridge
+uv sync
+```
+
+### Slack App Configuration
+
+1. Create a Slack App at [api.slack.com/apps](https://api.slack.com/apps)
+2. Enable **Socket Mode** and generate an App-Level Token (`xapp-...`)
+3. Add the following **Bot Token Scopes** under OAuth & Permissions:
+   - `app_mentions:read` — receive @mention events
+   - `chat:write` — send and update messages
+   - `im:history` — read DM messages
+   - `im:read` — access DM channels
+4. Subscribe to these **Events** under Event Subscriptions:
+   - `app_mention`
+   - `message.im`
+5. Install the app to your workspace and copy the **Bot User OAuth Token** (`xoxb-...`)
+
+### Environment Variables
+
+```bash
+cp .env.example .env
+```
+
+Edit `.env`:
+
+```bash
+SLACK_BOT_TOKEN=xoxb-your-bot-token
+SLACK_APP_TOKEN=xapp-your-app-level-token
+CLAUDE_WORK_DIR=/path/to/your/project
+CLAUDE_PERMISSION_MODE=acceptEdits
+SESSION_STORE_PATH=./sessions.json
+SESSION_TTL_HOURS=72
+```
+
+| Variable | Required | Default | Description |
+|----------|----------|---------|-------------|
+| `SLACK_BOT_TOKEN` | Yes | — | Slack Bot User OAuth Token |
+| `SLACK_APP_TOKEN` | Yes | — | Slack App-Level Token (Socket Mode) |
+| `CLAUDE_WORK_DIR` | No | `.` | Working directory for Claude Code |
+| `CLAUDE_PERMISSION_MODE` | No | `acceptEdits` | Claude permission mode |
+| `SESSION_STORE_PATH` | No | `./sessions.json` | Path to session mapping file |
+| `SESSION_TTL_HOURS` | No | `72` | Session TTL in hours |
+
+### Run (Local)
+
+```bash
+uv run agent-bridge
+```
+
+### Run (Docker)
+
+```bash
+cp .env.example .env
+# Edit .env with your tokens (including ANTHROPIC_API_KEY for Docker)
+
+docker compose up --build
+```
+
+### Test
+
+```bash
+uv run pytest tests/ -v
+```
+
+## Usage
+
+- **Channel**: Mention the bot — `@AgentBridge help me refactor this function`
+- **DM**: Send a direct message — the bot responds in the same conversation
+- **Thread continuity**: Reply in the same Slack thread to continue the agent session
+
+## Extending
+
+### Adding a new agent
+
+Create `agents/<name>/` with `config.py`, `controller.py`, `events.py`. Implement the `AgentController` protocol — your `run()` method yields `BridgeEvent`s. Wire it up in `__init__.py`.
+
+### Adding a new platform
+
+Create `platforms/<name>/` with `config.py`, `adapter.py`. Define your own session key logic (e.g., `discord:{guild}:{channel}`), manage per-session locking, consume `BridgeEvent`s from `bridge.handle_message()`. Wire it up in `__init__.py`.
+
+Neither change requires modifying the bridge, the other agent, or the other platform.
+
+## Design Decisions
+
+### One-shot per message (vs. long-running process)
+
+Each user message spawns a new `claude -p` process that exits after completion. Session continuity is handled by Claude Code's built-in `--resume` flag.
+
+**Why**: Simpler process lifecycle, no idle resource consumption, graceful handling of crashes.
+
+### Per-session locking (platform-owned)
+
+An `asyncio.Lock` per session key prevents concurrent agent processes for the same session. This is managed by the platform adapter, not the bridge, because locking strategy may vary by platform.
+
+### Throttled Slack updates
+
+Slack message updates are throttled to 1.5-second intervals during streaming.
+
+**Why**: Slack's API rate limits are ~1 request/second per method.