HashMo InteractiveOpen source · standing AI teams
APACHE-2.0 REFERENCE IMPLEMENTATION

OpenSourceConnector

AI teams that remember.Architecture anyone can build on.

OpenSourceConnector is a working reference pattern for standing, long-horizon multi-agent teams: provider APIs instead of browser automation, durable tiered memory, human-controlled approvals, and coordination that survives individual sessions.

Repository launch statusThe repository is intentionally private during launch preparation. This same GitHub URL becomes publicly accessible on launch day.
Apache-2.0Provider neutralMock quick startNo browser automation
opensourceconnector / team-runtime
TEAM
researcherbuilderreviewer
HOTCurrent sessionsAppend-only events
WARMWorking summariesLinked provenance
COLDDurable milestonesHuman-reviewed memory
requestapprovaloutcome

$ npm run setup

$ npm run serve

team online at 127.0.0.1:3847

The pattern

Not more agents for one prompt. A team that can keep working.

Most orchestration demos assemble several models for a single difficult query and then disappear. OSC addresses the longer problem: identity, memory, coordination, safety, and evidence across days and weeks.

API

API-native agents

Every teammate is reached through a provider's real API or a compatible local endpoint. No injected keystrokes, desktop control, or fragile browser automation.

MEM

Tiered, verifiable memory

Hot events, Warm summaries, and Cold milestones keep context durable while provenance shows where important memory came from.

HITL

Human-controlled safety

Ask, Auto, and Blocked policies make consequential work inspectable. Pending actions do not execute until a human approves them.

MCP

Open tool surface

The browser workspace and MCP endpoint expose the same organizational runtime so compatible clients can inspect and coordinate the team.

Start without an API bill

Run the complete pattern with the mock provider.

The public reference implementation includes a deterministic practice provider, example agents, browser UI, memory, approvals, and MCP. Live provider keys are optional.

  • Clone or download the repository after launch
  • Install and build with one setup command
  • Run the delivery-vs-outcome example
  • Open the local browser workspace
PowerShell / terminalQUICK START
npm run setup
npm run example:delivery-fixed
npm run serve
Browser UI + MCP · http://127.0.0.1:3847

Honest scope

A reference implementation, not a support contract.

OpenSourceConnector is published as a working architectural pattern. Fork it, study it, change it, and build on it. HashMo is not promising an open-source maintenance SLA, issue-triage schedule, or commercial support for this edition.

OPEN REFERENCE

What it gives builders

  • Standing multi-agent team runtime
  • Tiered memory and consolidation
  • Human approval and audit patterns
  • Browser UI and MCP endpoint
  • Provider adapters and local mock mode
  • Apache-2.0 source code
NOT THE CLAIM

What it does not promise

  • Proof of subjective AI continuity
  • A managed cloud service
  • Guaranteed provider availability
  • Browser or desktop automation
  • An ongoing maintenance roadmap
  • Commercial support or licensing

Two editions, different promises

Learn from the open pattern. Run organizations with OSC Pro.

OPEN SOURCE

OpenSourceConnector

Apache-2.0 reference implementation for developers, researchers, and teams exploring durable multi-agent architecture.

Repository opens at launch ↗
COMMERCIAL PRODUCT

OSC Pro

The full HashMo operating environment for AI organizations, with expanded providers, projects, missions, workspace documents, voice, health, scheduling, Slack, and governed external work.

Explore OSC Pro →

Open on launch day

Build on the pattern. Keep the architecture honest.

Read the limitations first, run the mock example, and treat every external action as a real trust boundary.

github.com/hashmoofficial-oss/OpenSourceConnector