agent-team 0.5.0__tar.gz

agent_team-0.5.0/LICENSE

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

agent_team-0.5.0/PKG-INFO

@@ -0,0 +1,180 @@
+Metadata-Version: 2.4
+Name: agent-team
+Version: 0.5.0
+Summary: A configurable team of AI agents (any model, any machine) that plans, builds, reviews, markets and ships a software project through GitHub.
+Author: Lakeba
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/lakeba/agent-team
+Project-URL: Documentation, https://lakeba.github.io/agent-team/
+Project-URL: Changelog, https://github.com/lakeba/agent-team/blob/main/CHANGELOG.md
+Keywords: ai,agents,llm,claude,ollama,github,devops
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: anthropic>=1.0
+Provides-Extra: screenshots
+Requires-Dist: pillow>=10; extra == "screenshots"
+Provides-Extra: dev
+Requires-Dist: pillow>=10; extra == "dev"
+Dynamic: license-file
+
+# agent-team
+
+A configurable team of AI agents that works on a software project the way a small team would:
+it plans a roadmap, builds features, reviews them, writes marketing material, and ships through
+GitHub with pull requests, CI, sign-offs and releases.
+
+Team members can run on any model and any machine: Claude through the Anthropic API, local
+models through Ollama, any OpenAI-compatible server, or another machine running
+`agent-team serve`. A team is described in a `.team.toml` file in each project, so adding a
+member, a machine or a project is a configuration change.
+
+It grew out of todo-py, a small command-line app this team planned, built, marketed and released
+(v1.0.0 and v1.0.1); its team is in [examples/todo-py.team.toml](examples/todo-py.team.toml).
+
+## How the team works
+
+| Workflow | Command | What happens |
+|---|---|---|
+| Discuss | `agent-team discuss "next features"` | Members talk in turn until they all agree; the lead updates `ROADMAP.md`. |
+| Build | `agent-team build "task" --branch x --pr` | The lead writes `PLAN.md`, builders implement it (in parallel with `--parallel`), tests run each round, the lead reviews until approved, then a PR opens. Optional QA, security and docs members write tests first, review the result and update the docs. |
+| Autopilot | `agent-team autopilot --milestone M2` | Works through the roadmap a PR at a time: the lead picks the next task, the team builds it, each devops shift reviews, fixes and merges, until the lead says the milestone is done (or it gets stuck, or hits a spend limit). |
+| Fix | `agent-team fix 12` | When the lead requests changes on a PR, a builder applies the review on that PR's branch, the lead confirms the blocking points are addressed, and it pushes; the next shift reviews the new commit. |
+| Market | `agent-team market` | The marketing member writes a brief, a website and a pitch deck; a fact-checker checks claims and the lead reviews with screenshots. |
+| Set up | `agent-team setup --license "MIT, copyright 2026 Lakeba"` | The devops member drafts README, CONTRIBUTING, CHANGELOG, CI and templates. |
+| Ship | `agent-team ship` | One devops shift on GitHub: triage, owner sign-offs, lead review, merge, release (or, with `release = "ask"`, a release proposal you approve with `ship --release X.Y.Z`), feedback digest. `agent-team schedule --every 6h` runs shifts unattended, never two at once. |
+| Dashboard | `agent-team ui` | Overview, Team, Runs, Costs, live Activity charts (spend, runs, merges, problems, latest events), Settings (easy switches and team templates, always previewed as a diff) and Projects (every project on this Mac). A page on this machine: the team and whether each member is reachable, every run with each member's verdicts, estimated costs per member, day and run, and the GitHub state. Edit members, connections, guarantees and prices there, add a machine with a guided wizard, and review the diff before saving. Start runs there and follow their output live. |
+
+Guardrails are enforced in code, not left to the models. A PR merges only when CI is green, the
+lead approved the exact head commit, and every member who owns a changed path signed off that
+same commit (the lead's approval is its own sign-off). On a re-review, reviewers block only on
+points still open or problems the new commit introduces, so a PR that fixes what was asked passes. Releases need green CI on `main` and a CHANGELOG entry. Text from outside the team
+always reaches the models marked as untrusted. Spend limits in `.team.toml` stop any run before it
+costs more than you allow, and large projects get a focused context instead of every file.
+
+Builders change files with small search/replace edits instead of rewriting them, and an edit
+that doesn't match is refused and sent back. Reviewers read files, search, see the diff and run
+the tests themselves. When a reviewer blocks for a reason that will matter again, the lesson is
+kept and every member sees it in later work.
+
+With `[sandbox] mode = "container"`, the code the team writes is tested in a throwaway container
+with no network and none of your keys. Every push is checked for secrets first (key and token formats, private keys, `.env` files, and
+the values in your keys file). Paths you list in `require_approval` wait for your approval of the
+exact commit. Weaker models hand work to a stronger member after rejected rounds (`escalate_to`),
+and `[notify]` posts to Slack or any webhook when PRs open or merge, approvals or releases wait
+for you, or autopilot stops.
+
+## Install
+
+Requirements: macOS or Linux, Python 3.11+ (on Ubuntu/Debian also `python3-venv`), git, and an
+Anthropic API key for Claude members. Optional: [Ollama](https://ollama.com/)
+for local models, on this machine or another. The workflows that work on GitHub (`build --pr`,
+`ship`, `setup` and the plugin's PR steps) also need the [GitHub CLI](https://cli.github.com/)
+signed in (`gh auth login`).
+
+One command installs the CLI into its own environment under `~/.agent-team`, puts `agent-team` on
+your `PATH` (`~/.local/bin`), and installs the Claude Code plugin if Claude Code is present:
+
+```bash
+curl -fsSL https://raw.githubusercontent.com/lakeba/agent-team/main/scripts/install.sh | bash
+```
+
+Run it again to update, then run `/reload-plugins` in any open Claude Code session (or start a new
+one): an open session keeps the commands it started with. Options go after `bash -s --`, for example `| bash -s -- --ref v0.1.0`
+for a specific version, `--no-plugin` to skip the plugin, or `--uninstall` to remove everything
+it installed. If you prefer pipx: `pipx install git+https://github.com/lakeba/agent-team.git`
+(that installs the CLI only).
+
+## Quick start
+
+```bash
+agent-team keys set ANTHROPIC_API_KEY    # asks for the key (hidden); every agent-team command finds it
+cd ~/code/my-project
+agent-team ready      # checklist: git, GitHub, keys, Ollama, with the fix for anything missing
+agent-team init       # writes .team.toml; add --ollama-url http://HOST:11434 for Ollama on another machine
+agent-team doctor     # the checklist again, then checks every member can be reached
+```
+
+Keys live in `~/.config/agent-team/env`, readable only by you, so they work the same from any shell,
+the dashboard, background runs and schedules (Ubuntu's `~/.bashrc`, for one, is skipped by
+non-interactive shells). A variable already exported in your environment wins.
+
+Then edit `.team.toml` (or open `agent-team ui` and use **Edit team**): set the project's
+guarantees, adjust the team, give members skills (Markdown files or Claude Code skill folders added
+to their prompts), set spend limits under `[limits]`, and run a workflow:
+
+```bash
+agent-team discuss "next features"                       # agree a roadmap
+agent-team build "add an export command" --branch team/export --pr
+agent-team ship                                          # one devops shift on GitHub
+```
+
+### Other commands
+
+| Command | What it does |
+|---|---|
+| `agent-team status [--json] [--health]` | The team, spend per member and today, recent and background runs, the schedule. |
+| `agent-team ui` | The dashboard: see and edit the team, start runs, follow costs. |
+| `agent-team jobs [start <workflow> \| stop <id> \| log <id>]` | Runs in the background, as the dashboard and the Claude panel start them. |
+| `agent-team schedule --every 6h` | Run devops shifts on a schedule (launchd on macOS, cron elsewhere); `--remove` to stop. |
+| `agent-team serve ...` | Serve a model on this machine as a team member for a team elsewhere. |
+| `agent-team discover` | Find agent-team nodes on the local network. |
+| `agent-team ready [--json]` | What this machine and project still need (git, GitHub, keys, Ollama, models), each with its fix. |
+| `agent-team keys [set NAME \| remove NAME]` | API keys and tokens in agent-team's own keys file; values are never shown. |
+| `agent-team issues [sync --milestone M2 --yes]` | The team's to-do list: `team:build` issues, created from the roadmap by the lead (shown first, created with `--yes`). Autopilot builds them and its PRs close them. |
+| `agent-team approve [PR]` | Approve a PR's current commit when it changes paths in `require_approval`; with no number, list what's waiting. |
+| `agent-team notify` | Send a test message to the `[notify]` webhook. |
+| `agent-team eval [--only feature,bug]` | Runs fixed scenarios with your real models in a throwaway project (no GitHub): pass/fail, rounds and cost. Asks before spending. |
+| `agent-team estimate build` | Predicts a run's cost from this project's past runs. |
+| `agent-team projects` | Every project you use agent-team in: spend, runs, what waits for you. |
+| `agent-team scoreboard` | Each builder's approval and first-round rate, average rounds and cost; each reviewer's pushback; cost per merged PR. |
+| `agent-team memory [add TEXT \| forget N]` | The lessons the team learned from its reviews, which every member sees in later work. |
+| `agent-team agents`, `agent-team doctor` | List the team; check every member can be reached. |
+
+`build` takes `--parallel` (split the plan across every builder), `--skip qa,security,docs`,
+`--rounds`, `--builder` and `--lead`. Every command takes `-C <project>`; `--help` lists the rest.
+
+### Use it from Claude Code
+
+The installer adds the plugin. To add it by hand, at the prompt of a Claude Code session:
+
+```
+/plugin install agent-team --marketplace lakeba/agent-team
+```
+
+Then, in any project: `/team-init`, `/team-doctor`, `/team-plan`, `/team-build <task>`,
+`/team-ship`, `/team-fix <PR>`, `/team-schedule <6h>`, `/team-market` and `/team-ui`. Claude runs the workflow where you can watch it, checks the
+result, and reports back. In projects with a `.team.toml`, the plugin also opens an agent-team side
+panel (or run `/team-panel`): the team, each member's health, recent runs and spend, with buttons to
+refresh, check health, start a devops shift and start the dashboard, plus background runs you can
+stop. `/team-run build <task>` (or `fix <PR>`, `discuss <topic>`, `ship`, `market`, `doctor`) starts a run in
+the background and the panel follows it. The commands need the `agent-team` CLI on your `PATH`.
+
+## Documentation
+
+- [Architecture](docs/architecture.md): providers, agents, workflows and how they fit.
+- [Configuration](docs/configuration.md): every `.team.toml` setting.
+- [Extending](docs/extending.md): add a team member, a role, a provider or a workflow.
+- [Remote agents](docs/remote-agents.md): let another machine join the team.
+- [Examples](examples/): the todo-py team, and a larger team across four machines with security,
+  QA and docs members, parallel builders and spend limits.
+- [Changelog](CHANGELOG.md) and [roadmap](ROADMAP.md).
+
+## Licence
+
+MIT, see [LICENSE](LICENSE).
+
+## Status
+
+Version 0.2.5. The workflows were proven on todo-py; see [ROADMAP.md](ROADMAP.md) for what's next
+and [CONTRIBUTING.md](CONTRIBUTING.md) to help.

agent_team-0.5.0/README.md

@@ -0,0 +1,150 @@
+# agent-team
+
+A configurable team of AI agents that works on a software project the way a small team would:
+it plans a roadmap, builds features, reviews them, writes marketing material, and ships through
+GitHub with pull requests, CI, sign-offs and releases.
+
+Team members can run on any model and any machine: Claude through the Anthropic API, local
+models through Ollama, any OpenAI-compatible server, or another machine running
+`agent-team serve`. A team is described in a `.team.toml` file in each project, so adding a
+member, a machine or a project is a configuration change.
+
+It grew out of todo-py, a small command-line app this team planned, built, marketed and released
+(v1.0.0 and v1.0.1); its team is in [examples/todo-py.team.toml](examples/todo-py.team.toml).
+
+## How the team works
+
+| Workflow | Command | What happens |
+|---|---|---|
+| Discuss | `agent-team discuss "next features"` | Members talk in turn until they all agree; the lead updates `ROADMAP.md`. |
+| Build | `agent-team build "task" --branch x --pr` | The lead writes `PLAN.md`, builders implement it (in parallel with `--parallel`), tests run each round, the lead reviews until approved, then a PR opens. Optional QA, security and docs members write tests first, review the result and update the docs. |
+| Autopilot | `agent-team autopilot --milestone M2` | Works through the roadmap a PR at a time: the lead picks the next task, the team builds it, each devops shift reviews, fixes and merges, until the lead says the milestone is done (or it gets stuck, or hits a spend limit). |
+| Fix | `agent-team fix 12` | When the lead requests changes on a PR, a builder applies the review on that PR's branch, the lead confirms the blocking points are addressed, and it pushes; the next shift reviews the new commit. |
+| Market | `agent-team market` | The marketing member writes a brief, a website and a pitch deck; a fact-checker checks claims and the lead reviews with screenshots. |
+| Set up | `agent-team setup --license "MIT, copyright 2026 Lakeba"` | The devops member drafts README, CONTRIBUTING, CHANGELOG, CI and templates. |
+| Ship | `agent-team ship` | One devops shift on GitHub: triage, owner sign-offs, lead review, merge, release (or, with `release = "ask"`, a release proposal you approve with `ship --release X.Y.Z`), feedback digest. `agent-team schedule --every 6h` runs shifts unattended, never two at once. |
+| Dashboard | `agent-team ui` | Overview, Team, Runs, Costs, live Activity charts (spend, runs, merges, problems, latest events), Settings (easy switches and team templates, always previewed as a diff) and Projects (every project on this Mac). A page on this machine: the team and whether each member is reachable, every run with each member's verdicts, estimated costs per member, day and run, and the GitHub state. Edit members, connections, guarantees and prices there, add a machine with a guided wizard, and review the diff before saving. Start runs there and follow their output live. |
+
+Guardrails are enforced in code, not left to the models. A PR merges only when CI is green, the
+lead approved the exact head commit, and every member who owns a changed path signed off that
+same commit (the lead's approval is its own sign-off). On a re-review, reviewers block only on
+points still open or problems the new commit introduces, so a PR that fixes what was asked passes. Releases need green CI on `main` and a CHANGELOG entry. Text from outside the team
+always reaches the models marked as untrusted. Spend limits in `.team.toml` stop any run before it
+costs more than you allow, and large projects get a focused context instead of every file.
+
+Builders change files with small search/replace edits instead of rewriting them, and an edit
+that doesn't match is refused and sent back. Reviewers read files, search, see the diff and run
+the tests themselves. When a reviewer blocks for a reason that will matter again, the lesson is
+kept and every member sees it in later work.
+
+With `[sandbox] mode = "container"`, the code the team writes is tested in a throwaway container
+with no network and none of your keys. Every push is checked for secrets first (key and token formats, private keys, `.env` files, and
+the values in your keys file). Paths you list in `require_approval` wait for your approval of the
+exact commit. Weaker models hand work to a stronger member after rejected rounds (`escalate_to`),
+and `[notify]` posts to Slack or any webhook when PRs open or merge, approvals or releases wait
+for you, or autopilot stops.
+
+## Install
+
+Requirements: macOS or Linux, Python 3.11+ (on Ubuntu/Debian also `python3-venv`), git, and an
+Anthropic API key for Claude members. Optional: [Ollama](https://ollama.com/)
+for local models, on this machine or another. The workflows that work on GitHub (`build --pr`,
+`ship`, `setup` and the plugin's PR steps) also need the [GitHub CLI](https://cli.github.com/)
+signed in (`gh auth login`).
+
+One command installs the CLI into its own environment under `~/.agent-team`, puts `agent-team` on
+your `PATH` (`~/.local/bin`), and installs the Claude Code plugin if Claude Code is present:
+
+```bash
+curl -fsSL https://raw.githubusercontent.com/lakeba/agent-team/main/scripts/install.sh | bash
+```
+
+Run it again to update, then run `/reload-plugins` in any open Claude Code session (or start a new
+one): an open session keeps the commands it started with. Options go after `bash -s --`, for example `| bash -s -- --ref v0.1.0`
+for a specific version, `--no-plugin` to skip the plugin, or `--uninstall` to remove everything
+it installed. If you prefer pipx: `pipx install git+https://github.com/lakeba/agent-team.git`
+(that installs the CLI only).
+
+## Quick start
+
+```bash
+agent-team keys set ANTHROPIC_API_KEY    # asks for the key (hidden); every agent-team command finds it
+cd ~/code/my-project
+agent-team ready      # checklist: git, GitHub, keys, Ollama, with the fix for anything missing
+agent-team init       # writes .team.toml; add --ollama-url http://HOST:11434 for Ollama on another machine
+agent-team doctor     # the checklist again, then checks every member can be reached
+```
+
+Keys live in `~/.config/agent-team/env`, readable only by you, so they work the same from any shell,
+the dashboard, background runs and schedules (Ubuntu's `~/.bashrc`, for one, is skipped by
+non-interactive shells). A variable already exported in your environment wins.
+
+Then edit `.team.toml` (or open `agent-team ui` and use **Edit team**): set the project's
+guarantees, adjust the team, give members skills (Markdown files or Claude Code skill folders added
+to their prompts), set spend limits under `[limits]`, and run a workflow:
+
+```bash
+agent-team discuss "next features"                       # agree a roadmap
+agent-team build "add an export command" --branch team/export --pr
+agent-team ship                                          # one devops shift on GitHub
+```
+
+### Other commands
+
+| Command | What it does |
+|---|---|
+| `agent-team status [--json] [--health]` | The team, spend per member and today, recent and background runs, the schedule. |
+| `agent-team ui` | The dashboard: see and edit the team, start runs, follow costs. |
+| `agent-team jobs [start <workflow> \| stop <id> \| log <id>]` | Runs in the background, as the dashboard and the Claude panel start them. |
+| `agent-team schedule --every 6h` | Run devops shifts on a schedule (launchd on macOS, cron elsewhere); `--remove` to stop. |
+| `agent-team serve ...` | Serve a model on this machine as a team member for a team elsewhere. |
+| `agent-team discover` | Find agent-team nodes on the local network. |
+| `agent-team ready [--json]` | What this machine and project still need (git, GitHub, keys, Ollama, models), each with its fix. |
+| `agent-team keys [set NAME \| remove NAME]` | API keys and tokens in agent-team's own keys file; values are never shown. |
+| `agent-team issues [sync --milestone M2 --yes]` | The team's to-do list: `team:build` issues, created from the roadmap by the lead (shown first, created with `--yes`). Autopilot builds them and its PRs close them. |
+| `agent-team approve [PR]` | Approve a PR's current commit when it changes paths in `require_approval`; with no number, list what's waiting. |
+| `agent-team notify` | Send a test message to the `[notify]` webhook. |
+| `agent-team eval [--only feature,bug]` | Runs fixed scenarios with your real models in a throwaway project (no GitHub): pass/fail, rounds and cost. Asks before spending. |
+| `agent-team estimate build` | Predicts a run's cost from this project's past runs. |
+| `agent-team projects` | Every project you use agent-team in: spend, runs, what waits for you. |
+| `agent-team scoreboard` | Each builder's approval and first-round rate, average rounds and cost; each reviewer's pushback; cost per merged PR. |
+| `agent-team memory [add TEXT \| forget N]` | The lessons the team learned from its reviews, which every member sees in later work. |
+| `agent-team agents`, `agent-team doctor` | List the team; check every member can be reached. |
+
+`build` takes `--parallel` (split the plan across every builder), `--skip qa,security,docs`,
+`--rounds`, `--builder` and `--lead`. Every command takes `-C <project>`; `--help` lists the rest.
+
+### Use it from Claude Code
+
+The installer adds the plugin. To add it by hand, at the prompt of a Claude Code session:
+
+```
+/plugin install agent-team --marketplace lakeba/agent-team
+```
+
+Then, in any project: `/team-init`, `/team-doctor`, `/team-plan`, `/team-build <task>`,
+`/team-ship`, `/team-fix <PR>`, `/team-schedule <6h>`, `/team-market` and `/team-ui`. Claude runs the workflow where you can watch it, checks the
+result, and reports back. In projects with a `.team.toml`, the plugin also opens an agent-team side
+panel (or run `/team-panel`): the team, each member's health, recent runs and spend, with buttons to
+refresh, check health, start a devops shift and start the dashboard, plus background runs you can
+stop. `/team-run build <task>` (or `fix <PR>`, `discuss <topic>`, `ship`, `market`, `doctor`) starts a run in
+the background and the panel follows it. The commands need the `agent-team` CLI on your `PATH`.
+
+## Documentation
+
+- [Architecture](docs/architecture.md): providers, agents, workflows and how they fit.
+- [Configuration](docs/configuration.md): every `.team.toml` setting.
+- [Extending](docs/extending.md): add a team member, a role, a provider or a workflow.
+- [Remote agents](docs/remote-agents.md): let another machine join the team.
+- [Examples](examples/): the todo-py team, and a larger team across four machines with security,
+  QA and docs members, parallel builders and spend limits.
+- [Changelog](CHANGELOG.md) and [roadmap](ROADMAP.md).
+
+## Licence
+
+MIT, see [LICENSE](LICENSE).
+
+## Status
+
+Version 0.2.5. The workflows were proven on todo-py; see [ROADMAP.md](ROADMAP.md) for what's next
+and [CONTRIBUTING.md](CONTRIBUTING.md) to help.

agent_team-0.5.0/pyproject.toml

@@ -0,0 +1,45 @@
+[build-system]
+requires = ["setuptools>=77"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "agent-team"
+version = "0.5.0"
+description = "A configurable team of AI agents (any model, any machine) that plans, builds, reviews, markets and ships a software project through GitHub."
+readme = "README.md"
+requires-python = ">=3.11"
+license = "MIT"
+license-files = ["LICENSE"]
+authors = [{ name = "Lakeba" }]
+keywords = ["ai", "agents", "llm", "claude", "ollama", "github", "devops"]
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "Environment :: Console",
+  "Intended Audience :: Developers",
+  "Operating System :: MacOS",
+  "Operating System :: POSIX :: Linux",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Programming Language :: Python :: 3.13",
+  "Topic :: Software Development",
+]
+dependencies = ["anthropic>=1.0"]
+
+[project.optional-dependencies]
+screenshots = ["pillow>=10"]
+dev = ["pillow>=10"]
+
+[project.urls]
+Homepage = "https://github.com/lakeba/agent-team"
+Documentation = "https://lakeba.github.io/agent-team/"
+Changelog = "https://github.com/lakeba/agent-team/blob/main/CHANGELOG.md"
+
+[project.scripts]
+agent-team = "agent_team.cli:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+agent_team = ["prompts/*.md", "dashboard/static/*"]

agent_team-0.5.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

agent_team-0.5.0/src/agent_team/__init__.py

@@ -0,0 +1,3 @@
+"""agent-team: a configurable team of AI agents that works on a project through GitHub."""
+
+__version__ = "0.5.0"

agent_team-0.5.0/src/agent_team/agent.py

@@ -0,0 +1,109 @@
+"""A team member at runtime: its config, its provider, and an append-only conversation."""
+from __future__ import annotations
+
+from importlib import resources
+from pathlib import Path
+
+from . import budget, providers, ui, usage
+from .config import AgentConfig, Team
+
+
+def role_prompt(team: Team, agent: AgentConfig, name: str | None = None) -> str:
+    """The agent's prompt text: its own file if configured, else the packaged one for its role."""
+    if agent.prompt and name is None:
+        return (team.root / agent.prompt).read_text(encoding="utf-8")
+    fname = f"{name or agent.role}.md"
+    try:
+        return resources.files("agent_team.prompts").joinpath(fname).read_text(encoding="utf-8")
+    except FileNotFoundError:
+        return resources.files("agent_team.prompts").joinpath("member.md").read_text(encoding="utf-8")
+
+
+def team_roster(team: Team) -> str:
+    lines = []
+    for a in team.agents.values():
+        where = team.providers[a.provider]
+        place = f"remote node {where.url}" if where.kind == "agent-http" else f"{where.kind} model {a.model}"
+        desc = f" {a.description}" if a.description else ""
+        owns = f" Owns: {', '.join(a.owns)}." if a.owns else ""
+        skills = f" Skills: {', '.join(_skill_names(team, a))}." if a.skills else ""
+        lines.append(f"- {a.name} ({a.role}, {place}).{desc}{owns}{skills}")
+    return "\n".join(lines)
+
+
+class Agent:
+    def __init__(self, team: Team, cfg: AgentConfig, system: str, label_suffix: str = ""):
+        self.team, self.cfg, self.system = team, cfg, system
+        pcfg = team.providers[cfg.provider]
+        self.provider = providers.build(pcfg, team.secret(pcfg))
+        self.label = ui.label(cfg.name, cfg.role + label_suffix, cfg.color)
+        self.messages: list[dict] = []   # append-only, so provider-side reasoning stays valid
+
+    @property
+    def name(self) -> str:
+        return self.cfg.name
+
+    def turn(self, content) -> str:
+        if not self.provider.supports_images and not isinstance(content, str):
+            content = providers.base.to_text(content)
+        budget.check(self.team)
+        self.messages.append({"role": "user", "content": content})
+        reply = self.provider.complete(self.system, self.messages, model=self.cfg.model,
+                                       effort=self.cfg.effort, label=self.label)
+        self.messages.append({"role": "assistant", "content": reply.content})
+        # A remote node reports the model it really ran, so its member is priced correctly.
+        u = dict(reply.usage or {})
+        kind, model = u.pop("kind", "") or self.provider.kind, u.pop("model", "") or self.cfg.model
+        usage.record(self.team.root, self.cfg.name, kind, model, u)
+        return reply.text
+
+
+def _skill_names(team: Team, cfg: AgentConfig) -> list[str]:
+    from . import skills
+    names = []
+    for entry in cfg.skills:
+        try:
+            names.append(skills.load_one(team, entry).name)
+        except Exception:
+            names.append(entry)
+    return names
+
+
+def make(team: Team, cfg: AgentConfig, prompt_name: str | None = None, label_suffix: str = "",
+         **fields) -> Agent:
+    """Build an agent whose system prompt is its role prompt filled with team and project facts."""
+    template = role_prompt(team, cfg, prompt_name)
+    values = {
+        "name": cfg.name, "role": cfg.role, "project": team.project.name, "repo": team.project.repo,
+        "roster": team_roster(team), "owns": ", ".join(cfg.owns) or "nothing",
+        "guarantees": "\n".join(f"- {g}" for g in team.project.guarantees) or "- (none listed)",
+        "test_command": team.project.test_command or "(none configured)",
+        **fields,
+    }
+    system = _fill(template, values)
+    from . import memory
+    learned = memory.for_prompt(team.root)
+    if learned:
+        system = f"{system.rstrip()}\n\n{learned}"
+    if cfg.skills:
+        from . import skills
+        system = f"{system.rstrip()}\n\n{skills.render(skills.load(team, cfg))}"
+    return Agent(team, cfg, system, label_suffix)
+
+
+def _fill(template: str, values: dict) -> str:
+    """str.format that leaves unknown {placeholders} and literal braces alone."""
+    class Keep(dict):
+        def __missing__(self, key):
+            return "{" + key + "}"
+    try:
+        return template.format_map(Keep(values))
+    except (ValueError, IndexError):
+        out = template
+        for k, v in values.items():
+            out = out.replace("{" + k + "}", str(v))
+        return out
+
+
+def prompt_path(team: Team, agent: AgentConfig) -> Path | None:
+    return team.root / agent.prompt if agent.prompt else None

agent_team-0.5.0/src/agent_team/budget.py

@@ -0,0 +1,56 @@
+"""Spend limits: stop a run before it costs more than `[limits]` allows.
+
+    [limits]
+    per_run = 5.0     # US dollars for one workflow run
+    per_day = 20.0    # US dollars per UTC day, across every run in this project
+
+Checked before every model call, from the estimates in `.team/usage.jsonl`. A call already in
+flight finishes, so a run can go over by at most one reply.
+"""
+from __future__ import annotations
+
+from . import usage
+from .config import Team
+
+
+class SpendLimitError(RuntimeError):
+    pass
+
+
+def spent(team: Team, run: str | None = None) -> dict:
+    """Estimated dollars spent in this run and today (UTC)."""
+    run = usage.current_run() if run is None else run
+    today = usage.now()[:10]
+    out = {"run": 0.0, "today": 0.0}
+    for e in usage.load(team.root):
+        cost = usage.price_for(e.get("model", ""), e.get("kind", ""), team.pricing).cost(e)
+        if run and e.get("run") == run:
+            out["run"] += cost
+        if (e.get("at") or "")[:10] == today:
+            out["today"] += cost
+    return {k: round(v, 4) for k, v in out.items()}
+
+
+def milestone_spent(team: Team, milestone: str) -> float:
+    return round(sum(usage.price_for(e.get("model", ""), e.get("kind", ""), team.pricing).cost(e)
+                     for e in usage.load(team.root) if e.get("milestone") == milestone), 4)
+
+
+def check(team: Team) -> None:
+    limits = team.limits
+    milestone = usage.current_milestone()
+    cap = limits.milestones.get(milestone) if milestone else None
+    if cap:
+        spent_m = milestone_spent(team, milestone)
+        if spent_m >= cap:
+            raise SpendLimitError(f"milestone {milestone} has spent an estimated ${spent_m:.2f}, reaching its "
+                                  f"[limits.milestones] budget of ${cap:.2f}")
+    if not (limits.per_run or limits.per_day):
+        return
+    s = spent(team)
+    if limits.per_run and s["run"] >= limits.per_run:
+        raise SpendLimitError(f"this run has spent an estimated ${s['run']:.2f}, reaching the "
+                              f"[limits].per_run limit of ${limits.per_run:.2f}")
+    if limits.per_day and s["today"] >= limits.per_day:
+        raise SpendLimitError(f"this project has spent an estimated ${s['today']:.2f} today (UTC), reaching "
+                              f"the [limits].per_day limit of ${limits.per_day:.2f}")