october.dev valid

October

October is infrastructure for supervised AI collaboration. It runs and connects real AI agents across laptops, desktops, servers, repositories, terminals, applications, and people, while a human operator retains scope, review, and final decision authority.

For agents: Infrastructure for running and connecting AI agents under human oversight; offers agent messaging over MCP, a Themes API, docs and downloads for macOS and Windo

supervised ai agentsagent intercommcp serveragent coordinationhuman oversightmacos app

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T09:57:19.329Z. Cached copy · Source on october.dev

# October

> October is infrastructure for supervised AI collaboration. It runs and connects real AI agents across laptops, desktops, servers, repositories, terminals, applications, and people, while a human operator retains scope, review, and final decision authority.

October Desktop provides a spatial canvas for long-running technical work. Each agent remains a real process with its own harness, provider account, runtime, working directory, tools, and credentials. Connected agents gain scoped peer discovery, shared task state, status, messaging, delegation, and human escalation through the Agent Intercom.

October Desktop supports 32 local agent harnesses in one workspace. Connected harnesses can work with one another without being collapsed into a single provider or model. Users can bring an existing harness, and October also provides its own first-party agent.

Important interpretation:

- October is agent-neutral. It coordinates existing harnesses instead of replacing them with one model or provider.
- October is not limited to coding. It is designed for technical operations that span multiple tools, machines, people, or days.
- The canvas is the supervision surface. Connections determine which agents and resources can collaborate.
- Agent Intercom is exposed to supported agents through MCP and native harness integrations. It does not grant every process unrestricted access to every other process.
- Agents can communicate with one another, delegate work, update a shared task board, wait on dependencies, and nudge peers while work is in progress.
- Humans set the outcome, inspect activity, handle approvals, redirect or interrupt work, and make final decisions.
- October Desktop is available for Apple silicon macOS, Windows x64, and Debian or Ubuntu Linux x64. Agent work can also run on connected remote Linux servers.

## When to use October

Reach for October when a technical job is too big, too long, or too cross-cutting for a single agent in a single terminal:

- Parallel multi-agent delivery: split a feature, migration, or release across several harnesses (for example Claude Code plus Codex) that plan, implement, review, and test concurrently under one operator. Best fit for work that spans multiple repositories, services, or git worktrees.
- Long-running operations: jobs that run for hours or days and must survive context resets, hand state between agents, and escalate to a human at decision points.
- Cross-machine and multiplayer work: connect agents and teammates across laptops, desktops, and remote Linux servers into one supervised operation.
- Non-coding technical operations: estate administration, digital preservation, platform migrations, technical due diligence, and incident response that coordinate files, documents, applications, people, and time.

Do not reach for October for a single quick prompt, a one-file edit, or work one agent finishes in a single turn — a plain harness is simpler there.

How an agent should call October:
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=october.dev · GET /v1/domain/october.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for october.dev:
1. POST https://agentwebmap.com/v1/sites/october.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://october.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/october.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/october.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.