MCPcopy
hub / github.com/OpenHands/OpenHands

github.com/OpenHands/OpenHands @cloud-1.40.0 sqlite

repository ↗ · DeepWiki ↗ · release cloud-1.40.0 ↗ · compare 2 versions
12,676 symbols 51,885 edges 2,101 files 6,219 documented · 49%
README

OpenHands logo

<strong>The self-hosted developer control center for coding agents and automations.</strong>






Run OpenHands, Claude Code, Codex, Gemini, or any ACP-compatible agent across local, remote, and cloud backends.

Project status beta CI status npm version Documentation Join us on Slack

Quickstart | Docs | Self-Hosting | ACP Agents | Automations | Slack

Agent Canvas automation preview


OpenHands Agent Canvas turns your coding agents into a self-hosted, always-on engineering team. It's a developer control center for starting conversations and automating everyday tasks — like generating reports that publish to Slack or automatically decomposing GitHub issues into tasks.

It runs locally on your machine by default, but can connect to multiple “agent backends”, e.g. running agents in Docker containers, on VMs, or within your company infrastructure. You can optionally choose to run agents on OpenHands Cloud or OpenHands Enterprise infrastructure.

Agent Canvas runs the open source OpenHands agent out-of-the-box, but can use any third-party agent like Claude Code and Codex.

Self-host your way Run agents locally, in Docker, on VMs, or anywhere you can run an agent server backend
Switch between different backends Switch between local, remote, and cloud agents without losing focus
Create automations Create automations and workflows that integrate with Slack, GitHub, Linear, and more. Run on a schedule or in response to webhook events
Integrate with the tools you use Connect your automations with third-party services like Slack, GitHub, Notion, and more to automate workflows
Bring your own model Use with any LLM
Use with any agent Use with OpenHands, Claude Code, Codex, Gemini, or any agent with Agent-Client Protocol (ACP).

If you have questions or feedback, please open a GitHub issue or join the #proj-agent-canvas channel in Slack.

[!NOTE] The code in this repo is moving! See Agent Canvas transition FAQ

The source code for OpenHands Agent and Agent Server lives in OpenHands/software-agent-sdk.

The source code for Agent Canvas lives in OpenHands/agent-canvas.

Quickstart

You can install OpenHands to run agents on any machine: on your laptop, on a dedicated computer like a Mac Mini, or on a server in the cloud.

The most powerful way to run OpenHands is on a server in the cloud. This allows your agents to continue running even when your laptop is shut, and makes it easier to trigger your agents through third-party services like Slack, GitHub, and Datadog. See the self-hosting guide for details, especially with respect to security hardening.

Notably, you can run the backend in multiple different environments, and switch between them from the same Agent Canvas frontend. E.g. you can share an Agent Server with your team for agents doing code review and dependency updates, then have your personal agents running on your laptop.

Option 1: Without a Sandbox

[!WARNING] This runs the agent-server directly on the machine you're installing on — the agent will have full access to your filesystem!

Prerequisites: Node.js 22.12.x or later, uv

npm install -g @openhands/agent-canvas
agent-canvas

The agent-canvas command starts the full local stack by default. You can also split it when you want to run pieces separately:

agent-canvas --frontend-only  # static frontend + ingress only
agent-canvas --backend-only   # agent server + automation backend + ingress only

Option 2: With a Docker Sandbox

Prerequisites:

  • Docker: Docker Desktop on macOS/Windows, or Docker Engine/Docker Desktop on Linux.
  • A host directory for PROJECTS_PATH containing the project folders you want the agent to access. Create it before starting the container.

macOS / Linux:

export PROJECTS_PATH="$HOME/projects"  # directory containing your project folders
mkdir -p "$PROJECTS_PATH" "$HOME/.openhands"

docker run -it --rm \
  -p 8000:8000 \
  -v "$HOME/.openhands:/home/openhands/.openhands" \
  -v "${PROJECTS_PATH}:/projects" \
  ghcr.io/openhands/agent-canvas:1.0.0-rc.11

Windows (PowerShell / Windows Terminal): See README.windows.md for the equivalent commands.

The agent will be able to access any project under PROJECTS_PATH.

Option 3: From Source

[!WARNING] This runs the agent-server directly on the machine you're installing on — the agent will have full access to your filesystem!

Prerequisites: Node.js 22.12.x or later, npm, uv (for running the agent server via uvx)

git clone https://github.com/OpenHands/agent-canvas.git
cd agent-canvas
npm install
npm run dev

Access the UI at http://localhost:8000. You can add additional backends directly from the UI.

Architecture

Agent Canvas is powered by the OpenHands Agent Server, a REST API for running multiple agents on a single machine. Each Agent Server runs on a single host/port; the Agent Canvas can connect to multiple Agent Servers and easily flip between them.

You can run an Agent Server anywhere:

  • Directly on your laptop (be careful!)
  • On a dedicated machine like a Mac Mini
  • On a virtual machine in the cloud
  • Inside OpenHands Cloud (our commercial offering)

The Agent Server is often paired with an Automation Server, which lets you set up agents that run on a schedule or in response to events.

image

More documentation

Extension points exported contracts — how you extend this code

BranchPage (Interface)
* V1 API response for paginated branch search (cursor-based)
frontend/src/types/git.d.ts
Props (Interface)
(no doc)
openhands-ui/components/select/react-select.d.ts
IOption (Interface)
(no doc)
openhands-ui/shared/types.ts
Window (Interface)
(no doc)
frontend/global.d.ts
ExtendedRenderOptions (Interface)
(no doc)
frontend/test-utils.tsx
ClickOutsideTestComponentProps (Interface)
(no doc)
frontend/__tests__/hooks/use-click-outside-element.test.tsx
RepositoryPage (Interface)
* V1 API response for paginated repository search (cursor-based)
frontend/src/types/git.d.ts
InstallationPage (Interface)
* V1 API response for paginated installation search (cursor-based)
frontend/src/types/git.d.ts

Core symbols most depended-on inside this repo

get
called by 928
openhands/app_server/settings/llm_profiles.py
warning
called by 399
frontend/src/utils/event-logger.ts
cn
called by 292
frontend/src/utils/utils.ts
error
called by 194
frontend/src/utils/event-logger.ts
renderWithProviders
called by 186
frontend/test-utils.tsx
a_session_maker
called by 171
enterprise/storage/database.py
filter
called by 123
openhands/app_server/utils/logger.py
displayErrorToast
called by 95
frontend/src/utils/custom-toast-handlers.tsx

Shape

Function 5,147
Method 4,842
Class 1,282
Interface 720
Route 674
Enum 11

Languages

Python78%
TypeScript22%

Modules by API surface

tests/unit/app_server/test_live_status_app_conversation_service.py172 symbols
enterprise/tests/unit/test_lite_llm_manager.py156 symbols
enterprise/tests/unit/server/routes/test_jira_dc_integration_routes.py155 symbols
enterprise/tests/unit/server/routes/test_orgs.py143 symbols
enterprise/tests/unit/server/routes/test_jira_integration_routes.py130 symbols
enterprise/tests/unit/integrations/jira_dc/test_jira_dc_manager.py99 symbols
tests/unit/app_server/test_remote_sandbox_service.py96 symbols
tests/unit/app_server/test_docker_sandbox_service.py90 symbols
enterprise/tests/unit/server/services/test_org_member_service.py90 symbols
tests/unit/test_issue_duplicate_scripts.py88 symbols
enterprise/tests/unit/test_slack_integration.py74 symbols
tests/unit/test_analytics_service.py73 symbols

Dependencies from manifests, versioned

@floating-ui/react0.27.12 · 1×
@heroui/react2.8.8 · 1×
@microlink/react-json-view1.27.1 · 1×
@monaco-editor/react4.7.0-rc.0 · 1×
@mswjs/socket.io-binding0.2.0 · 1×
@playwright/test1.58.2 · 1×
@react-router/dev7.15.0 · 1×
@react-router/node7.15.0 · 1×
@react-router/serve7.15.0 · 1×
@storybook/addon-a11y9.0.12 · 1×
@storybook/addon-docs9.0.12 · 1×

For agents

$ claude mcp add OpenHands \
  -- python -m otcore.mcp_server <graph>

⬇ download graph artifact