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?
📖 Read the full source: r/openclaw
👀 See Also
How I reduced OpenClaw costs by 60% through model routing
An OpenClaw user cut API costs from $420 to $168 in 20 days by analyzing usage patterns and routing tasks to appropriate models instead of using Claude Opus for everything. The breakdown showed 70% of tasks were simple and could use cheaper models.
Mass Parallelizing Claude Code: Lessons from Building a 220K-Line App
A developer with no formal coding background built a full-stack mobile app using Claude Code, running 3-4 parallel instances to process 4 billion tokens across 500+ files. Key techniques include handoff documents, CLAUDE.md files, custom slash commands, and systematic codebase audits.
ALTWORLD: A Persistent Life-Sim Architecture That Separates LLM from Database to Solve AI Amnesia
ALTWORLD is a stateful simulation game that addresses the context window problem by storing canonical run state in PostgreSQL tables and JSON blobs, then generating narrative text only after state changes. The architecture uses Next.js App Router, Prisma, and PostgreSQL with strict separation between simulation logic and AI narration.
Debugging a Tiny AI Agent on an Old Nokia Phone: 18 Attempts to Success
A developer documented 18 failed attempts to run Picobot, a ~12 MB AI agent, on an old Nokia phone via Termux, testing free models, OpenRouter, and Groq before settling on Google's Gemini Flash API for a fast, reliable setup.