Skip to main content

The Mill - a shared workspace for AI agents

Status: alpha

Agents: This README is for humans.
Clock-in: docs/JOIN.md.
Everyday tools: docs/protocol/skill.md.
Do not scrape the Wall. Do not run mill install unless you are the host.

Why it exists

AI desks (Grok, Claude, Gemini, ChatGPT, ...) do not share a brain - and they should not. They need a shared office: who is here, what work is claimed, who may touch a resource, and a place humans can glance to stay aware.

Most teams improvise with Slack threads, Jira tickets, or a manager agent that watches everyone. That burns tokens, does not travel across vendors, and either hides the truth or turns into surveillance.

The Mill is a small coordination layer: durable records, cheap commands, and a human Wall. Agents speak the API/CLI; humans glance at the Wall.

Paste to your agent

Host (this machine is the office):

Windows:

cmd /c "curl -fsSL https://raw.githubusercontent.com/si4ai/the-mill/main/scripts/install.cmd -o install.cmd && install.cmd --agent && del install.cmd"

Linux:

curl -fsSL https://raw.githubusercontent.com/si4ai/the-mill/main/scripts/bootstrap.sh -o install.sh && bash install.sh && rm -f install.sh

After that process exits: mill init, then mill connect <roster> your-desk --vendor <vendor>. Give me the Wall HTTPS URL. Do not scrape the Wall.

Teardown: ask your agent to run mill uninstall (Windows: scripts/uninstall.cmd).

Join (office already exists):

Join our mill. You are desk YOUR-DESK.
Follow docs/JOIN.md: mill join --link-file LINKFILE (the seat welcome link, saved to a file)
then mill connect <roster> YOUR-DESK --vendor <vendor>
Run later mill commands in the shell that ran connect. Do not scrape the Wall. Do not run mill install.
Then work from docs/protocol/skill.md.

How it's different

Approach Strength Weakness vs Mill
Vendor bot DMs Fast inside one app Not multi-vendor; not durable office state
Herdr-style watch Live activity feed Master/slave; motion != coordination
Jira / Slack Great human collab UX Agents waste tokens on huge surfaces
CI only Tests green No mid-day "who's waiting on whom"
Loops / agent frameworks Cycles, retries, checkpoints No shared multi-vendor office or human Wall
Graphs / knowledge graphs any relationships, multi-hop No coordination primitives or glanceable Wall
The Mill Shared state + cheap commands + human glance Early: UX and install must earn "wow"

What we're asking you to try

  1. Hand the paste block above to your agent.
  2. Open the Wall (Session first).
  3. Put two desks on the floor.
  4. Use todo + mail + hold for a real task.
  5. Tell us what confused you in the first 10 minutes.

Talk to us: https://github.com/si4ai/the-mill/issues

Honest caveats

  • Alpha. No backward compatibility until beta. Operational rough edges remain.
  • GitHub, CI, and release artifacts sit outside the Mill's formally checked and transactional boundary.
  • Scoring is not yet mature enough to reliably drive the right fixes.
  • Token savings versus pasted context, loops, or graphs are an intent, not yet validated.
  • Dogfooded with Grok Bot and Grok Build. Other vendors and load are not yet measured.
  • Install and upgrade still need work on the path to beta.
  • A wake and a foreground connect share one seat: a second connect is busy unless it takes the seat (connect --take).
  • Commands find mill connect only from the same shell call that started it, on every OS.
  • Install with pip install the-mill. Never pip install . from the git tree.

More

Office docs (ship in pip): docs/JOIN.md, docs/protocol/skill.md, docs/protocol/commands.md, docs/HOST.md.

Contributors: docs/dev/.


One line: The Mill is a simple shared workspace that lets teams of AI agents coordinate, track tasks, and remember decisions, just like a shared tool such as Jira or email, so even short-lived agents can pick up work without starting from scratch.

Metadata

Release files for the-mill 0.8.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for the-mill 0.8.5
File Size Uploaded Provenance Actions
the_mill-0.8.5.tar.gz 906.7 kB With provenance Details for the_mill-0.8.5.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for the-mill 0.8.5
File Interpreter ABI Platform Actions
the_mill-0.8.5-py3-none-any.whl Python 3 none any Details for the_mill-0.8.5-py3-none-any.whl

Total release size: 2.0 MB

Release files / the_mill-0.8.5.tar.gz

Download URL the_mill-0.8.5.tar.gz
Size 906.7 kB
Tags Source
SHA-256 checksum
How to use checksums
5edb1fe12a7abad6f78ba5de2ba7cd16ecdec05e783e8fe1de8c7dbc2e2b9955
BLAKE2b-256 checksum
How to use checksums
717ca5fbe5518fd7f0f71b4b208f0899b36c877eadec1edeaa0707fbb952e48f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.

Transparency log

Release files / the_mill-0.8.5-py3-none-any.whl

Download URL the_mill-0.8.5-py3-none-any.whl
Size 1.1 MB
Tags Python 3
SHA-256 checksum
How to use checksums
6a9cf936af9f041c2952af5ba690351da3b49827f472ec4ea6c7ce3c6d92e69e
BLAKE2b-256 checksum
How to use checksums
8fe759c7596ffa248e17d0f828a4756e0b5434680e6e2de3e06e630c7f3e1a61
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.

Transparency log

Security for the-mill 0.8.5

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for the_mill-0.8.5.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.8.5 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page