ForgeCode

ForgeCode is an independent, open-source fork of the legacy Kilo Code IDE codebase.

The project continues and reshapes that codebase as a community-maintained agentic coding assistant, with JetBrains IDEs as the first priority and PyCharm as the primary practical target. ForgeCode is not affiliated with, endorsed by, or maintained by Kilo Code or Kilo Code LLC.

Project status

ForgeCode is in an early transition phase. The legacy Kilo Code IDE codebase is scheduled to reach end of life on July 31, 2026, and this fork is being prepared as an independent continuation.

The repository still contains inherited Kilo, Roo Code, Cline, and related names in package metadata, source paths, assets, settings, services, and documentation. Some functionality may still depend on Kilo-controlled services or infrastructure until those paths are audited and replaced.

Why ForgeCode

ForgeCode exists to preserve and develop the useful parts of the legacy IDE agent system while moving toward:

• independent project governance and branding;
• provider-agnostic configuration with personal API keys;
• OpenRouter and OpenAI-compatible provider support;
• continued development of agents, modes, prompts, workflows, tools, and MCP integrations;
• a JetBrains-first development path, especially for PyCharm users.

Platform priorities

1. JetBrains and PyCharm

The first priority is making the JetBrains plugin usable, maintainable, and independently branded. The repository already includes a Kotlin JetBrains plugin and a Node.js host bridge for the inherited extension-host runtime.

2. VS Code

The VS Code extension remains part of the project and continues to provide the inherited extension runtime, UI, tools, modes, provider integrations, and .vsix packaging flow. It is the second consolidation priority after the JetBrains/PyCharm path is stabilized.

Current capabilities

The current repository includes working implementation areas for:

• chat-driven agentic coding workflows;
• built-in and custom modes;
• file, command, browser, and MCP tool access;
• multiple model providers, including OpenRouter and OpenAI-compatible configuration paths;
• MCP server management and MCP marketplace item handling;
• JetBrains IDE surfaces such as a tool window, editor context actions, terminal customization, inline completion services, and Git commit-message generation;
• the inherited VS Code extension UI and packaging flow.

These are existing codebase capabilities, not a guarantee that every path is fully ForgeCode-ready. Features connected to Kilo services, branding, or account flows remain transitional.

Development

ForgeCode development should focus first on the JetBrains/PyCharm plugin path.

Verified repository commands include:

pnpm jetbrains:build
pnpm jetbrains:run
pnpm jetbrains:bundle

General workspace commands are also defined:

pnpm install
pnpm build
pnpm lint
pnpm check-types
pnpm test

The local environment must provide the required toolchain before these commands can run. See DEVELOPMENT.md for the current development setup, verified repository commands, and known transitional limitations.

Roadmap

Planned work:

1. Stabilize the JetBrains/PyCharm startup, packaging, settings, and provider flows.
2. Replace public-facing Kilo branding with ForgeCode branding while preserving required attribution.
3. Reduce or remove dependency on Kilo-controlled hosted services.
4. Prioritize personal API keys, OpenRouter, and compatible provider configurations.
5. Preserve and improve the agent system: modes, prompts, workflows, tools, task persistence, and MCP integrations.
6. Consolidate the VS Code extension after the JetBrains/PyCharm path is usable and documented.
7. Update inherited documentation, metadata, assets, and release processes in small reviewable steps.

Roadmap items are planned work unless explicitly listed under current capabilities.

Independence and attribution

ForgeCode is an independent fork. It does not represent Kilo Code, Kilo Code LLC, Roo Code, Cline, or their maintainers.

ForgeCode is derived from the legacy Kilo Code codebase, which is itself derived from Roo Code and Cline and includes additional third-party work. Existing copyright, license, and attribution notices must be preserved.

Current upstream notices include:

• Original work: Copyright 2025 Cline Bot Inc.
• Modified work (Roo Code): Copyright 2025 Roo Veterinary Inc.
• Modified work (Kilo Code): Copyright 2025- Kilo Code LLC.
• Additional included software developed by Continue Dev, Inc., Copyright 2023 Continue Dev, Inc.

See NOTICE for the current notice file. Future ForgeCode changes should add ForgeCode attribution without removing required upstream attribution.

License

ForgeCode is licensed under the Apache License 2.0. See LICENSE.