PRODUCT FEATURES · FACTS CHECKED 2026-09-08

Features around the agent, not only inside the prompt.

MonkeyCode is positioned as an AI development platform for engineering teams. Its product thesis combines requirements, tasks, environments, models, projects, desktop and mobile clients, and deployment choices into one managed workflow.

English translation of the original MonkeyCode task workspace screenshot, showing project navigation, the task input and task history.
The MonkeyCode task workspace

Original product image with English text. Interface and account values vary by version.

Documented capability map

Eight layers to evaluate.

These descriptions summarize public project materials; they are not performance, security, or compatibility guarantees.

MONKEYCODE / WORKFLOW

From a brief to a reviewable change

The model handles the task. The workspace gives it somewhere to work. You decide what to keep.

  1. Your brief

    Define the goal and allowed scope.

  2. Model + workspace

    Run the task with files, terminal and tests.

  3. Reviewable change

    Inspect the diff and verify the result.

01

Requirement and task management

Organize bounded AI work around requirements, projects, and task history rather than isolated prompts.

02

Server-side development environments

Run repository work with files, terminal, build, test, ports, and preview workflows in managed environments.

03

Desktop client with local agent (MonkeyWork)

Authorize a working directory and let the agent read, create, and modify local code, documents, and assets; a paired browser extension assists with web tasks.

04

Mobile follow-up

View task progress, continue conversations, and receive results on Android and iOS while tasks keep running.

05

Model management

Select from model families exposed by the current platform configuration; exact versions and routes must be verified.

06

Team visibility

Keep project and task context visible beyond one developer session.

07

Hosted or private deployment

Evaluate the hosted service or operate a documented private/offline deployment path.

08

Open-source codebase

Inspect and modify the public AGPL-3.0 codebase subject to its license terms.

Product tour

The managed workflow, in the official product images.

Official project screenshots. Interface details change by release; verify the version you evaluate.

MonkeyCode cloud terminal and task execution
Cloud terminal and task execution
MonkeyCode project collaboration and file management
Project collaboration and file management
MonkeyCode mobile and cross-device task management
Mobile and cross-device task management

Evaluation workflow

Trace a requirement to accepted evidence.

Public materials establish the components; your pilot must verify how completely they connect in the release you test.

  1. 01
    Define a bounded requirement

    Write acceptance criteria, repository scope, permissions, and prohibited actions.

  2. 02
    Create and execute an AI task

    Confirm environment startup, repository access, selected model, commands, and retained history.

  3. 03
    Build and test

    Keep command output, failures, retries, previews, and artifacts as review evidence.

  4. 04
    Review the change

    Inspect the diff and acceptance criteria. Verify branch, commit, and PR behavior rather than assuming automation.

Deployment distinction

Hosted and self-hosted move responsibility.

Do not assume identical features, models, integrations, operations, or security controls across deployment modes.

AreaHosted evaluationSelf-hosted evaluation
Platform operationProvider-operated serviceOrganization owns installation, capacity, upgrades, and recovery
Environment boundaryVerify provider behavior and termsVerify your hosts, network, isolation, and storage
Models and integrationsConfirm currently available configurationConfirm release support, credentials, routes, and provider terms
Security evidenceRequest current service evidenceTest configured controls and operational processes

Common questions

Features, answered.

Related: is it open source?, how it differs from editor tools, plans and pricing.

What can MonkeyCode do?
Documented capabilities include requirement and task management, server-side development environments, model management, team visibility, hosted or private deployment, a desktop client with a local agent (MonkeyWork), mobile follow-up, and an open-source AGPL-3.0 codebase.
Does MonkeyCode do code completion?
No. The hosted web app is not positioned as editor autocomplete; it coordinates bounded AI tasks in managed server-side environments. The desktop client adds a local agent for authorized directories — not an autocomplete layer. Editor-first tools cover in-IDE completion, and some teams use both.
Do MonkeyCode tasks run in the cloud?
The hosted service runs tasks in server-side development environments with build, test, and preview workflows — no local setup. The desktop client can also run a local agent on your machine and continue cloud tasks across devices.
Is MonkeyCode open source?
Yes. The public chaitin/MonkeyCode repository is licensed under GNU AGPL-3.0, so you can inspect and modify it subject to the license terms.
Are hosted, desktop, and self-hosted features identical?
Do not assume so. Where tasks run, local file access, browser pairing, mobile reach, and admin controls differ by mode; see the execution-mode boundaries on the product page and verify each in the mode you plan to use.
VERIFY THE SYSTEM

Move from capabilities to deployment evidence.

Cookie settings

We use cookies only for analytics (GA4 + Matomo) to improve the docs. No ads, no tracking across sites.