OpenClaw as a developer: A two-week experiment with isolated AI coding agents

A developer at an unnamed company built an autonomous "AI developer" on OpenClaw and ran it for two weeks in Slack, competing with Claude Tag. The setup runs on a 16 GB VPS, emphasizes security, and delegates all coding to external agents like Claude Code.

Key Setup Details

The AI operates in a heavily isolated environment:

• Configuration and context files are read-only, disabling self-learning.
• Internet access is restricted to an allowlist of domains.
• No access to deployed environments.
• It has its own GitHub and Linear accounts.
• Full codebase access, but runs in a fully mocked mode.
• Free to install NPM and Python dependencies as needed.

The workflow follows a spec → plan → execution pattern, same as the company's internal process. It always works in worktrees and dedicated feature branches, manually tests with dev servers (exposed on VPN for team review), and then opens PRs.

Open Source Components

The developer open-sourced the custom skill and CLI tool used to control the agent, and runs a personal instance for side projects. At work, the coding agent is Claude Code; personally, it's Codex.

The Author's Concern

After 30+ FTE days invested since February, the author heard Peter Steinberger say he reshaped OpenClaw into his own harness for building everything, including OpenClaw itself. That made him question whether disabling self-learning and delegating coding goes against OpenClaw's direction. If OpenClaw is moving toward coding on its own, is his project a dead end?