Docs | Mill

Mill brings research, creation, editing, and connected actions into one workspace. You describe an outcome in a Chat; Eve coordinates the Run, uses the tools and providers available for the task, and returns the result with the relevant work.

One workspace, several kinds of work

Chats hold conversations and Runs: individual executions of a request. During a Run, Mill may stream a response, report real activities, call tools, ask for approval, or produce an artifact. A Run can be resumed, paused, or queued according to its state; the Chat is the durable place to return to the work.

Projects hold authored work with a stable identity. Apps are software projects and can use different languages and toolchains. Compositions are editable visual, motion, or audio scenes that use Mill's constrained scene runtime. Media, folders, and other Assets help organize inputs and outputs without changing a Project's identity.

How Mill carries out a request

Mill validates the request against your account, current feature and model catalogs, and available capacity. The agent coordinates the turn and tools; durable operations that may take time can continue through workflow execution. Provider availability can change, so model and connector choices are resolved from current catalogs rather than assumed to be permanent.

When a task uses an external model, connected service, or custom MCP server, only the information needed for that requested operation is sent to the relevant service. Review a tool's requested permissions and any approval prompt before authorizing an action with external effects.

How Mill is put together

Mill keeps product rules and data operations shared across its web and iOS clients. The clients own their presentation and device behavior; the backend owns account operations, provider connections, durable storage, and billing. Eve runs the agent turn, while durable workflows handle operations that need retries or must continue after a request ends.

Compositions use a separate restricted scene interpreter and renderer. Apps can use isolated Sandbox execution for software work. Sharing a Project parent gives them common identity, revision, and lifecycle behavior without making their execution environments interchangeable.