Getting startedSet up integrationsCreate your first initiativeInvite your teamPlan today's workShare your first update
Developer toolsMCPCLIAPI KeysREST APIJavaScriptJavaScript SDKOAuth AppsWebhooks
DocsAPI Reference

Main

  • Home
  • About
  • Pricing
  • Vault
  • Changelog
  • Docs

Features

  • Roadmaps
  • Planning
  • Standups
  • Status updates
  • Insights
  • AI assistant / MCP
  • Integrations

Solutions

  • Startups
  • Dev shops / agencies
  • Software teams
  • Internal IT & platform teams

Alternatives

  • vs Jira
  • vs Linear
  • vs Asana
  • vs Monday.com
  • vs ClickUp
  • vs Notion

Company

  • Blog
  • Security
  • Log in
  • Sign up
  • Terms of Use
  • Privacy Policy

Resources

  • Docs
  • Community
  • API reference
  • CLI
  • Desktop app
  • SDK

© 2026 One Horizon. All rights reserved

FacebookInstagramThreadsXRedditTikTokYouTubeMedium

Developer tools

Developer docs cover the surfaces you use to connect software to the workspace: MCP, CLI, API keys, REST API, JavaScript SDK, OAuth apps, and webhooks.

Agent execution has its own section. If you are sending work to an app, running local workers, building a local agent, or building a cloud agent, start with Agent workflows. For the product model behind those handoffs, use Spec-driven development. Use the API reference for endpoint schemas, request fields, response fields, and webhook event payloads.

Pick the right surface

SurfaceUse it for
MCPConnect AI assistants to workspace context and tools.
CLIWork from the terminal, inspect work, send items to coding tools, and run local Codex workers.
API KeysAuthenticate trusted server-side API and SDK calls for one workspace.
REST APIRead and update workspace data from services, scripts, and CI.
JavaScript SDKUse generated TypeScript clients and types from Node.js.
OAuth AppsAdd Log in with One Horizon or Connect One Horizon to an app that needs user-approved workspace access.
WebhooksNotify a service when workspace events happen.

Building an agent?

The same developer surfaces can support an agent integration: OAuth for user-approved workspace access, the REST API or SDK for calls, and webhooks for cloud notifications.

Keep the agent model in the Agents section. Use Build a Local Agent for private local execution, Build a Cloud Agent for an agent that stays online and can be shared by a team, and Agent Sessions for sessions, claims, activities, stale handling, and completion behavior.

Use the API reference when you need exact endpoints, schemas, webhook event types, or error shapes.

PreviousWindsurfNextMCP

Related Articles

Custom app

Build a custom integration with OAuth apps, webhooks, the REST API, and the JavaScript SDK.

Build Cloud

Build a cloud agent that stays online and can be shared by a team.

Build Local

Build a local agent that runs on your machine and claims your queued work.

Local Workers

Create and run a local Codex worker from Desktop or the CLI.

  • Pick the right surface
  • Building an agent?
  • Back to top