python-slack-agents 0.6.2__tar.gz → 0.7.0__tar.gz

{python_slack_agents-0.6.2 → python_slack_agents-0.7.0}/.gitignore

@@ -1,6 +1,9 @@
 # Worktrees
 .worktrees/
 
+# Local implementation plans (working docs)
+.plans/
+
 # Python
 __pycache__/
 *.py[cod]

{python_slack_agents-0.6.2 → python_slack_agents-0.7.0}/AGENTS.md

@@ -102,12 +102,14 @@ The project includes AI-agent-friendly documentation following the llms.txt conv
 
 ## Releasing
 
-1. Update `version` in `pyproject.toml`
-2. Update `CHANGELOG.md` with the new version and changes
-3. Run `python3 src/slack_agents/scripts/generate_llms_full.py` to regenerate `llms-full.txt`
-4. Commit and push to `main`
-5. Create a GitHub Release (which creates a git tag)
-6. The `publish.yml` workflow automatically builds and publishes to PyPI via trusted publishing
+`CHANGELOG.md` is the gate. Entries accumulate under `## [Unreleased]` as PRs land; releasing just renames that heading to the new version. If prior releases skipped this step (as 0.6.3 did), backfill those versions first so the changelog is honest about history.
+
+1. **CHANGELOG.md** — rename `## [Unreleased]` to `## [X.Y.Z] - YYYY-MM-DD` with today's date, and add a fresh empty `## [Unreleased]` above it.
+2. **pyproject.toml** — bump `version` to `X.Y.Z`.
+3. **llms-full.txt** — regenerate: `python3 src/slack_agents/scripts/generate_llms_full.py`.
+4. Commit and push to `main`.
+5. Create a GitHub Release (which creates a git tag).
+6. The `publish.yml` workflow automatically builds and publishes to PyPI via trusted publishing.
 
 The PyPI deployment requires manual approval in the GitHub Actions UI. Do NOT publish to PyPI manually — the GitHub Release trigger handles it.
 

{python_slack_agents-0.6.2 → python_slack_agents-0.7.0}/CHANGELOG.md

@@ -6,6 +6,45 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/), and this
 
 ## [Unreleased]
 
+## [0.7.0] - 2026-04-14
+
+### Changed
+
+- **Overlays are no longer Python packages.** `slack-agents init` scaffolds a plain git repo with `requirements.txt` (pinning the currently-installed framework version) instead of `pyproject.toml`. No more `pip install -e .` step for overlays — users run `pip install -r requirements.txt` and are done.
+- The framework CLI now walks up from the agent directory on startup, finds the nearest `src/` sibling, and prepends it to `sys.path`. Custom providers under `src/<pkg>/` resolve without installing the overlay as a pip package.
+- Bundled Dockerfile installs overlay dependencies from `requirements.txt` (or PEP 735 `[dependency-groups]` as an alternative) instead of running `pip install .`. The `README.md` / `llms-full.txt` placeholder workaround is gone.
+- Scaffolder `.gitignore` drops `*.egg-info/` and `dist/` (overlays no longer build wheels).
+
+### Added
+
+- `_auto_extend_sys_path()` helper in `slack_agents.config`, called from `load_agent_config()` before any plugin import.
+- End-to-end overlay integration test covering scaffold → auto-sys.path → custom provider resolution, plus Dockerfile-shape assertions.
+
+### Removed
+
+- `build-docker` no longer rejects overlays with `req*.txt` files — that file is now the expected input.
+- `slack-agents init` no longer emits `pyproject.toml` or warns about requirements files.
+- "Framework Development" section removed from `docs/setup.md` — contributors see `CONTRIBUTING.md` instead, keeping user-facing docs focused on overlay users.
+
+### Docs
+
+- Full rewrite of `docs/private-repo.md` around a single-path overlay model. PEP 735 `[dependency-groups]` documented as an alternative for teams who want `pyproject.toml` without `[project]`.
+- `README.md` "Project Structure" and "Extending" sections rewritten to match.
+
+### Migration
+
+- Delete your overlay's `pyproject.toml` and any `*.egg-info/` directories.
+- Add a `requirements.txt` pinning `python-slack-agents==0.7.0` (or `<2`).
+- Run `pip install -r requirements.txt`.
+- Custom providers under `src/<pkg>/` work without `pip install -e .`.
+
+## [0.6.3] - 2026-03-31
+
+### Fixed
+
+- Preserve agent name in Docker image for multi-agent database support (`COPY` uses `${AGENT_NAME}` so each image's agent directory keeps its identity).
+- Remove `libmupdf-dev` from the Docker image — image size down to 354 MB.
+
 ## [0.6.2] - 2026-03-19
 
 ### Added

{python_slack_agents-0.6.2 → python_slack_agents-0.7.0}/CONTRIBUTING.md

@@ -46,6 +46,12 @@ refactor: simplify streaming formatter table detection
 
 Prefixes: `feat:`, `fix:`, `docs:`, `chore:`, `test:`, `refactor:`. First line under 72 characters. Add a body after a blank line if context is needed.
 
+## CHANGELOG
+
+When your change is user-visible (a new feature, a behavior change, a removed option, a fix with user-visible symptoms), add a bullet to `CHANGELOG.md` under `## [Unreleased]`. Group by Keep-a-Changelog categories (`### Added`, `### Changed`, `### Fixed`, `### Removed`). Internal refactors and test-only changes don't need an entry.
+
+Releasing is just renaming `[Unreleased]` — so if every PR touches it, releases stay cheap and honest.
+
 ## Pull Requests
 
 1. Fork the repo and create a branch

{python_slack_agents-0.6.2 → python_slack_agents-0.7.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: python-slack-agents
-Version: 0.6.2
+Version: 0.7.0
 Summary: A Python framework for deploying AI agents as Slack bots
 Project-URL: Homepage, https://github.com/CompareNetworks/python-slack-agents
 Project-URL: Repository, https://github.com/CompareNetworks/python-slack-agents
@@ -90,9 +90,9 @@ pip install python-slack-agents
 # Scaffold the project
 slack-agents init my-agents
 
-# Add your tokens and install for development
-cp .env.example .env       # add your Slack and LLM tokens
-pip install -e .
+# Add your tokens and install framework + deps
+cp .env.example .env                 # add your Slack and LLM tokens
+pip install -r requirements.txt
 
 # Run the hello-world agent
 slack-agents run agents/hello-world
@@ -243,21 +243,31 @@ tools:
 
 ## Project Structure
 
-When you add custom providers (tools, LLM, storage, or access control), your project needs a `pyproject.toml` and a `src/` directory so that `pip install -e .` makes your code importable and `slack-agents build-docker` works:
+Your overlay is a plain git repo — not a Python package. You edit configs, commit, and run; there's no
+install-the-overlay-as-a-package step. A typical layout looks like:
 
 ```
 my-agents/
-├── pyproject.toml          # declares python-slack-agents as dependency
-├── src/
-│   └── my_agents/          # your custom providers go here
-│       └── __init__.py
+├── requirements.txt        # pins python-slack-agents (and any extra deps)
+├── .env.example
+├── .gitignore
 ├── agents/
 │   └── my-agent/
 │       ├── config.yaml
 │       └── system_prompt.txt
-└── .env
+└── src/                    # optional — only if you add custom providers
+    └── my_agents/
+        └── __init__.py
 ```
 
+Two conventions to know:
+
+- **`src/` holds custom Python.** On `slack-agents run`, the framework walks up from the agent directory,
+  finds the nearest `src/` sibling, and prepends it to `sys.path`. Anything under `src/<pkg>/...` is
+  importable as `<pkg>.…` with no install step.
+- **`requirements.txt` pins your framework version and any extra Python deps.** `pip install -r requirements.txt`
+  is the only install command you ever run.
+
 `slack-agents init` scaffolds this for you. See [Organizing agents](https://github.com/CompareNetworks/python-slack-agents/blob/main/docs/private-repo.md) for details.
 
 ## Extending
@@ -281,7 +291,10 @@ class Provider(BaseLLMProvider):
         ...
 ```
 
-After `pip install -e .`, your providers are importable and the `type` field in config resolves them. This also works with `slack-agents build-docker` — the bundled Dockerfile runs `pip install .` automatically.
+After you drop a module under `src/`, it's picked up automatically on the next `slack-agents run` —
+the framework prepends `./src` to `sys.path` at startup. The same mechanism works inside Docker:
+the bundled Dockerfile installs dependencies from `requirements.txt` and copies your `src/` into the
+image, so custom providers resolve in production too.
 
 See the docs for the full interface for each component:
 

{python_slack_agents-0.6.2 → python_slack_agents-0.7.0}/README.md

@@ -44,9 +44,9 @@ pip install python-slack-agents
 # Scaffold the project
 slack-agents init my-agents
 
-# Add your tokens and install for development
-cp .env.example .env       # add your Slack and LLM tokens
-pip install -e .
+# Add your tokens and install framework + deps
+cp .env.example .env                 # add your Slack and LLM tokens
+pip install -r requirements.txt
 
 # Run the hello-world agent
 slack-agents run agents/hello-world
@@ -197,21 +197,31 @@ tools:
 
 ## Project Structure
 
-When you add custom providers (tools, LLM, storage, or access control), your project needs a `pyproject.toml` and a `src/` directory so that `pip install -e .` makes your code importable and `slack-agents build-docker` works:
+Your overlay is a plain git repo — not a Python package. You edit configs, commit, and run; there's no
+install-the-overlay-as-a-package step. A typical layout looks like:
 
 ```
 my-agents/
-├── pyproject.toml          # declares python-slack-agents as dependency
-├── src/
-│   └── my_agents/          # your custom providers go here
-│       └── __init__.py
+├── requirements.txt        # pins python-slack-agents (and any extra deps)
+├── .env.example
+├── .gitignore
 ├── agents/
 │   └── my-agent/
 │       ├── config.yaml
 │       └── system_prompt.txt
-└── .env
+└── src/                    # optional — only if you add custom providers
+    └── my_agents/
+        └── __init__.py
 ```
 
+Two conventions to know:
+
+- **`src/` holds custom Python.** On `slack-agents run`, the framework walks up from the agent directory,
+  finds the nearest `src/` sibling, and prepends it to `sys.path`. Anything under `src/<pkg>/...` is
+  importable as `<pkg>.…` with no install step.
+- **`requirements.txt` pins your framework version and any extra Python deps.** `pip install -r requirements.txt`
+  is the only install command you ever run.
+
 `slack-agents init` scaffolds this for you. See [Organizing agents](https://github.com/CompareNetworks/python-slack-agents/blob/main/docs/private-repo.md) for details.
 
 ## Extending
@@ -235,7 +245,10 @@ class Provider(BaseLLMProvider):
         ...
 ```
 
-After `pip install -e .`, your providers are importable and the `type` field in config resolves them. This also works with `slack-agents build-docker` — the bundled Dockerfile runs `pip install .` automatically.
+After you drop a module under `src/`, it's picked up automatically on the next `slack-agents run` —
+the framework prepends `./src` to `sys.path` at startup. The same mechanism works inside Docker:
+the bundled Dockerfile installs dependencies from `requirements.txt` and copies your `src/` into the
+image, so custom providers resolve in production too.
 
 See the docs for the full interface for each component:
 

{python_slack_agents-0.6.2 → python_slack_agents-0.7.0}/docs/cli.md

@@ -10,7 +10,7 @@ Scaffold a new project in the current directory.
 slack-agents init <project_name>
 ```
 
-Creates `pyproject.toml`, `src/<package>/`, `.env.example`, and a `hello-world` agent. Existing files are skipped with a warning.
+Creates `requirements.txt`, `src/<package>/`, `.env.example`, `.gitignore`, and a `hello-world` agent. Existing files are skipped with a warning.
 
 ## run
 

python_slack_agents-0.7.0/docs/private-repo.md

@@ -0,0 +1,81 @@
+# Organizing Your Agents
+
+Agents are just directories with `config.yaml` and `system_prompt.txt`. Where you put them depends on your situation.
+
+## Option 1: In the framework repo
+
+If you're developing the framework itself, add agents directly to `agents/`. To keep private agents out of version control, use a gitignored directory instead:
+
+```bash
+slack-agents run agents-local/my-agent
+```
+
+## Option 2: Separate repository
+
+For production agents with company-specific prompts, tools, and configs, create a standalone repository:
+
+```bash
+mkdir my-agents && cd my-agents
+python3 -m venv .venv
+source .venv/bin/activate
+pip install python-slack-agents
+slack-agents init my-agents
+pip install -r requirements.txt
+```
+
+This scaffolds:
+
+```
+my-agents/
+├── requirements.txt              # pins python-slack-agents
+├── .env.example
+├── .gitignore
+├── agents/
+│   └── hello-world/
+│       ├── config.yaml
+│       └── system_prompt.txt
+└── src/
+    └── my_agents/
+        └── __init__.py           # add custom providers here
+```
+
+Your overlay is a **plain git repo** — not a Python package. You edit configs, commit, and run. There is no `pip install .` / `pip install -e .` step.
+
+### Two conventions to know
+
+- **`src/` holds custom Python.** On `slack-agents run`, the framework walks up from the agent directory looking for a `src/` sibling and prepends it to `sys.path`. Anything you put under `src/my_agents/...` becomes importable as `my_agents.…` — no install step.
+- **`requirements.txt` pins your framework and any extra Python deps.** `pip install -r requirements.txt` is the only install command you ever run.
+
+### Custom providers
+
+Drop a module under `src/` and reference it in config:
+
+```yaml
+tools:
+  internal-api:
+    type: my_agents.tools.internal_api
+    allowed_functions: [".*"]
+    base_url: "{INTERNAL_API_URL}"
+```
+
+Create `src/my_agents/tools/internal_api.py` with a `Provider` class; the framework will find it on the next `slack-agents run`. No reinstall needed.
+
+### Prefer pyproject.toml?
+
+You can use a `pyproject.toml` instead of `requirements.txt` — but **do not add a `[project]` table**, or your overlay becomes an installable package again (the thing this design deliberately avoids). Use PEP 735 `[dependency-groups]`:
+
+```toml
+[dependency-groups]
+default = ["python-slack-agents==X.Y.Z"]
+```
+
+Install with `pip install --group default` (pip ≥ 24.1) or `uv sync`.
+
+### Docker
+
+No custom Dockerfile needed — `python-slack-agents` bundles one that auto-detects your dependency file:
+
+```bash
+slack-agents build-docker agents/my-agent
+slack-agents build-docker agents/my-agent --push registry.example.com
+```

{python_slack_agents-0.6.2 → python_slack_agents-0.7.0}/docs/setup.md

@@ -17,25 +17,17 @@ pip install python-slack-agents
 # Scaffold the project
 slack-agents init my-agents
 
-# Add your tokens and install for development
-cp .env.example .env       # add your Slack and LLM tokens (see below)
-pip install -e .
+# Install framework (and any deps) from requirements.txt
+pip install -r requirements.txt
+
+# Add your tokens
+cp .env.example .env
 
 # Run the hello-world agent
 slack-agents run agents/hello-world
 ```
 
-## Framework Development
-
-If you're working on the framework itself:
-
-```bash
-git clone https://github.com/CompareNetworks/python-slack-agents.git
-cd python-slack-agents
-python3 -m venv .venv
-source .venv/bin/activate
-pip install -e ".[dev]"
-```
+*Working on the framework itself? See [CONTRIBUTING.md](../CONTRIBUTING.md).*
 
 ## Environment Variables
 

{python_slack_agents-0.6.2 → python_slack_agents-0.7.0}/llms-full.txt

@@ -54,25 +54,17 @@ pip install python-slack-agents
 # Scaffold the project
 slack-agents init my-agents
 
-# Add your tokens and install for development
-cp .env.example .env       # add your Slack and LLM tokens (see below)
-pip install -e .
+# Install framework (and any deps) from requirements.txt
+pip install -r requirements.txt
+
+# Add your tokens
+cp .env.example .env
 
 # Run the hello-world agent
 slack-agents run agents/hello-world
 ```
 
-## Framework Development
-
-If you're working on the framework itself:
-
-```bash
-git clone https://github.com/CompareNetworks/python-slack-agents.git
-cd python-slack-agents
-python3 -m venv .venv
-source .venv/bin/activate
-pip install -e ".[dev]"
-```
+*Working on the framework itself? See [CONTRIBUTING.md](../CONTRIBUTING.md).*
 
 ## Environment Variables
 
@@ -803,7 +795,7 @@ Scaffold a new project in the current directory.
 slack-agents init <project_name>
 ```
 
-Creates `pyproject.toml`, `src/<package>/`, `.env.example`, and a `hello-world` agent. Existing files are skipped with a warning.
+Creates `requirements.txt`, `src/<package>/`, `.env.example`, `.gitignore`, and a `hello-world` agent. Existing files are skipped with a warning.
 
 ## run
 
@@ -1169,32 +1161,35 @@ python3 -m venv .venv
 source .venv/bin/activate
 pip install python-slack-agents
 slack-agents init my-agents
-pip install -e .
+pip install -r requirements.txt
 ```
 
 This scaffolds:
 
 ```
 my-agents/
-├── pyproject.toml
-├── src/
-│   └── my_agents/
-│       └── __init__.py
+├── requirements.txt              # pins python-slack-agents
+├── .env.example
+├── .gitignore
 ├── agents/
 │   └── hello-world/
 │       ├── config.yaml
 │       └── system_prompt.txt
-└── .env.example
+└── src/
+    └── my_agents/
+        └── __init__.py           # add custom providers here
 ```
 
-The `pyproject.toml` and `src/` directory are required so that:
+Your overlay is a **plain git repo** — not a Python package. You edit configs, commit, and run. There is no `pip install .` / `pip install -e .` step.
 
-- **`slack-agents run`** can import custom providers under `src/` (via `pip install -e .`)
-- **`slack-agents build-docker`** works (the bundled Dockerfile runs `pip install .`)
+### Two conventions to know
+
+- **`src/` holds custom Python.** On `slack-agents run`, the framework walks up from the agent directory looking for a `src/` sibling and prepends it to `sys.path`. Anything you put under `src/my_agents/...` becomes importable as `my_agents.…` — no install step.
+- **`requirements.txt` pins your framework and any extra Python deps.** `pip install -r requirements.txt` is the only install command you ever run.
 
 ### Custom providers
 
-Add custom providers to `src/` and reference them in config:
+Drop a module under `src/` and reference it in config:
 
 ```yaml
 tools:
@@ -1204,9 +1199,22 @@ tools:
     base_url: "{INTERNAL_API_URL}"
 ```
 
+Create `src/my_agents/tools/internal_api.py` with a `Provider` class; the framework will find it on the next `slack-agents run`. No reinstall needed.
+
+### Prefer pyproject.toml?
+
+You can use a `pyproject.toml` instead of `requirements.txt` — but **do not add a `[project]` table**, or your overlay becomes an installable package again (the thing this design deliberately avoids). Use PEP 735 `[dependency-groups]`:
+
+```toml
+[dependency-groups]
+default = ["python-slack-agents==X.Y.Z"]
+```
+
+Install with `pip install --group default` (pip ≥ 24.1) or `uv sync`.
+
 ### Docker
 
-No custom Dockerfile needed — `python-slack-agents` bundles one:
+No custom Dockerfile needed — `python-slack-agents` bundles one that auto-detects your dependency file:
 
 ```bash
 slack-agents build-docker agents/my-agent

{python_slack_agents-0.6.2 → python_slack_agents-0.7.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "python-slack-agents"
-version = "0.6.2"
+version = "0.7.0"
 description = "A Python framework for deploying AI agents as Slack bots"
 authors = [{name = "Eric Pichon", email = "epichon@comparenetworks.com"}]
 readme = "README.md"

python_slack_agents-0.7.0/src/slack_agents/Dockerfile

@@ -0,0 +1,38 @@
+FROM python:3.12-slim
+
+WORKDIR /app
+
+# Install dependencies first so this layer caches well.
+# Supports either requirements.txt (default from `slack-agents init`)
+# or a pyproject.toml with PEP 735 [dependency-groups] (no [project]).
+COPY requirements.txt* pyproject.toml* ./
+RUN if [ -f requirements.txt ]; then \
+        pip install --no-cache-dir -r requirements.txt ; \
+    elif [ -f pyproject.toml ]; then \
+        pip install --no-cache-dir --group default ; \
+    else \
+        echo "Error: overlay must have requirements.txt or a pyproject.toml with [dependency-groups]" >&2 ; \
+        exit 1 ; \
+    fi
+
+# Download DejaVu fonts for PDF export with Unicode support
+RUN python -m slack_agents.scripts.download_fonts
+
+# Copy the overlay's custom providers (if any). The framework's CLI
+# prepends ./src to sys.path at runtime so imports like
+# `my_agents.tools.foo` resolve without installing the overlay.
+COPY src/ /app/src/
+
+# Copy only the selected agent into /app/agent/<name>/ so the framework
+# derives agent_name from the directory name. Multiple agents sharing a
+# database remain distinguishable. The glob agent/* resolves to the
+# single subdirectory. `exec` replaces the shell so slack-agents
+# receives signals directly.
+ARG AGENT_PATH
+ARG AGENT_NAME
+COPY ${AGENT_PATH}/ /app/agent/${AGENT_NAME}/
+
+RUN useradd -r -s /bin/false agent
+USER agent
+
+CMD ["sh", "-c", "exec slack-agents run agent/*"]

{python_slack_agents-0.6.2 → python_slack_agents-0.7.0}/src/slack_agents/cli/build_docker.py

@@ -67,18 +67,6 @@ def execute(args):
     else:
         image_tag = f"{image_name}:{version}"
 
-    req_files = sorted(Path(".").glob("req*.txt"))
-    if req_files:
-        names = ", ".join(f.name for f in req_files)
-        print(
-            f"Error: found {names} in the project root.\n"
-            "Docker builds install dependencies from pyproject.toml, not\n"
-            "requirements files. Move your dependencies into pyproject.toml\n"
-            "under [project] dependencies, then remove the requirements file(s).",
-            file=sys.stderr,
-        )
-        sys.exit(1)
-
     print(f"Building {image_tag} ...")
     result = subprocess.run(
         [
@@ -88,6 +76,8 @@ def execute(args):
             args.platform,
             "--build-arg",
             f"AGENT_PATH={agent_dir}",
+            "--build-arg",
+            f"AGENT_NAME={agent_name}",
             "-f",
             str(dockerfile),
             "-t",

{python_slack_agents-0.6.2 → python_slack_agents-0.7.0}/src/slack_agents/cli/init.py

@@ -1,22 +1,6 @@
 """CLI subcommand: init — scaffold a new project."""
 
-PYPROJECT_TEMPLATE = """\
-[build-system]
-requires = ["setuptools"]
-build-backend = "setuptools.build_meta"
-
-[project]
-name = "{project_name}"
-version = "0.1.0"
-requires-python = ">=3.12"
-dependencies = [
-    "python-slack-agents<2",
-    # add packages required by your plugins here
-]
-
-[tool.setuptools.packages.find]
-where = ["src"]  # required to import plugins and to build docker images
-"""
+REQUIREMENTS_TEMPLATE = "python-slack-agents{pin}\n"
 
 ENV_EXAMPLE = """\
 # Full setup guide:
@@ -35,12 +19,10 @@ GITIGNORE = """\
 .venv/
 __pycache__/
 *.pyc
-*.egg-info/
 *.db
 .DS_Store
 .idea/
 .vscode/
-dist/
 """
 
 HELLO_WORLD_CONFIG = """\
@@ -76,10 +58,22 @@ def register(subparsers):
         "init",
         help="Scaffold a new project in the current directory",
     )
-    p.add_argument("project_name", help="Project name (used in pyproject.toml)")
+    p.add_argument("project_name", help="Project name (used to derive the src/ package name)")
     p.set_defaults(handler=execute)
 
 
+def _framework_pin() -> str:
+    """Return a pip version specifier pinning the current framework version.
+
+    Falls back to '<2' if the installed version can't be determined."""
+    try:
+        from importlib.metadata import PackageNotFoundError, version
+
+        return f"=={version('python-slack-agents')}"
+    except (PackageNotFoundError, ImportError):
+        return "<2"
+
+
 def execute(args):
     import re
     from pathlib import Path
@@ -88,9 +82,7 @@ def execute(args):
     package_name = re.sub(r"[^a-z0-9]+", "_", project_name.lower()).strip("_") or "my_agents"
 
     files = {
-        "pyproject.toml": PYPROJECT_TEMPLATE.format(
-            project_name=project_name, package_name=package_name
-        ),
+        "requirements.txt": REQUIREMENTS_TEMPLATE.format(pin=_framework_pin()),
         f"src/{package_name}/__init__.py": "",
         ".env.example": ENV_EXAMPLE,
         ".gitignore": GITIGNORE,
@@ -111,18 +103,7 @@ def execute(args):
         path.write_text(content)
         print(f"Created {rel_path}")
 
-    # Warn about requirements files that won't be picked up by Docker builds
-    req_files = sorted(Path(".").glob("req*.txt"))
-    if req_files:
-        names = ", ".join(f.name for f in req_files)
-        print(f"WARNING: found {names}")
-        print("  Docker builds install dependencies from pyproject.toml, not")
-        print("  requirements files. Move your dependencies into pyproject.toml")
-        print("  under [project] dependencies or your Docker images will be")
-        print("  missing packages.")
-        print()
-
     print("Next steps:")
-    print("  cp .env.example .env                # add your tokens")
-    print("  pip install -e .                     # install for development")
-    print("  slack-agents run agents/hello-world  # run the example agent")
+    print("  cp .env.example .env                      # add your tokens")
+    print("  pip install -r requirements.txt           # install the framework")
+    print("  slack-agents run agents/hello-world       # run the example agent")