Back to directory

OMA

A self-hosted TypeScript agent runtime where consequential actions wait for durable, tamper-evident approval and every run leaves an offline-verifiable record.

OMA

OMA (Open Multi-Agent) lets an organization run its own agents rather than depend on a hosted control plane, connecting to cloud or local models such as Ollama, vLLM, or llama-server. A plan, task dispatch, or tool call can suspend for approval; the request is stored with the checkpoint, bound to a hash of exactly what the reviewer saw, and the run resumes from that content after a restart, with a decision that is atomic and first-wins.

A journal backend records every block the model saw, every tool call and result, and every context rewrite, and a verification function reads that journal back offline and checks that each recorded event matches its named source.

OMA runs single agents, explicit task pipelines, or goal-driven teams, and is written in TypeScript under the MIT license.

More in Agent frameworks

See all 902
  • Recurse

    recurse.run

    A serverless harness that lets a coding agent design, test, and deploy its own specialist sub-agents as tools, MCP servers, or bots, defined by a schema-validated manifest.

  • ProofForge

    shulgin.is-a.dev

    An AI-agent pipeline that decomposes a mathematics problem, proves each piece, and formalizes the result in Lean 4 and Mathlib until the Lean kernel accepts it, with six of its proofs already merged into Google DeepMind's formal-conjectures repository.

  • local-coder

    github.com

    Builds a local coding-agent team on top of Ollama and OpenCode by detecting the machine's hardware, recommending models for seven specialist roles, and testing whether each assigned model can actually use tools, edit a repository and pass verification.