@wsz987/channel-harness

Thin Harness-native bridge between channel adapters and DeepSeek Harness agents/sessions.

This package is the only package allowed to import Harness public APIs. It turns ChannelEvents emitted by @wsz987/channel-core adapters into Harness sessions, routes them to the right agent, and streams assistant output back to the channel reply pipeline.

Install

pnpm add @wsz987/channel-harness

As a Cordis plugin:

- id: channels-harness
  name: '@wsz987/channel-harness'
  inject:
    - channels
    - agents
    - agentDefaultModel
    - agentPresets
    - llm
    - commands
    - apiProxy

Channel images follow the official Harness image pipeline: the bridge hands raw inbound image bytes to the Harness Attachment Store (attachments.saveImage -> ImageAttachmentRef -> real ImageBlock) and never rewrites messages for model compatibility. Whether the current model can see images (vision variant vs. deterministic text placeholder) is decided by Harness request projection, and the append-only session history keeps the original attachment reference.

What it does

| Area | Responsibility | | --- | --- | | SessionBinding / BindingStore | Binds platform conversations to Harness session ids (file-backed by default, survives restarts) | | AgentManager / AgentRouter | Resolves/creates the agent for a conversation via agent.default plus per-channel/account/conversation overrides | | MessageConverter | Maps structured ChannelEvent messages to Harness message types | | ReplyRouter / ReplyContextStore | Streams session/event output back to the adapter (ReplyHandle) | | ChannelQuestionPresenter (interactions/) | Presents ask_user_question requests through generic interactive actions. Web profile answers through the official ApiProxy mux contract; headless deployments register the channel as the official UserQuestionProvider (ctx.userQuestions) | | WorkspaceResolver | Maps conversations to Harness workspaces (channel-account by default) | | commands | Registers Agent-scoped slash commands (/new) through Harness CommandRuntime | | outbox | Proactive send_channel_message tool support (OutboxService) |

Model routing remains Harness-owned. A channel Session uses the model resolved at create/resume time from its request header, route options, or the shared agentDefaultModel. /model delegates the current-Session switch to the official Host RPC (or the official headless hook) and persists the same choice as the default for future Sessions. The bridge does not add a second owner or run a first-turn model preparation RPC.

Configuration

- id: channels-harness
  name: '@wsz987/channel-harness'
  inject: [channels, agents, agentDefaultModel, agentPresets, llm, commands, apiProxy]
  config:
    agent:
      default:
        preset: main
        provider: deepseek
        model: deepseek-chat
        maxTokens: 4096
    routing:
      mode: global            # global | channel | account | conversation
    bindingStore:
      type: file              # memory | file
    workspace:
      mode: channel-account   # channel-account | host-cwd | disabled
      autoCreate: true
    userQuestions:
      enabled: true
      timeoutMs: 300000
    reply:
      updateIntervalMs: 200
      splitParagraphs: true
      splitCodeBlocks: true
      finalFlush: true
    maxConcurrency: 4
    drainTimeoutMs: 5000
    includeMetadataPrefix: false

Routing priority when routing.mode is not global: conversation > account > channel > agent.default.

Development

pnpm --filter @wsz987/channel-harness build
pnpm --filter @wsz987/channel-harness typecheck
pnpm --filter @wsz987/channel-harness test

Related

• Repository root
• Architecture design

License

MIT