Skip to content

Campus Harness

Campus Harness is the system for building and customizing persistent, tool-using agents.

Agent components

An application package can declare:

  • Instructions and private context
  • A standard Agent skill package
  • App-specific context packs
  • Explicit worker roles and triggers
  • MCP tools it serves or consumes
  • Lifecycle, resource, model, and payment boundaries

The account’s Personal Agent keeps one persistent session and loads only the context and tools admitted for the current work. Create, fork, and runtime-tuning actions can start fresh isolated workers with target-specific workspaces, credentials, and grants.

Tools are the authority boundary

Instructions guide behavior; they do not grant capability. Every synchronous action still crosses an exact MCP schema, audience, permission, budget, payment, wake, and audit boundary.

Continue with MCP, workflows, background execution, and application packaging.

Software belongs to people. Campus gives it a durable place to run.