跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
设计与 UI

harness-integration-guide

Reference guide for building new Omnigent harness integrations — covers SDK/subprocess harnesses and native harnesses as separate tracks, each with their own feature matrix, implementation patterns, and prioritized checklist.

omnigent-ai · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add omnigent-ai/omnigent --skill harness-integration-guide

技能说明


name: harness-integration-guide description: Reference guide for building new Omnigent harness integrations — covers SDK/subprocess harnesses and native harnesses as separate tracks, each with their own feature matrix, implementation patterns, and prioritized checklist.

Harness integration guide

This skill describes the feature matrix every Omnigent harness must consider. Use it when planning, reviewing, or implementing a new harness.

Omnigent has two distinct harness tracks with different architectures and feature sets:

  • SDK/subprocess harnesses — run the vendor model directly (in-process SDK, CLI subprocess, or ACP subprocess). They own the model lifecycle.
  • Native harnesses — wrap a vendor's own TUI or server and mirror its output into Omnigent. They observe and relay, rather than drive.

Part 1 — SDK / subprocess harnesses

These harnesses run the vendor model directly and bridge Omnigent tools into the vendor's tool-calling interface.

Capability matrix

CapabilityWhat it means
Connects to Omnigent MCPHarness exposes/consumes tools via the MCP protocol (in-proc SDK MCP server)
Model overrideUser can select a model via --model / config; some harnesses are vendor-locked (e.g. Claude-only, GPT-only, Gemini-only)
AuthHow credentials are obtained — API key, gateway token, vendor CLI login, OAuth, etc.
StreamingHarness forwards token-level or delta-level streaming to the Omnigent forwarder
Omnigent policiesHarness enforces Omnigent-side tool policies — must support ALLOW, ASK, and DENY verdicts for both tool calls and tool results
Native elicitationWhen a policy verdict is ASK, the harness surfaces the approval request in the Omnigent web UI so the user can approve or deny
InterruptUser can cancel a running turn mid-stream
Live queue (concurrent)Multiple turns can be queued and processed concurrently
Tool-boundary steerOmnigent can inject steering text at tool-call boundaries
Resume/fork from Omnigent transcriptRebuild a conversation from a stored Omnigent transcript (replay history, seed prompt, or vendor session ID)
CompactionLong conversations are compacted; harness surfaces CompactionComplete events
ReasoningModel reasoning/thinking tokens are forwarded
ImagesImage content (screenshots, diagrams) is forwarded — full binary, path reference, or text-flattened
Cost trackingHarness reports token usage and cost data back to Omnigent for each turn

MCP connectivity

The harness must bridge Omnigent's builtin MCP tools so the model can call them. These tools provide session management, agent orchestration, policy control, and web access:

  • sys_session_get_info, sys_session_list, sys_session_get_history
  • sys_agent_get, sys_agent_list, sys_agent_download
  • sys_call_async, sys_cancel_async, sys_cancel_task
  • sys_read_inbox
  • sys_add_policy, sys_policy_registry
  • load_skill
  • list_comments, update_comment
  • web_fetch, web_search

Omnigent policies

The harness must support the Omnigent policy engine's three verdicts at two checkpoints:

CheckpointALLOWASKDENY
Tool call (before execution)Proceed silentlySurface approval request to user (via elicitation)Block the call and return a policy-denied error to the model
Tool result (after execution)Return result to modelSurface result for user review before returningSuppress the result and return a policy-denied error to the model

Native elicitation

When a policy verdict is ASK, the harness must surface the pending tool call or tool result in the Omnigent web UI as an approval card, then relay the user's approve/deny decision back to the harness to continue or block execution.

Resume / fork strategies

StrategyHow it works
Full history replayReplays the entire message history into a fresh thread/session
History prefix replayReplays a prefix of the history into a fresh session
Text-prefix replayInjects a text summary/prefix of prior history
Prompt seedingSeeds prior history into the system prompt on rebuild
Vendor session IDRelies on the vendor's own session persistence (no Omnigent-side rebuild)

Auth patterns

PatternDescription
API key / Databricks gatewayDirect API key or routed through a Databricks gateway
Vendor API key (direct)Vendor-specific API key (e.g. Cursor, Gemini)
Vendor CLI login / config fileCredentials stored in a vendor config file or managed via vendor CLI login
OAuth / GitHub tokenOAuth flow or platform token (e.g. GitHub PAT)
Gateway + fallbackPrimary gateway with fallback to vendor-native auth

Checklist for a new SDK/subprocess harness

All capabilities are required for a complete harness integration:

  • Connects to Omnigent MCP (in-proc SDK MCP server or vendor-specific bridge)
  • Model override works (or document vendor lock-in)
  • Auth is configured and documented (setup flow in omni setup)
  • Streaming forwards to the Omnigent forwarder
  • Omnigent policies enforce tool-use rules
  • Native elicitation surfaces tool-approval requests to web UI
  • Interrupt cancels the running turn
  • Live queue supports concurrent turns
  • Tool-boundary steering injects correctly
  • Resume/fork rebuilds conversation from Omnigent transcript
  • Compaction is surfaced (CompactionComplete events)
  • Reasoning tokens are forwarded
  • Images are forwarded (full binary preferred; path or text-flattened acceptable)
  • Cost tracking reports token usage and cost per turn
  • Unit tests cover tool bridging, auth, model routing
  • Mock LLM tests cover the happy path without real API calls

Shortcut: ACP CLI harnesses are one catalog row

If the vendor CLI

阅读完整来源 ↗