The ultimate harness for coding agents and beyond. All your agents. All your machines. One command center. Start with code, then follow your curiosity and build across disciplines: CAD, circuits, robots, games and music.
TypeScript 3d-modelingagent-frameworkagent-harnessai-agentscadclaude-codecodexcoding-agentsdeveloper-toolsesp32game-developmentmcp-servermulti-agentopen-hardwareopencodeopenharnesspcbroboticsterminaltmux
/**
* Agent Messages (`messages`), a service in the edge host: harnesses in one tab message each other with `harness
* send`, while the account has it on (Settings ▸ Experimental, off by default; messages/service.ts,
* docs/design/2026-10-10-agent-messages.md). Its typed deliveries go through `core.turns.deliver` under `team:` ids,
* which the core writes only into an idle, empty composer, and the core asks in line whether one may still be written
* (`canWrite`).
* - The `agent_messages` request: `harness send` in an agent's pane, the owner's other machines, the windows.
* - In the core's process (`HARNESSD_SERVICES=none`, or a subset without it) it starts here, at once; out of it,
* services/messagesProcess.ts starts the same service in the edge host.
*/
import type { CoreApi, CorePorts, ServiceRequests } from '../core/api.js'
import { startAgentMessages, type MessagesOptions } from '../messages/service.js'
/** The requests Agent Messages answers, declared in core/api.ts for the core to route. */
export { MESSAGES_REQUESTS } from '../core/api.js'
/** Agent Messages in the core's process (`HARNESSD_SERVICES=none`): its port is whether a delivery may be written. */
export function startMessagesInCore(core: CoreApi, ports: CorePorts, options: MessagesOptions = {}): ServiceRequests {
const messages = startAgentMessages(core, options)
ports.messages = Object.assign({ canWrite: (deliveryId: string) => messages.canWrite(deliveryId), settingsChanged: () => messages.settingsChanged() }, { stop: () => messages.stop() })
messages.start()
return messages.requests
}