chiefofstaff 0.1.0__tar.gz

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

@@ -0,0 +1,28 @@
+name: Bug report
+description: Something does not work as described.
+labels: [bug]
+body:
+  - type: textarea
+    id: what
+    attributes:
+      label: What happened, and what did you expect?
+    validations:
+      required: true
+  - type: textarea
+    id: steps
+    attributes:
+      label: How to reproduce
+      description: Ideally in demo mode (chiefofstaff --demo), so anyone can try it.
+  - type: input
+    id: versions
+    attributes:
+      label: Versions
+      description: "chiefofstaff --version, copilot --version, and your OS"
+    validations:
+      required: true
+  - type: textarea
+    id: details
+    attributes:
+      label: Logs or the session timeline
+      description: Remove anything private (tokens, Slack messages, company code) first.
+      render: text

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

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Security issue
+    url: https://github.com/evanl666/chiefofstaff/security/advisories/new
+    about: Report vulnerabilities privately, please.

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

@@ -0,0 +1,15 @@
+name: Idea
+description: Something Chief of Staff should do.
+labels: [idea]
+body:
+  - type: textarea
+    id: problem
+    attributes:
+      label: What gets in your way today?
+      description: The situation, not the solution. Who interrupts you, what you have to watch.
+    validations:
+      required: true
+  - type: textarea
+    id: idea
+    attributes:
+      label: What would help?

chiefofstaff-0.1.0/.github/pull_request_template.md

@@ -0,0 +1,8 @@
+## What changes for the owner
+
+<!-- One or two sentences. Screenshots from the demo for UI changes. -->
+
+## How it was tested
+
+- [ ] `uv run ruff check . && uv run ruff format --check . && uv run pytest -q`
+- [ ] Demo or live test, if it changes behavior: <!-- which -->

chiefofstaff-0.1.0/.github/workflows/copilot.yml

@@ -0,0 +1,37 @@
+name: Copilot integration
+# The contract tests against the real GitHub Copilot CLI. They need a token with Copilot access
+# (a fine-grained personal access token with the "Copilot Requests" permission) stored as the
+# COPILOT_GITHUB_TOKEN secret; without it the job is skipped.
+on:
+  schedule:
+    - cron: "17 6 * * *"
+  workflow_dispatch:
+permissions:
+  contents: read
+jobs:
+  contract:
+    runs-on: ubuntu-latest
+    env:
+      GH_TOKEN: ${{ secrets.COPILOT_GITHUB_TOKEN }}
+    steps:
+      - name: Skip without a Copilot token
+        id: token
+        run: echo "present=${{ secrets.COPILOT_GITHUB_TOKEN != '' }}" >> "$GITHUB_OUTPUT"
+      - uses: actions/checkout@v4
+        if: steps.token.outputs.present == 'true'
+      - uses: actions/setup-node@v4
+        if: steps.token.outputs.present == 'true'
+        with:
+          node-version: "22"
+      - uses: astral-sh/setup-uv@v6
+        if: steps.token.outputs.present == 'true'
+        with:
+          python-version: "3.13"
+      - if: steps.token.outputs.present == 'true'
+        run: npm install -g @github/copilot
+      - if: steps.token.outputs.present == 'true'
+        run: uv sync --locked --extra dev
+      - if: steps.token.outputs.present == 'true'
+        run: uv run --extra dev pytest -q -m copilot tests/test_backend_contract.py
+        env:
+          CHIEFOFSTAFF_TEST_COPILOT: "1"

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

@@ -0,0 +1,38 @@
+name: Release
+# Pushing a tag like v0.1.0 builds the package and publishes it to PyPI with trusted publishing
+# (configure the "chiefofstaff" project on PyPI to trust this workflow first).
+on:
+  push:
+    tags: ["v*"]
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+        with:
+          python-version: "3.13"
+      - run: uv sync --locked --extra dev
+      - run: uv run --locked --extra dev pytest -q
+      - run: uv build
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+      contents: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1
+      - uses: softprops/action-gh-release@v2
+        with:
+          files: dist/*
+          generate_release_notes: true

chiefofstaff-0.1.0/.github/workflows/test.yml

@@ -0,0 +1,48 @@
+name: Test
+on: [push, pull_request]
+permissions:
+  contents: read
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.11", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+        with:
+          python-version: ${{ matrix.python-version }}
+      - run: uv sync --locked --extra dev
+      - run: uv run --locked --extra dev ruff check .
+      - run: uv run --locked --extra dev ruff format --check .
+      - run: uv run --locked --extra dev pyright
+      - run: npx --yes eslint@10.14.0 src/chiefofstaff/static
+      - run: uv run --locked --extra dev pytest -q
+
+  demo-ui:
+    # The whole product in a browser, with scripted sessions: no Copilot or Slack account.
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+        with:
+          python-version: "3.13"
+      - run: uv sync --locked --extra dev
+      - run: uv run --with playwright python -m playwright install --with-deps chromium
+      - run: uv run --with playwright python scripts/demo_smoke.py
+      - uses: actions/upload-artifact@v4
+        if: always()
+        with:
+          name: demo-screenshots
+          path: browser-shots/
+
+  secrets:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: gitleaks/gitleaks-action@v2
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

chiefofstaff-0.1.0/.gitignore

@@ -0,0 +1,13 @@
+.venv/
+__pycache__/
+*.py[cod]
+.pytest_cache/
+.ruff_cache/
+dist/
+*.egg-info/
+.env
+.env.*
+*.db
+*.db-*
+.DS_Store
+browser-shots/

chiefofstaff-0.1.0/CHANGELOG.md

@@ -0,0 +1,21 @@
+# Changelog
+
+## 0.1.0 (2026-11-02)
+
+First public release.
+
+- **Router** that splits requests into tasks, routes follow-ups to the worker that already
+  knows the subject, and asks you when it is unsure which project a task belongs to.
+- **Tasks and runs**: dependencies, reports, retries, cancellation and usage per task.
+- **Inbox**: what needs you, what is running, and results ready to review with **receipts**
+  (observed test runs, changes, commits and PR checks next to what the worker reported).
+- **Focus Shield**: notifications wait while you focus; one summary afterwards.
+- **Delegate by reaction**: react 🤖 to any Slack message to turn it into a task, answered
+  in its thread when done.
+- **Slack and GitHub**: replies and PR reviews drafted in your voice, sent only after you
+  approve; followed threads and PRs go straight to their worker.
+- **Watchdog** that notices stalled or looping workers and nudges them.
+- **Sandboxed workers** (Copilot's OS sandbox): writes only to their own folders, no access to
+  your keys, GitHub credentials through a proxy.
+- **Reliable delivery**: interrupted sends and drafts are checked before anything is resent.
+- **Demo mode** (`chiefofstaff --demo`): the whole product without any account.

chiefofstaff-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,11 @@
+# Code of Conduct
+
+This project follows the [Contributor Covenant, version 2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct/).
+In short: be kind, assume good intent, critique ideas rather than people, and make room for
+newcomers. Harassment and personal attacks are not tolerated, in issues, pull requests,
+discussions or anywhere the project is represented.
+
+Report unacceptable behavior privately to the maintainers through GitHub (the
+"Report content" option, or a private security advisory for anything sensitive). Reports are
+handled confidentially; maintainers may remove content and block participants who break this
+code.

chiefofstaff-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,126 @@
+# Contributing
+
+Thanks for helping. This page gets you from a clone to a merged change. The map of the code is
+[docs/ARCHITECTURE.md](docs/ARCHITECTURE.md); a list of well-scoped first changes is
+[docs/good-first-issues.md](docs/good-first-issues.md).
+
+## Set up
+
+You need Python 3.11+ and [uv](https://docs.astral.sh/uv/). A Copilot account is optional:
+most work needs none.
+
+```bash
+git clone https://github.com/evanl666/chiefofstaff && cd chiefofstaff
+uv sync --extra dev
+uv run chiefofstaff --demo          # the whole product, scripted, no accounts
+```
+
+## Tests
+
+| Command | What | Needs |
+| --- | --- | --- |
+| `uv run pytest -q` | Unit and scenario tests (fake and scripted backends) | Nothing |
+| `uv run --with playwright python scripts/demo_smoke.py` | The UI through the demo scenario, light and dark | `playwright install chromium` once |
+| `CHIEFOFSTAFF_TEST_COPILOT=1 uv run pytest -q -m copilot` | Contract tests against the real Copilot CLI | Copilot; a few small model calls |
+| `uv run python scripts/live_e2e.py` | Every feature end to end with real Copilot | Copilot; ~10 minutes of model use |
+| `uv run --with playwright python scripts/browser_smoke.py` | The UI with real Copilot | Copilot |
+
+Before a pull request:
+
+```bash
+uv run ruff check . && uv run ruff format --check . && uv run pyright && uv run pytest -q
+npx eslint@10 src/chiefofstaff/static     # the web UI
+```
+CI runs those, the demo browser test and a secret scan on every push.
+
+Write tests for behavior, not for implementation: a scenario through `tests/conftest.py`'s
+`Harness` (a fake Copilot you drive with `session.emit(...)`) is usually right. Failures at the
+worst moment belong in `tests/test_faults.py`.
+
+## Style
+
+- Code: `ruff` (100 columns) and `pyright` for Python, ESLint for the UI; all clean. Names say what things are; comments say why, not what.
+- Text the owner reads (UI, notifications, prompts): short, plain, specific. No exclamation
+  marks, no "successfully".
+- Keep the UI simple: plain HTML, CSS and JavaScript; no framework or build step.
+- One change per pull request, with a test. Say what changes for the owner.
+
+## Add an event source
+
+Teams, email, Linear, PagerDuty: a source watches something and hands new events to the
+runtime. Slack (`sources/slack.py`) and GitHub (`sources/github.py`) are complete examples.
+
+```python
+# src/chiefofstaff/sources/linear.py
+import asyncio
+
+from ..store import Store
+
+
+class LinearSource:
+    name = "linear"
+
+    def __init__(self, store: Store, host, client):
+        self.store, self.host, self.client = store, host, client
+        self.status = {"enabled": True, "connected": False, "error": ""}
+        self.job = None
+
+    async def start(self):
+        self.job = asyncio.create_task(self.loop())
+
+    async def stop(self):
+        if self.job:
+            self.job.cancel()
+
+    def wake(self):
+        pass
+
+    async def loop(self):
+        while True:
+            for issue in await self.client.assigned_to_me():
+                # A stable key per event: the same issue update never reaches the Router twice.
+                await self.host.on_trigger(
+                    "linear",
+                    [f"linear:{issue.id}@{issue.updated_at}"],
+                    f"New issue assigned to the owner: {issue.title}\n{issue.url}",
+                )
+            await asyncio.sleep(120)
+```
+
+Register it with `runtime.sources.append(LinearSource(store, runtime, client))` (in the
+runtime factory, or behind a setting). The Router receives the event in an envelope marked
+`trust="untrusted"`; tell it what to do with such events in `prompts.py` if the default
+judgment is not enough. To let sessions follow an item (comments go straight to the worker),
+add a thread key format in `threads.py` and call `host.on_thread(...)` for followed items, as
+`GitHubSource.poll_pull` does.
+
+## Debug a delivery
+
+Everything a session was sent is in the database. With Chief of Staff running (WAL mode lets
+you read it):
+
+```bash
+DB=~/Library/Application\ Support/chiefofstaff/chiefofstaff.db   # see "Data:" at startup
+sqlite3 "$DB" "select substr(id,1,8), role, status, title from sessions where closed_at is null"
+# A session's timeline; rows with meta.prompt are its outbox
+sqlite3 "$DB" "select id, kind, substr(text,1,60), substr(meta,1,80) from messages
+               where session_id like 'abcd1234%' order by id desc limit 20"
+# How far it was sent (sent:) and handled (idle:); a sending: key means a send was interrupted
+sqlite3 "$DB" "select key, value from kv where key glob 's*:abcd1234*' or key glob 'idle:abcd1234*'"
+# Tasks, runs and observed commands
+sqlite3 "$DB" "select id, status, title from tasks order by created_at desc limit 10"
+sqlite3 "$DB" "select run_id, kind, exit_code, substr(command,1,60) from commands order by id desc limit 10"
+```
+
+`copilot --resume <session id>` opens the same conversation in a terminal. To see the raw
+JSON-RPC traffic, wrap `copilot._jsonrpc.JsonRpcClient._send_message` and `_handle_message`
+in a small script (both take one message dict).
+
+## Pull requests
+
+- Describe the change from the owner's side, and how you tested it (paste the demo
+  screenshots for UI changes).
+- Keep pull requests small; open an issue first for anything that changes how sessions behave.
+- By contributing you agree that your contribution is licensed under the MIT license.
+
+This project follows the [Code of Conduct](CODE_OF_CONDUCT.md).

chiefofstaff-0.1.0/LICENSE

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

chiefofstaff-0.1.0/PKG-INFO

@@ -0,0 +1,158 @@
+Metadata-Version: 2.5
+Name: chiefofstaff
+Version: 0.1.0
+Summary: One inbox for all your GitHub Copilot sessions: tasks and follow-ups go to the right session, Slack replies wait for your approval, and finished work waits for your review.
+Project-URL: Homepage, https://github.com/evanl666/chiefofstaff
+Project-URL: Issues, https://github.com/evanl666/chiefofstaff/issues
+Author: evanl666
+License-Expression: MIT
+License-File: LICENSE
+Keywords: ai-agents,developer-tools,github-copilot,multi-agent,orchestration,slack
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Web Environment
+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
+Requires-Dist: fastapi<1,>=0.115
+Requires-Dist: github-copilot-sdk<1.1,>=1.0.28
+Requires-Dist: httpx<1,>=0.28
+Requires-Dist: keyring<26,>=25
+Requires-Dist: mcp<2,>=1.24
+Requires-Dist: platformdirs<5,>=4
+Requires-Dist: pydantic<3,>=2.10
+Requires-Dist: uvicorn<1,>=0.34
+Provides-Extra: dev
+Requires-Dist: httpx<1,>=0.28; extra == 'dev'
+Requires-Dist: pyright==1.1.414; extra == 'dev'
+Requires-Dist: pytest-asyncio<2,>=0.25; extra == 'dev'
+Requires-Dist: pytest<10,>=8; extra == 'dev'
+Requires-Dist: ruff<1,>=0.11; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# Chief of Staff
+
+**English** · [简体中文](https://github.com/evanl666/chiefofstaff/blob/main/README.zh-CN.md)
+
+One inbox for all your GitHub Copilot sessions. Tell it what you need. It gives each task to
+its own Copilot session, sends follow-ups to the session that already has the context, drafts
+your Slack replies, and lets you know when something is ready to review.
+
+![The inbox, with finished tasks waiting for review](https://raw.githubusercontent.com/evanl666/chiefofstaff/main/docs/images/inbox-review.png)
+
+Try it with scripted sessions first. No account needed:
+
+```bash
+uvx chiefofstaff --demo
+```
+
+## Why I built this
+
+I usually have several Copilot sessions going at once: one fixing a test, one reviewing a PR,
+one digging through logs. Every few minutes I'd flip between terminals to see which one was
+stuck, which one had a question, and which one had quietly finished. Slack kept pinging me in
+between. After a while I couldn't remember which session knew what, and I'd start a new one for
+a follow-up that an old one could have answered in a minute.
+
+Now I talk to one session, the Router, and Chief of Staff keeps track of the rest.
+
+## What it does
+
+- Splits a request into tasks. "Fix the flaky login test, then add rate limiting, and compare
+  feature-flag services" becomes three tasks. The second waits for the first and starts with
+  its result.
+- Sends follow-ups to the session that did the work, with its history and checkout, instead of
+  starting over in a new one.
+- Shows what was observed next to what the worker reports: the test runs, commits, diff and PR
+  checks. If a report says "all tests pass" and no test ran, the card says so.
+- Leaves your own checkout alone. Each worker gets its own folder and git worktree and runs in
+  Copilot's OS sandbox, so it can't write anywhere else.
+- Drafts replies to Slack DMs and mentions in your style. Nothing is sent until you press Send.
+- Lets you delegate from Slack: react 🤖 to any message ("can someone look at the export
+  bug?") and it becomes a task. When it's done, the answer is drafted in that thread.
+- Has a focus mode. Pick how long: notifications wait, the Router handles what it can, and you
+  get one summary at the end.
+- Watches for workers that stall or go in circles, and nudges them.
+
+It runs on the Copilot you already have: your plan, your models, your MCP servers and your
+company's policies. No other AI service or API key.
+
+![Approving a Slack reply](https://raw.githubusercontent.com/evanl666/chiefofstaff/main/docs/images/approve-dark.png)
+
+## Install
+
+You need macOS or Linux, Python 3.11 or newer, [uv](https://docs.astral.sh/uv/getting-started/installation/)
+(or pipx), and the [GitHub Copilot CLI](https://docs.github.com/en/copilot/how-tos/copilot-cli):
+
+```bash
+npm install -g @github/copilot
+copilot login
+uvx chiefofstaff            # or: pipx install chiefofstaff && chiefofstaff
+```
+
+Your browser opens `http://127.0.0.1:8765`. Add a project folder, then type what you need in
+the box at the bottom.
+
+Everything runs on your machine, and your data stays in `~/Library/Application Support/chiefofstaff`
+(macOS) or `~/.local/share/chiefofstaff` (Linux). Closing the tab doesn't stop anything; press
+Ctrl+C in the terminal to stop. Sessions continue where they left off when you start it again.
+
+Options: `--port`, `--data-dir`, `--no-browser`, `--demo`. To update: `uvx chiefofstaff@latest`
+or `pipx upgrade chiefofstaff`.
+
+## Signing in
+
+There are a few separate sign-ins. Only the first one is required.
+
+1. **Copilot.** Run `copilot login` once. If you haven't, the page tells you what to do. On a
+   company plan, an admin may need to turn on Copilot CLI for you.
+2. **The page itself.** Every start prints a private link with a fresh token in the terminal
+   and opens it for you. It stays signed in for 24 hours. After a restart, use the new link.
+   Keep it to yourself: whoever has it can act as you.
+3. **GitHub**, to review PRs you're asked to review: `gh auth login`. With the sandbox on, also
+   run `copilot sandbox ca create && copilot sandbox ca trust` once, so `gh` works inside it.
+4. **Slack and other services.** Paste a Slack user token in Settings
+   ([how to get one](https://github.com/evanl666/chiefofstaff/blob/main/docs/guide.md#slack)).
+   When a worker needs another service, like your docs or issue tracker, a sign-in card shows
+   up in the inbox.
+
+## How it works
+
+Every session is a regular Copilot CLI session. You'll find them in `copilot --resume`, named
+"Chief of Staff · …". Chief of Staff drives them through the Copilot SDK:
+
+```
+you ── inbox ── Router ── tasks ──► worker · worker · worker
+                  ▲                 (own folder, worktree, sandbox)
+Slack, GitHub ────┘    Slack session ──► drafts you approve
+                       Watchdog ──► nudges stuck workers
+```
+
+Sessions never talk to each other directly. They call tools like `spawn_worker`, `report` or
+`ask_session`, and Chief of Staff delivers the message. Each message is saved before it's sent
+and labeled with who it's from, so a Slack message can't pass itself off as you.
+
+- [User guide](https://github.com/evanl666/chiefofstaff/blob/main/docs/guide.md)
+- [Architecture](https://github.com/evanl666/chiefofstaff/blob/main/docs/ARCHITECTURE.md)
+- [Security](https://github.com/evanl666/chiefofstaff/blob/main/SECURITY.md): what the OS
+  sandbox enforces, what Chief of Staff enforces, and what relies on the model following
+  instructions.
+
+## Status
+
+Early (0.1). Expect rough edges. Copilot usage counts against your plan like any other
+session, and the inbox shows the credits each task used.
+
+Bug reports and ideas are welcome as issues. If you'd like to contribute, start with
+[CONTRIBUTING.md](https://github.com/evanl666/chiefofstaff/blob/main/CONTRIBUTING.md) and the
+[good first issues](https://github.com/evanl666/chiefofstaff/blob/main/docs/good-first-issues.md).
+
+## License
+
+MIT. Chief of Staff is an independent project, not made by or affiliated with GitHub. GitHub
+Copilot is a trademark of GitHub, Inc.

chiefofstaff-0.1.0/README.md

@@ -0,0 +1,121 @@
+# Chief of Staff
+
+**English** · [简体中文](README.zh-CN.md)
+
+One inbox for all your GitHub Copilot sessions. Tell it what you need. It gives each task to
+its own Copilot session, sends follow-ups to the session that already has the context, drafts
+your Slack replies, and lets you know when something is ready to review.
+
+![The inbox, with finished tasks waiting for review](docs/images/inbox-review.png)
+
+Try it with scripted sessions first. No account needed:
+
+```bash
+uvx chiefofstaff --demo
+```
+
+## Why I built this
+
+I usually have several Copilot sessions going at once: one fixing a test, one reviewing a PR,
+one digging through logs. Every few minutes I'd flip between terminals to see which one was
+stuck, which one had a question, and which one had quietly finished. Slack kept pinging me in
+between. After a while I couldn't remember which session knew what, and I'd start a new one for
+a follow-up that an old one could have answered in a minute.
+
+Now I talk to one session, the Router, and Chief of Staff keeps track of the rest.
+
+## What it does
+
+- Splits a request into tasks. "Fix the flaky login test, then add rate limiting, and compare
+  feature-flag services" becomes three tasks. The second waits for the first and starts with
+  its result.
+- Sends follow-ups to the session that did the work, with its history and checkout, instead of
+  starting over in a new one.
+- Shows what was observed next to what the worker reports: the test runs, commits, diff and PR
+  checks. If a report says "all tests pass" and no test ran, the card says so.
+- Leaves your own checkout alone. Each worker gets its own folder and git worktree and runs in
+  Copilot's OS sandbox, so it can't write anywhere else.
+- Drafts replies to Slack DMs and mentions in your style. Nothing is sent until you press Send.
+- Lets you delegate from Slack: react 🤖 to any message ("can someone look at the export
+  bug?") and it becomes a task. When it's done, the answer is drafted in that thread.
+- Has a focus mode. Pick how long: notifications wait, the Router handles what it can, and you
+  get one summary at the end.
+- Watches for workers that stall or go in circles, and nudges them.
+
+It runs on the Copilot you already have: your plan, your models, your MCP servers and your
+company's policies. No other AI service or API key.
+
+![Approving a Slack reply](docs/images/approve-dark.png)
+
+## Install
+
+You need macOS or Linux, Python 3.11 or newer, [uv](https://docs.astral.sh/uv/getting-started/installation/)
+(or pipx), and the [GitHub Copilot CLI](https://docs.github.com/en/copilot/how-tos/copilot-cli):
+
+```bash
+npm install -g @github/copilot
+copilot login
+uvx chiefofstaff            # or: pipx install chiefofstaff && chiefofstaff
+```
+
+Your browser opens `http://127.0.0.1:8765`. Add a project folder, then type what you need in
+the box at the bottom.
+
+Everything runs on your machine, and your data stays in `~/Library/Application Support/chiefofstaff`
+(macOS) or `~/.local/share/chiefofstaff` (Linux). Closing the tab doesn't stop anything; press
+Ctrl+C in the terminal to stop. Sessions continue where they left off when you start it again.
+
+Options: `--port`, `--data-dir`, `--no-browser`, `--demo`. To update: `uvx chiefofstaff@latest`
+or `pipx upgrade chiefofstaff`.
+
+## Signing in
+
+There are a few separate sign-ins. Only the first one is required.
+
+1. **Copilot.** Run `copilot login` once. If you haven't, the page tells you what to do. On a
+   company plan, an admin may need to turn on Copilot CLI for you.
+2. **The page itself.** Every start prints a private link with a fresh token in the terminal
+   and opens it for you. It stays signed in for 24 hours. After a restart, use the new link.
+   Keep it to yourself: whoever has it can act as you.
+3. **GitHub**, to review PRs you're asked to review: `gh auth login`. With the sandbox on, also
+   run `copilot sandbox ca create && copilot sandbox ca trust` once, so `gh` works inside it.
+4. **Slack and other services.** Paste a Slack user token in Settings
+   ([how to get one](docs/guide.md#slack)).
+   When a worker needs another service, like your docs or issue tracker, a sign-in card shows
+   up in the inbox.
+
+## How it works
+
+Every session is a regular Copilot CLI session. You'll find them in `copilot --resume`, named
+"Chief of Staff · …". Chief of Staff drives them through the Copilot SDK:
+
+```
+you ── inbox ── Router ── tasks ──► worker · worker · worker
+                  ▲                 (own folder, worktree, sandbox)
+Slack, GitHub ────┘    Slack session ──► drafts you approve
+                       Watchdog ──► nudges stuck workers
+```
+
+Sessions never talk to each other directly. They call tools like `spawn_worker`, `report` or
+`ask_session`, and Chief of Staff delivers the message. Each message is saved before it's sent
+and labeled with who it's from, so a Slack message can't pass itself off as you.
+
+- [User guide](docs/guide.md)
+- [Architecture](docs/ARCHITECTURE.md)
+- [Security](SECURITY.md): what the OS
+  sandbox enforces, what Chief of Staff enforces, and what relies on the model following
+  instructions.
+
+## Status
+
+Early (0.1). Expect rough edges. Copilot usage counts against your plan like any other
+session, and the inbox shows the credits each task used.
+
+Bug reports and ideas are welcome as issues. If you'd like to contribute, start with
+[CONTRIBUTING.md](CONTRIBUTING.md) and the
+[good first issues](docs/good-first-issues.md).
+
+## License
+
+MIT. Chief of Staff is an independent project, not made by or affiliated with GitHub. GitHub
+Copilot is a trademark of GitHub, Inc.