0.7.0

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 ..

v0.6.3

What's Changed

• fix: Preserve agent name in Docker image so multiple agents sharing a database are distinguishable. Previously all Docker-built agents used agent_name = "agent".

v0.6.2

What's New

Added

• Canvas user-level authorization — tools enforce requesting user's access level via files.info metadata
• Canvas file importer (application/vnd.slack-docs) — users can attach canvases to messages
• file_id field on InputFile — file import pipeline now passes Slack file IDs to handlers
• org_access parameter on canvas_access_add for workspace-wide access

Changed

• Canvas tool descriptions instruct the LLM to guide users to attach canvases via Slack's + button (never ask for IDs)
• Canvas tool errors now return structured JSON instead of plain text

Removed

• canvas_list tool (scaling concern with batch files.info; users discover canvases via Slack UI)
• channel_id parameter from canvas_create (standalone canvases only)
• channel_ids parameter from canvas_access_add and canvas_access_remove

Full Changelog: v0.6.1...v0.6.2

v0.6.1

What's New

• Improved slack-agents init — now generates .gitignore, .env.example with setup guide link and token instructions, and shows proposed content when skipping existing files
• build-docker shows required env vars — after build (and push), lists all {ENV_VAR} patterns from the agent's config so you know what secrets to provide at runtime
• req*.txt detection — init warns and build-docker errors if requirements files are found, since Docker builds use pyproject.toml dependencies
• YAML comment safety — commented-out {ENV_VAR} patterns no longer cause KeyError at startup
• Updated setup flow — docs now use venv-first approach: create venv, install package, then slack-agents init

v0.6.0

What's New

• slack-agents init <project_name> — new CLI command that scaffolds a project with pyproject.toml, src/, .env.example, and a hello-world agent. Sets up the required structure for custom providers and Docker builds.

• AI agent discoverability — added llms.txt and llms-full.txt following the llms.txt convention. llms-full.txt is bundled in the PyPI wheel so AI agents can read the full reference locally after pip install.

• Simplified Dockerfile — builds now work for both the framework repo and user projects without requiring README.md or llms-full.txt in the build context.

• Documentation — new "Project Structure" section in README explaining the pyproject.toml + src/ requirement for custom providers. Updated docs for the init command, organizing agents, and the release process.

v0.5.0

Initial PyPI release