Agent Village

Access and setup

Explore the workflow. Know what it takes to start.

Agent Village's public pages introduce the team and explain a design-led route from an agreed goal to reviewable proof. The Workflow controls are a demonstration; they do not launch agents or publish a site.

Public source. Restricted hosted office. The Agent Village GitHub repository and issue queue are public. Anyone can read or clone the source without an invitation. A public clone does not grant hosted office access or authorize autonomous missions.
01

What you can explore here

The team demo uses sample activity to introduce the Village. The Workflow page explains the intended Maya, Susie, Sam, and Quinn handoffs. Its buttons only illustrate retry, cancellation, and reset behavior.

02

Start with a public clone

Browse the source and README and public issue queue, or clone it locally:

git clone https://github.com/startupsandcode/agent-village.git

A clone lets you inspect and adapt the source, run deterministic tests with fake providers, and run the local single-user interface. Follow the Windows and local setup guide or local interface guide.

  • The local interface needs Node.js 20.12 or newer. It does not require GitHub login or a GitHub token.
  • Live local projects require your own OpenAI or Anthropic API key and can incur provider charges. A ChatGPT subscription is not an API key. Set a provider spending limit before a live run.
  • The supported local flow clarifies a goal, plans, builds a bounded static website, reviews the files, and exports approved files. Submitting a goal starts a provider call; building requires a separate explicit action.
  • Export does not publish. GitHub and Vercel publication require separate credentials, target checks, and explicit actions.

For the Codex issue-to-PR workflow, use VS Code with Codex and authenticate to GitHub for issue or pull request actions. Work in your own fork or an authorized repository; public read access does not grant upstream push or merge permission. Agree on an issue and acceptance criteria before implementation.

03

The hosted office remains restricted

The hosted /office workspace and its private APIs require Vercel sign-in and an invited, verified email. Hosted runs additionally require operator authorization, server-side configuration, and explicit feature activation. Cloning the source, opening a public issue, or supplying a provider key grants none of these permissions.

This public site does not offer self-service hosted access or launch missions. Authorized operators should use the hosted office guide. Running your own local copy does not connect you to the hosted workspace or authorize work in another repository.