Repo brief: YaoApp/yao

Generated by RepoPilot · document generated 2026-09-16 · concise human review Evidence snapshot · analyzed 2026-09-16T21:13:22.935Z · commit e208ea9d0d04

Verdict

Mixed — Single-maintainer risk — review before adopting

• Last commit 2d ago
• 2 active contributors
• CI configured
• Tests present

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

What it is

Yao Agents is a self-hosted, multi-device agent orchestration platform written primarily in Go that runs AI agents locally on your machines while managing them from a unified workspace. It lets you track agent tasks on a shared board, persist conversations into a knowledge base, and expose agent capabilities via standard APIs (SSE and WebSocket). The core system manages agent lifecycle, LLM integration, MCP protocol support, and persistent state across distributed nodes. Monorepo structure: agent/assistant/ contains the core assistant engine with LLM integration, MCP protocol support, and hook system; agent/assistant/hook/ implements a sophisticated hook/middleware pipeline for…

Start here

Open these first:

• agent/assistant/assistant.go — Core assistant orchestration logic that coordinates LLM interactions, hooks, and state management for agent workflows.
• agent/assistant/hook/hook.go — Hook system that enables extensible lifecycle callbacks (create, next, script execution) for assistant operations.
• agent/board/board.go — Task board abstraction providing kanban-style task management with columns and card templating.
• agent/caller/orchestrator.go — Process orchestration engine that manages execution flows, context passing, and agent invocation chains.
• agent/assistant/mcp.go — Model Context Protocol integration enabling tool/function calling and external service integration for agents.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

Clone: git clone https://github.com/YaoApp/yao.git && cd yao. Build: The Makefile is present but specific targets cannot be inferred from available evidence—verify the Makefile for build, test, and dev commands. No pa…

Daily commands:

Exact commands cannot be inferred—the Makefile exists but build targets are not detailed in evidence. Check cat Makefile for targets like make build, make dev, or make test. Go projects typically use `go build .…

…shortened for this brief.

Key cautions & unknowns

• Small team — 2 contributors active in recent commits
• Single-maintainer risk — top contributor 99% of recent commits
• Scorecard: default branch unprotected (0/10)
• No explicit go.mod evidence provided—verify Go version requirements and dependencies before building. MCP integration (mcp.go) requires understanding of the Model Context Protocol specification and its handshake.…
• License evidence is incomplete or ambiguous.
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests
• OpenSSF Scorecard

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.