Repository Analysis

open-multi-agent/open-multi-agent

TypeScript AI agent orchestration framework with dynamic workflows. Describe the goal, not the graph: a coordinator plans the task DAG at runtime and runs it on any LLM (Claude, ChatGPT, Gemini, DeepSeek, or local models).

4.0 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of open-multi-agent/open-multi-agent, a TypeScript project with 6,580 GitHub stars. SynthScan v2.0 examined 74,994 lines of code across 260 source files, recording 200 pattern matches distributed across 8 syntactic categories. The overall adjusted score of 4.0 places this repository in the Likely human-written band.

The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).

4.0
Adjusted Score
4.0
Raw Score
100%
Time Factor
2026-07-12
Last Push
6.6K
Stars
TypeScript
Language
75.0K
Lines of Code
260
Files
200
Pattern Hits
2026-07-14
Scan Date
0.00
HC Hit Rate

What These Metrics Mean

Adjusted Score
Primary synthetic code indicator. Raw score normalised per 1,000 lines of code and multiplied by the temporal discount factor. This is the definitive comparative metric — use it to rank repositories by AI authorship density.
Raw Score
The unmodified sum of all severity-weighted, context-multiplied pattern match scores before temporal discounting. Reflects the absolute signal strength independent of when the repository was last active.
Time Factor
The temporal discount multiplier (0–100%) applied to the raw score. Repositories last updated before ChatGPT's launch (Nov 2022) receive a 5% factor. Full signal is only assigned to repositories active in the post-adoption era (Jan 2024+).
Pattern Hits
Total count of individual pattern matches across all files and categories. A high hit count with a low score may indicate a very large codebase with isolated AI snippets; a low count with a high score indicates dense, concentrated AI signatures.
HC Hit Rate
High+Critical pattern hits per file, averaged across the repository. This orthogonal signal catches repositories where a few files are densely packed with high-severity AI tells — a strong indicator even when the normalised score appears moderate due to codebase size.
Lines of Code / Files
Total lines and files analysed. The scanner examines 94 file extensions. These denominators are used to normalise the score, enabling fair comparison between repositories of vastly different sizes.

Score History

This chart maps the temporal evolution of the adjusted synthetic code score across successive scan runs. An upward trajectory indicates ongoing incorporation of AI-generated code or expanding LLM-assisted scaffolding; a stable or declining trajectory may reflect active human refactoring, code removal, or the adoption of stricter authorship policies. The dashed secondary line (right axis) independently tracks total raw pattern hit count, which can diverge from the normalised score when codebase size changes significantly between scans.

Severity Breakdown

Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.

CRITICAL 0HIGH 1MEDIUM 22LOW 177

Directory Score Breakdown

This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.

Pattern Findings

The scanner identified 200 distinct pattern matches across 8 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a statistically significant AI authorship indicator. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.

Reading the findings table: The Severity column indicates the diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.

Verbosity Indicators47 hits · 76 pts
SeverityFileLineSnippetContext
LOWpackages/core/examples/basics/multi-model-team.ts185// Step 1: researcher fetches the ratesCOMMENT
LOWpackages/core/examples/basics/multi-model-team.ts205// Step 2: analyst writes the briefing, receiving the researcher output as contextCOMMENT
LOWpackages/core/examples/patterns/fan-out-aggregate.ts118// Step 1: Fan-out — run all 3 analysts in parallelCOMMENT
LOWpackages/core/examples/patterns/fan-out-aggregate.ts148// Step 2: Aggregate — synthesizer reads all 3 analysesCOMMENT
LOW…ges/core/examples/patterns/cross-provider-reasoning.ts53 // Step 1: a reasoning-capable OpenAI model produces a turn that includesCOMMENT
LOW…ges/core/examples/patterns/cross-provider-reasoning.ts76 // Step 2: swap the model to Anthropic mid-conversation. WithoutCOMMENT
LOWpackages/core/examples/cookbook/contract-review-dag.ts46// Step 1: Agent configurations (4 agents)COMMENT
LOWpackages/core/examples/cookbook/contract-review-dag.ts127// Step 2: Task configurations (4 tasks)COMMENT
LOWpackages/core/examples/cookbook/contract-review-dag.ts143// Step 3: Progress trackingCOMMENT
LOWpackages/core/examples/cookbook/contract-review-dag.ts218// Step 4: Parallelism verificationCOMMENT
LOWpackages/core/examples/cookbook/contract-review-dag.ts247// Step 5: Orchestrator and Team configurationCOMMENT
LOWpackages/core/examples/cookbook/contract-review-dag.ts263// Step 6: Read contract textCOMMENT
LOWpackages/core/examples/cookbook/contract-review-dag.ts317// Step 7: Run the DAGCOMMENT
LOWpackages/core/examples/cookbook/meeting-summarizer.ts155// Step 1: Parallel fan-out with per-agent timingCOMMENT
LOWpackages/core/examples/cookbook/meeting-summarizer.ts205// Step 2: Parallelism assertionCOMMENT
LOWpackages/core/examples/cookbook/meeting-summarizer.ts223// Step 3: Aggregate into Markdown reportCOMMENT
LOW…/core/examples/cookbook/translation-backtranslation.ts229// Step 1: Agent A translatesCOMMENT
LOW…/core/examples/cookbook/translation-backtranslation.ts248// Step 2: Agent B back-translatesCOMMENT
LOW…/core/examples/cookbook/translation-backtranslation.ts265// Step 3: Agent C reviews semantic driftCOMMENT
LOW…ages/core/examples/cookbook/incident-postmortem-dag.ts42// Step 1: Agent configurations (5 agents)COMMENT
LOW…ages/core/examples/cookbook/incident-postmortem-dag.ts153// Step 2: Task configurations (5 tasks)COMMENT
LOW…ages/core/examples/cookbook/incident-postmortem-dag.ts169// Step 3: Progress trackingCOMMENT
LOW…ages/core/examples/cookbook/incident-postmortem-dag.ts244// Step 4: Parallelism verificationCOMMENT
LOW…ages/core/examples/cookbook/incident-postmortem-dag.ts275// Step 5: Orchestrator and Team configurationCOMMENT
LOW…ages/core/examples/cookbook/incident-postmortem-dag.ts314// Step 6: Read fixture filesCOMMENT
LOW…ages/core/examples/cookbook/incident-postmortem-dag.ts373// Step 7: Run the DAGCOMMENT
LOW…integrations/with-tencentdb-memory/team-with-memory.ts122// Step 1: recall long-term memory from previous runsCOMMENT
LOW…integrations/with-tencentdb-memory/team-with-memory.ts199// Step 2: run the team — shared-memory writes are captured into TDAMCOMMENT
LOW…integrations/with-tencentdb-memory/team-with-memory.ts239// Step 3: flush extraction so captures become searchableCOMMENT
LOW…integrations/with-tencentdb-memory/team-with-memory.ts253// Step 4: verify — search the distilled long-term memoriesCOMMENT
LOW…ore/examples/integrations/with-engram/research-team.ts167// Step 1: ResearchCOMMENT
LOW…ore/examples/integrations/with-engram/research-team.ts175// Step 2: Fact-checkCOMMENT
LOW…ore/examples/integrations/with-engram/research-team.ts184// Step 3: Write briefingCOMMENT
LOWpackages/core/src/llm/copilot.ts111 // Step 1: Request a device codeCOMMENT
LOWpackages/core/src/llm/copilot.ts128 // Step 2: Prompt the user via callbackCOMMENT
LOWpackages/core/src/llm/copilot.ts131 // Step 3: Poll for the user to complete authCOMMENT
LOWpackages/core/src/agent/runner.ts883 // Step 1: Call the LLM and collect the full response for this turn.COMMENT
LOWpackages/core/src/agent/runner.ts909 // Step 2: Build the assistant message from the response content.COMMENT
LOWpackages/core/src/agent/runner.ts995 // Step 3: Decide whether to continue looping.COMMENT
LOWpackages/core/src/agent/runner.ts1032 // Step 4: Execute all tool calls in PARALLEL.COMMENT
LOWpackages/core/src/agent/runner.ts1137 // Step 5: Accumulate results and build the user message that carriesCOMMENT
LOWpackages/core/src/orchestrator/orchestrator.ts2093 // Step 1: Coordinator decomposes goal into tasksCOMMENT
LOWpackages/core/src/orchestrator/orchestrator.ts2153 // Step 2: Parse tasks from coordinator outputCOMMENT
LOWpackages/core/src/orchestrator/orchestrator.ts2179 // Step 3: Auto-assign any unassigned tasksCOMMENT
LOWpackages/core/src/orchestrator/orchestrator.ts2184 // Step 4: Build pool and executeCOMMENT
LOWpackages/core/src/orchestrator/orchestrator.ts2297 // Step 5: Coordinator synthesises final resultCOMMENT
LOWpackages/core/src/orchestrator/orchestrator.ts2612 // Step 2: run proposer(s); accumulate usage and honour the budget before judging.COMMENT
Structural Annotation Overuse47 hits · 76 pts
SeverityFileLineSnippetContext
LOWpackages/core/examples/basics/multi-model-team.ts185// Step 1: researcher fetches the ratesCOMMENT
LOWpackages/core/examples/basics/multi-model-team.ts205// Step 2: analyst writes the briefing, receiving the researcher output as contextCOMMENT
LOWpackages/core/examples/patterns/fan-out-aggregate.ts118// Step 1: Fan-out — run all 3 analysts in parallelCOMMENT
LOWpackages/core/examples/patterns/fan-out-aggregate.ts148// Step 2: Aggregate — synthesizer reads all 3 analysesCOMMENT
LOW…ges/core/examples/patterns/cross-provider-reasoning.ts53 // Step 1: a reasoning-capable OpenAI model produces a turn that includesCOMMENT
LOW…ges/core/examples/patterns/cross-provider-reasoning.ts76 // Step 2: swap the model to Anthropic mid-conversation. WithoutCOMMENT
LOWpackages/core/examples/cookbook/contract-review-dag.ts46// Step 1: Agent configurations (4 agents)COMMENT
LOWpackages/core/examples/cookbook/contract-review-dag.ts127// Step 2: Task configurations (4 tasks)COMMENT
LOWpackages/core/examples/cookbook/contract-review-dag.ts143// Step 3: Progress trackingCOMMENT
LOWpackages/core/examples/cookbook/contract-review-dag.ts218// Step 4: Parallelism verificationCOMMENT
LOWpackages/core/examples/cookbook/contract-review-dag.ts247// Step 5: Orchestrator and Team configurationCOMMENT
LOWpackages/core/examples/cookbook/contract-review-dag.ts263// Step 6: Read contract textCOMMENT
LOWpackages/core/examples/cookbook/contract-review-dag.ts317// Step 7: Run the DAGCOMMENT
LOWpackages/core/examples/cookbook/meeting-summarizer.ts155// Step 1: Parallel fan-out with per-agent timingCOMMENT
LOWpackages/core/examples/cookbook/meeting-summarizer.ts205// Step 2: Parallelism assertionCOMMENT
LOWpackages/core/examples/cookbook/meeting-summarizer.ts223// Step 3: Aggregate into Markdown reportCOMMENT
LOW…/core/examples/cookbook/translation-backtranslation.ts229// Step 1: Agent A translatesCOMMENT
LOW…/core/examples/cookbook/translation-backtranslation.ts248// Step 2: Agent B back-translatesCOMMENT
LOW…/core/examples/cookbook/translation-backtranslation.ts265// Step 3: Agent C reviews semantic driftCOMMENT
LOW…ages/core/examples/cookbook/incident-postmortem-dag.ts42// Step 1: Agent configurations (5 agents)COMMENT
LOW…ages/core/examples/cookbook/incident-postmortem-dag.ts153// Step 2: Task configurations (5 tasks)COMMENT
LOW…ages/core/examples/cookbook/incident-postmortem-dag.ts169// Step 3: Progress trackingCOMMENT
LOW…ages/core/examples/cookbook/incident-postmortem-dag.ts244// Step 4: Parallelism verificationCOMMENT
LOW…ages/core/examples/cookbook/incident-postmortem-dag.ts275// Step 5: Orchestrator and Team configurationCOMMENT
LOW…ages/core/examples/cookbook/incident-postmortem-dag.ts314// Step 6: Read fixture filesCOMMENT
LOW…ages/core/examples/cookbook/incident-postmortem-dag.ts373// Step 7: Run the DAGCOMMENT
LOW…integrations/with-tencentdb-memory/team-with-memory.ts122// Step 1: recall long-term memory from previous runsCOMMENT
LOW…integrations/with-tencentdb-memory/team-with-memory.ts199// Step 2: run the team — shared-memory writes are captured into TDAMCOMMENT
LOW…integrations/with-tencentdb-memory/team-with-memory.ts239// Step 3: flush extraction so captures become searchableCOMMENT
LOW…integrations/with-tencentdb-memory/team-with-memory.ts253// Step 4: verify — search the distilled long-term memoriesCOMMENT
LOW…ore/examples/integrations/with-engram/research-team.ts167// Step 1: ResearchCOMMENT
LOW…ore/examples/integrations/with-engram/research-team.ts175// Step 2: Fact-checkCOMMENT
LOW…ore/examples/integrations/with-engram/research-team.ts184// Step 3: Write briefingCOMMENT
LOWpackages/core/src/llm/copilot.ts111 // Step 1: Request a device codeCOMMENT
LOWpackages/core/src/llm/copilot.ts128 // Step 2: Prompt the user via callbackCOMMENT
LOWpackages/core/src/llm/copilot.ts131 // Step 3: Poll for the user to complete authCOMMENT
LOWpackages/core/src/agent/runner.ts883 // Step 1: Call the LLM and collect the full response for this turn.COMMENT
LOWpackages/core/src/agent/runner.ts909 // Step 2: Build the assistant message from the response content.COMMENT
LOWpackages/core/src/agent/runner.ts995 // Step 3: Decide whether to continue looping.COMMENT
LOWpackages/core/src/agent/runner.ts1032 // Step 4: Execute all tool calls in PARALLEL.COMMENT
LOWpackages/core/src/agent/runner.ts1137 // Step 5: Accumulate results and build the user message that carriesCOMMENT
LOWpackages/core/src/orchestrator/orchestrator.ts2093 // Step 1: Coordinator decomposes goal into tasksCOMMENT
LOWpackages/core/src/orchestrator/orchestrator.ts2153 // Step 2: Parse tasks from coordinator outputCOMMENT
LOWpackages/core/src/orchestrator/orchestrator.ts2179 // Step 3: Auto-assign any unassigned tasksCOMMENT
LOWpackages/core/src/orchestrator/orchestrator.ts2184 // Step 4: Build pool and executeCOMMENT
LOWpackages/core/src/orchestrator/orchestrator.ts2297 // Step 5: Coordinator synthesises final resultCOMMENT
LOWpackages/core/src/orchestrator/orchestrator.ts2612 // Step 2: run proposer(s); accumulate usage and honour the budget before judging.COMMENT
Hyper-Verbose Identifiers46 hits · 43 pts
SeverityFileLineSnippetContext
LOWpackages/core/tests/tool-result-compression.test.ts54function buildErrorRegistryAndExecutor(): { registry: ToolRegistry; executor: ToolExecutor } {CODE
LOWpackages/core/tests/tool-result-compression.test.ts70function extractToolResultContents(messages: LLMMessage[]): string[] {CODE
LOWpackages/core/tests/checkpoint.test.ts116async function deleteNonCheckpointEntries(store: MemoryStore): Promise<void> {CODE
LOWpackages/core/tests/structured-output.test.ts194function buildMockAgentWithAdapter(config: AgentConfig, adapter: LLMAdapter): Agent {CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts396function extractGithubRepoFullNames(value: unknown): string[] {CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts425function textContainsNormalizedPhrase(text: string, phrase: string): boolean {CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts453function nonOfficialClaimNearTarget(text: string, target: string | undefined): boolean {CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts572function normalizeDatasetCandidate(raw: string, evidenceKind: DatasetEvidenceKind): string | undefined {CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts625function datasetEvidenceBaseConfidence(evidenceKind: DatasetEvidenceKind): number {CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts640function datasetEvidenceConfidence(CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts658function makeDatasetCandidateEvidence(CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts675function extractDatasetCandidateEvidenceFromText(CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts701function extractDatasetCandidateEvidenceFromPaths(paths: string[]): DatasetCandidateEvidence[] {CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts725function summarizeDatasetCandidates(CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts765function extractDatasetMentionsFromAstaSnippets(value: unknown): string[] {CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts922function buildDatasetCluesFromRepos(repoEvidence: Array<Record<string, unknown> | undefined>): Array<Record<string, unknCODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts1003function isUnavailableSourcePayload(value: unknown): boolean {CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts1033function hasSuccessfulSourcePayload(value: unknown): boolean {CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts1047function collectSourceEvidenceStrings(value: unknown, acc: string[] = []): string[] {CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts1073function hasReproductionFeedbackSignal(record: Record<string, unknown>): boolean {CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts1078function sourceHasReproductionFeedbackSignal(value: unknown): boolean {CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts1095function findDatasetRestrictionEvidence(text: string): string | undefined {CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts1141function extractedUnscopedEvidence(CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts1244function liveUnscopedEvidenceFields(CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts1317function summarizeRelationshipHints(value: unknown): string[] {CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts1333function scoreRepositoryForReplication(repo: Record<string, unknown>): number {CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts1382function compactRepositoryEvidenceForCodeAgent(repo: Record<string, unknown>): Record<string, unknown> {CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts1408function repoHasTrainingOrEvalPath(repo: Record<string, unknown>): boolean {CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts1427function repoHasUnofficialImplementationSignal(repo: Record<string, unknown>): boolean {CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts2567function assertPlannerDetectedConflicts(plan: ReplicationPlan, mode: SourceMode): void {CODE
LOW…ges/core/examples/cookbook/paper-replication-triage.ts2585function verifySourceTasksStartedTogether(resultTasks: readonly TaskExecutionRecord[]): void {CODE
LOWpackages/core/examples/cookbook/contract-review-dag.ts39function getAndIncrementAttempt(agentName: string): number {CODE
LOWpackages/core/src/llm/azure-openai.ts73function resolveAzureDeploymentName(model: string): string {CODE
LOWpackages/core/src/llm/anthropic.ts77function toAnthropicContentBlockParam(CODE
LOWpackages/core/src/llm/anthropic.ts206function fromAnthropicContentBlock(CODE
LOWpackages/core/src/llm/reasoning-fallback.ts124export function resolveReasoningOutboundMaxChars(CODE
LOWpackages/core/src/llm/reasoning-fallback.ts176export function reasoningBlockToInlineText(CODE
LOWpackages/core/src/llm/ai-sdk.ts51export function llmMessagesToAiSdkModelMessages(CODE
LOWpackages/core/src/llm/ai-sdk.ts174function buildLlmResponseFromGenerateText(result: {CODE
LOWpackages/core/src/agent/structured-output.ts21export function buildStructuredOutputInstruction(schema: ZodSchema): string {CODE
LOWpackages/core/src/agent/runner.ts321function stripImageBlocksForSummary(messages: LLMMessage[]): LLMMessage[] {CODE
LOWpackages/core/src/agent/runner.ts353function prependSyntheticPrefixToFirstUser(CODE
LOWpackages/core/src/cli/oma.ts353async function writeRunTeamDashboardFile(html: string): Promise<string> {CODE
LOWpackages/core/src/orchestrator/orchestrator.ts787function buildRevealCoordinatorLines(CODE
LOWpackages/core/src/orchestrator/orchestrator.ts801function prependRevealCoordinatorContext(CODE
LOWpackages/core/src/tool/mcp.ts108function assertUniqueNormalizedToolNames(CODE
Fake / Example Data27 hits · 36 pts
SeverityFileLineSnippetContext
LOWpackages/core/tests/context-strategy.test.ts296 const FILLER = 'lorem ipsum dolor sit amet '.repeat(50) // ~1.3k charsCODE
LOWpackages/core/tests/context-strategy.test.ts296 const FILLER = 'lorem ipsum dolor sit amet '.repeat(50) // ~1.3k charsCODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts58 ['anthropic', () => new AnthropicAdapter('dummy-key'), 'own-issued' as const],CODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts59 ['gemini', () => new GeminiAdapter('dummy-key'), 'own-issued' as const],CODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts60 ['openai', () => new OpenAIAdapter('dummy-key'), 'never' as const],CODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts61 ['azure-openai', () => new AzureOpenAIAdapter('dummy-key', 'https://example.openai.azure.com'), 'never' as const],CODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts62 ['copilot', () => new CopilotAdapter('dummy-token'), 'never' as const],CODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts63 ['deepseek', () => new DeepSeekAdapter('dummy-key'), 'tool-use-only' as const],CODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts64 ['grok', () => new GrokAdapter('dummy-key'), 'never' as const],CODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts65 ['qiniu', () => new QiniuAdapter('dummy-key'), 'never' as const],CODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts66 ['minimax', () => new MiniMaxAdapter('dummy-key'), 'never' as const],CODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts67 ['mimo', () => new MiMoAdapter('dummy-key'), 'tool-use-only' as const],CODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts68 ['hunyuan', () => new HunyuanAdapter('dummy-key'), 'tool-use-only' as const],CODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts81 const parent = new OpenAIAdapter('dummy-key').capabilitiesCODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts82 expect(new GrokAdapter('dummy-key').capabilities).toEqual(parent)CODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts83 expect(new QiniuAdapter('dummy-key').capabilities).toEqual(parent)CODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts84 expect(new MiniMaxAdapter('dummy-key').capabilities).toEqual(parent)CODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts93 expect(new DeepSeekAdapter('dummy-key').capabilities).toEqual({CODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts96 expect(new MiMoAdapter('dummy-key').capabilities).toEqual({CODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts99 expect(new HunyuanAdapter('dummy-key').capabilities).toEqual({CODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts102 expect(new DeepSeekAdapter('dummy-key').capabilities).not.toEqual(CODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts103 new OpenAIAdapter('dummy-key').capabilities,CODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts105 expect(new MiMoAdapter('dummy-key').capabilities).not.toEqual(CODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts106 new OpenAIAdapter('dummy-key').capabilities,CODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts108 expect(new HunyuanAdapter('dummy-key').capabilities).not.toEqual(CODE
LOWpackages/core/tests/llm-adapter-capabilities.test.ts109 new OpenAIAdapter('dummy-key').capabilities,CODE
LOWpackages/core/tests/hunyuan-adapter.test.ts48 const adapter = new HunyuanAdapter('dummy-key')CODE
Modern AI Meta-Vocabulary16 hits · 35 pts
SeverityFileLineSnippetContext
MEDIUMREADME.md92- **[CodingScaffold](https://github.com/JRS1986/CodingScaffold)** — Agentic-coding scaffold that lists OMA as an optionaCODE
MEDIUMREADME.md111│ └── core/ # @open-multi-agent/core — the published libraryCODE
MEDIUMREADME_zh.md100- **[CodingScaffold](https://github.com/JRS1986/CodingScaffold)** — agentic-coding 脚手架,把 OMA 列为可选编排后端,附带 `runTeam` 工作流模板CODE
MEDIUMREADME_zh.md119│ └── core/ # @open-multi-agent/core(发布的库)CODE
MEDIUMdocs/checkpoint.md180These are tracked as follow-ups: [#312](https://github.com/open-multi-agent/open-multi-agent/issues/312) (mid-task recovCODE
MEDIUMdocs/tool-configuration.md28**Custom / runtime tools are exempt from the grant requirement** — registering them _is_ the grant. Tools passed via `cuCODE
MEDIUMpackages/core/README.md59[Quick Start](#quick-start) · [Three Ways to Run](#three-ways-to-run) · [Features](#features) · [Orchestration Controls]CODE
MEDIUMpackages/core/README.md170| **Mix providers in one team** | 13 built-in providers plus any OpenAI-compatible endpoint (Ollama, vLLM, LM Studio, OpCODE
MEDIUMpackages/core/README.md259- **[CodingScaffold](https://github.com/JRS1986/CodingScaffold)** — Agentic-coding scaffold that lists OMA as an optionaCODE
MEDIUMpackages/core/README_zh.md170| **同队混用 provider** | 13 家内置 provider,外加任意 OpenAI 兼容端点(Ollama、vLLM、LM Studio、OpenRouter、Groq),同队可自由混用。将 tool call 作为纯文本输CODE
MEDIUMpackages/core/README_zh.md259- **[CodingScaffold](https://github.com/JRS1986/CodingScaffold)** — agentic-coding 脚手架,把 OMA 列为可选编排后端,附带 `runTeam` 工作流模板CODE
MEDIUMpackages/core/examples/README.md47## patterns — orchestration patternsCOMMENT
MEDIUMpackages/core/src/agent/agent.ts147 // External backend: it runs its own agentic loop, so none of theCOMMENT
MEDIUMpackages/core/src/agent/runner.ts848 // Main agentic loop — `while (true)` until end_turn or maxTurnsCOMMENT
MEDIUMpackages/create-oma-app/README.md15├── src/index.ts # the demo: one goal → multi-agent DAG → dashboardCODE
MEDIUMpackages/create-oma-app/README.md17├── package.json # one runtime dependency: @open-multi-agent/coreCODE
Decorative Section Separators6 hits · 18 pts
SeverityFileLineSnippetContext
MEDIUM…core/tests/e2e/coordinator-dependency-widening.test.ts151 // ── Bug cases: brief declarations must not be widened ──────────────────COMMENT
MEDIUM…core/tests/e2e/coordinator-dependency-widening.test.ts167 // ── Known-good: exhaustive declarations must still be fully wired ──────COMMENT
MEDIUMpackages/core/examples/providers/gemma4-local.ts102// ═══════════════════════════════════════════════════════════════════════════COMMENT
MEDIUMpackages/core/examples/providers/gemma4-local.ts104// ═══════════════════════════════════════════════════════════════════════════COMMENT
MEDIUMpackages/core/examples/providers/gemma4-local.ts155// ═══════════════════════════════════════════════════════════════════════════COMMENT
MEDIUMpackages/core/examples/providers/gemma4-local.ts157// ═══════════════════════════════════════════════════════════════════════════COMMENT
Over-Commented Block10 hits · 10 pts
SeverityFileLineSnippetContext
LOWpackages/core/tests/short-circuit.test.ts201 //COMMENT
LOWpackages/core/examples/basics/multi-model-team.ts101// ---------------------------------------------------------------------------COMMENT
LOW…ges/core/examples/patterns/cross-provider-reasoning.ts21 * Prerequisites:COMMENT
LOW…e/examples/cookbook/rare-disease-information-triage.ts501// Production source adapter sketchCOMMENT
LOW…examples/cookbook/narrative-puzzle-hint-arbitration.ts561// Lore: load from game CMS with versioned narrative contentCOMMENT
LOW…kages/core/examples/cookbook/competitive-monitoring.ts441//COMMENT
LOW…examples/integrations/with-vercel-ai-sdk/next-env.d.ts1/// <reference types="next" />COMMENT
LOWpackages/core/src/llm/deepseek.ts21 * by DeepSeek on 2026-07-24.COMMENT
LOWpackages/core/src/llm/ai-sdk.ts221 readonly name = 'ai-sdk'COMMENT
LOWpackages/core/src/llm/hunyuan.ts41 // continues a tool-calling conversation, otherwise the chain of thought isCOMMENT
Magic Placeholder Names1 hit · 5 pts
SeverityFileLineSnippetContext
HIGH…/examples/integrations/with-tencentdb-memory/README.md120 -e MODEL_API_KEY="your-api-key" \CODE