clodex-ide

本页保存的是公开项目资料快照，阅读过程不需要连接 GitHub。

CLODEx

One task. One durable engineering workspace.

图片：Website 图片：Community build 图片：CI 图片：License 图片：Node 图片：pnpm

CLODEx is an open-source, local-first agentic IDE for long-running engineering work. It keeps code, Git, terminal, browser, models, and MCP tools inside one durable desktop workspace, with approval and review surfaces for sensitive actions.

The source and the verified cross-platform Community Observed 21 Technical Preview are available for macOS, Windows, and Linux.

Download Community Observed 21 · See the Free product scope · Build from source · Русский обзор

Durable work	One engineering workspace	Models on your terms
Keep task history and recover work after restarts instead of rebuilding context from scratch.	Move between files, diffs, Git, terminal, browser, and MCP without leaving the task.	Sign in with CLODEx, bring your own provider key, use a compatible endpoint, or connect local Ollama.

Current Free Technical Preview: Community Observed 21 was built from exact canonical source d2dd2b63077c67255d60b8ab53f5c3c0995c7f84 by Actions run 30483341383, passed the enforced Free/managed and packaged-byte gates, and is published as the immutable v1.16.0-communityobserved21 prerelease on 2026-07-29. It is still unsigned/ad-hoc and not notarized; see the warning below before installing.

Community Observed 21 includes the manual release-discovery bridge first published in Community Observed 15. In Settings → About, Check for Updates performs a user-triggered, fail-closed release check and can open a newer immutable Community release page in the external browser. It never downloads or installs an update automatically.

Why CLODEx

Most AI coding interfaces are optimized for the next message. Real engineering work is longer: understand a repository, plan a change, edit multiple files, run commands, inspect the application, review the diff, recover from failure, and continue tomorrow.

CLODEx treats that work as a durable task rather than a disposable chat.

A chat-first workflow	CLODEx
Context is rebuilt from messages	The task retains its workspace and history
Tools feel like separate integrations	Files, Git, terminal, browser, and MCP share one workspace
A patch is the end of the interaction	Pending edits, diffs, command output, and review remain part of the task
One provider defines the workflow	Account-backed models, BYOK, compatible endpoints, and local models coexist
Automation is difficult to inspect	Sensitive operations can require explicit approval and remain reviewable

The product principle is simple:

Model output is input, not authority.

Free product scope

The following capabilities define the open, local Community product scope. Release notes remain the source of truth for what is present and accepted in a specific packaged artifact. Community Observed 21 is the current verified cross-platform Technical Preview.

Area	Free product scope
Durable tasks	Searchable task history, workspace-aware context, cancellation, restart recovery, and continued work across sessions.
Code and review	File editing, Pending Edits, line-level diffs, Git operations, worktrees, local commits, and pull-request review workflows.
Terminal and browser	Persistent local shell sessions, local ports, embedded browsing, console inspection, screenshots, and visual verification.
Models	CLODEx account integration, provider API keys, custom OpenAI-compatible endpoints, model selection, and local Ollama.
MCP	User-configured stdio and remote MCP servers, HTTP/SSE transports, OAuth flows, tools, resources, prompts, and approval-aware execution.
Account access	Secure CLODEx.xyz sign-in through the system browser with an RFC 8252 loopback callback, state, and PKCE S256.
Language and privacy	English and Русский (beta), plus a required first-launch allow-or-decline choice for optional product statistics.
Distribution	Community Observed 21 provides macOS Apple Silicon, macOS Intel, Windows x64, Debian/Ubuntu x64, and Fedora/RHEL x64 tester packages.

A typical workflow

1. Open a repository and start a task.
2. Ask CLODEx to explain, plan, implement, or review a change.
3. Let the agent inspect files and use approved local tools.
4. Review Pending Edits, line-level diffs, terminal output, browser state, and any permission requests.
5. Accept, revise, commit, or continue the same task later.

CLODEx is designed to keep the core engineering loop in one place, not to hide it behind a single “done” message.

Built for review

CLODEx keeps user control visible throughout the task.

Developer request
      ↓
Agent proposes a plan or action
      ↓
Permission and approval checks
      ↓
Local tool or integration executes
      ↓
Diffs, outputs, artifacts, and task history return for review

The public source includes explicit permission, approval, diff, and review surfaces. Read Security and data for the public security model and data-handling contract.

Proof, not promises

Claim	Public evidence
The Free/managed product boundary is explicit and must fail closed for Community packaging	Free Product Contract · boundary policy and CI checks in this repository
The current tester binaries come from one pinned public source revision and build run	Source d2dd2b63 · Actions run 30483341383
The current installers passed the enforced packaging boundary and byte audit	Community Observed 21 release · SHA256SUMS.txt · validation manifests and SBOMs in the evidence archive
The repository includes CI, provenance, contribution, and secret-scanning controls	GitHub Actions · DCO · security policy
The project documents its upstream lineage and redistribution obligations	CLODEx vs Stagewise · Third-party notices

The evidence archive intentionally distinguishes observed evidence from claims about external effects. A validation report proves what it actually checked; it does not turn a preview into a stable product.

Download Community Observed 21

The current Community Free Technical Preview is 1.16.0-communityobserved21, built from exact source d2dd2b63077c67255d60b8ab53f5c3c0995c7f84 by GitHub Actions run 30483341383, and published on 2026-07-29.

Platform	Package	Download
macOS Apple Silicon	ARM64 DMG	Download
macOS Intel	x64 DMG	Download
Windows	x64 EXE	Download
Debian / Ubuntu	x64 DEB	Download
Fedora / RHEL	x64 RPM	Download

Verify the selected installer with SHA256SUMS.txt. The evidence archive contains the platform validation manifests, CycloneDX SBOMs, warnings, internal bundle checksums, and the root byte-audit report. The checksum file covers the five unchanged installer assets and the evidence archive.

Unsigned Technical Preview: the macOS packages are ad-hoc signed, are not signed with a trusted Developer ID, and are not notarized. The Windows package is not Authenticode-signed. The Linux packages do not carry a CLODEx vendor signature. Verify SHA-256 and use only the operating system’s per-application review flow. Do not disable Gatekeeper, SmartScreen, Defender, or equivalent protections globally.

Install

• macOS: open the DMG for your architecture and drag CLODEx to /Applications.
• Windows: verify SHA-256, then run the x64 setup and review the SmartScreen warning for this individual application.
• Debian / Ubuntu: sudo apt install ./.deb
• Fedora / RHEL: sudo rpm -i .rpm

Report installation or testing problems through GitHub Issues or the support guide.

Connect your models

CLODEx supports four practical connection paths:

1. CLODEx account: sign in through CLODEx.xyz and use the keys and models available to that account.
2. Bring your own key: connect supported model providers directly.
3. Compatible endpoint: use a custom OpenAI-compatible API.
4. Local inference: connect Ollama, normally at http://localhost:11434.

For BYOK and custom endpoints, provider terms, availability, and charges remain between the user and the selected provider. Never include API keys, tokens, private source, or unredacted logs in a public issue.

Security and privacy

The Technical Preview is built around inspectable boundaries rather than invisible trust.

• Local-first workspace: task state and desktop tooling are local by default. Network access is used only by features and services the user selects, such as hosted models, account access, remote MCP, browser navigation, or opted-in statistics.
• System-browser authentication: CLODEx.xyz login uses state, PKCE S256, a one-time opaque code, and an exact loopback callback. Bearer tokens are not returned in the callback URL.
• Protected credentials: account and provider credentials use the application’s protected storage path rather than renderer-local storage.
• Reviewable actions: permission prompts, Pending Edits, diffs, and Git review surfaces let users inspect changes before commit or merge.
• Explicit statistics choice: Community Observed telemetry starts only after the user chooses allow or decline.
• Bounded pseudonymous events: when allowed, product statistics may include a pseudonymous installation ID, counters, bounded timing, enum values, and app/platform metadata. The Community Observed contract excludes prompts, messages, source code, commands, paths, URLs, API keys, tool arguments, error text, feedback text, session recording, and AI tracing.

Read Security and data. Report vulnerabilities privately through SECURITY.md, not through a public issue.

Preview scope

The capabilities listed in Free product scope define the baseline Community product contract. Source-tree experiments and feature-gated surfaces are not part of that baseline promise. Release notes are the source of truth for each published build. Community Observed 21 is the current verified Technical Preview; its release notes and evidence define its exact artifact scope.

Contributors can start with the repository map and architecture documentation.

Run from source

Requirements

• Node.js 22.23.1
• pnpm 10.30.3
• Git
• macOS, Linux, or Windows

Setup

git clone https://github.com/mereyabdenbekuly-ctrl/clodex-ide.git
cd clodex-ide

corepack enable
corepack prepare pnpm@10.30.3 --activate

cp .env.example .env
cp .env.example .env.dev

pnpm install --frozen-lockfile
pnpm build:packages
pnpm --dir apps/browser start:fast

Use the checked development command when type checking should run in parallel with Electron:

pnpm --dir apps/browser start

Environment and provider configuration are documented in local development. Never commit .env files, credentials, signing keys, or local runtime state.

Validation

Before opening a pull request:

pnpm check
pnpm typecheck
pnpm test
pnpm security:secrets

GitHub CI, release manifests, checksums, and attestations are the source of truth for published artifacts. Start with testing and release and VERSIONING.md.

Documentation

Goal	Document
Understand the product quickly	Product overview · Русский обзор
Run and develop locally	Developer handbook · Local development
Navigate the repository	Repository map
Review architecture	Architecture
Review security and data handling	Security and data · Security policy
Understand the current preview	Community Observed builds
Understand what the Free build includes	Community Free Product Contract
Understand project lineage	CLODEx and Stagewise
Contribute or collaborate	Contributing · Collaboration paths

Extending CLODEx

The repository contains integration surfaces for:

• MCP servers and OAuth-enabled remote MCP connections;
• reusable skills and context files;
• plugins and extension metadata.

Availability depends on the release channel. Review extensions and integrations and the current release notes before presenting an integration as generally available.

Project lineage

CLODEx began as a modified version of the open-source Stagewise codebase and has diverged into an independently maintained project focused on durable agent work, governed execution, model choice, integration boundaries, and release evidence.

The exact upstream base commit, reproducible diff method, CLODEx-specific systems, and continuing upstream-derived areas are documented in CLODEx vs Stagewise. Upstream copyright and license notices are preserved in Third-party notices. CLODEx is not affiliated with or endorsed by Stagewise.

Contributing

Contributions should be scoped, testable, and reviewable.

1. Read CONTRIBUTING.md.
2. Follow VERSIONING.md.
3. Sign commits according to the repository DCO.
4. Run formatting, type checking, tests, and secret scanning.
5. Include focused tests for changed behavior.

Bug reports, installation feedback, provider problems, documentation fixes, security reviews, and focused pull requests are welcome.

Maintainer and community

CLODEx is independently maintained by Merey Abdenbekuly.

• Website: ide.clodex.xyz
• Updates: X · @CLODEx_lab
• Testing and support: SUPPORT.md
• Governance: GOVERNANCE.md
• Code of conduct: CODE_OF_CONDUCT.md

If CLODEx is useful, support options are listed on the project website.

License

CLODEx is distributed under the GNU Affero General Public License v3.0. Third-party components retain their original licenses and notices.