Using Claude Code to Automate AI Research Experiments for 12 Hours

Automated AI Research with Claude Code
A developer documented using Claude Code to automate AI research experiments for 12 hours straight. The project focused on CLaaS, a real-time continual learning framework that moves context into weights using self-distillation.
Experimental Setup
The goal was to tune self-distillation training runs to maximize a model's compliance to different preference verifiers, such as concise responses and no emojis. Experiments ran locally on an RTX 5090 overnight.
System Architecture
The repository was built to be highly configurable:
- Every tunable parameter exposed via CLI using Hydra config management
- HTML dashboards for every training step and evaluation run
- Metrics, inputs, and outputs made observable through dashboards
- Claude Code could query dashboards via curl requests to check progress
Experiment Management
The workflow was controlled by a local EXPERIMENTS.md file with specific rules:
- Each experiment could change at most one variable or make one code change
- Between experiments, the model had to either accept or revert the previous change based on results
- Any new code changes had to be exposed via config for later tuning
- The model recorded all progress, hypotheses, and outcomes in the file as a running journal
- Used a "Ralph Wiggum loop" with the goal of maximizing preference compliance
Results
Over 12 hours, the system ran 9 experiments:
- Found and fixed a model collapse bug on the first run
- Tuned gradient steps per batch to 4
- Tuned learning rate to 3e-5
- Compliance improved from 0.000 to 1.000
- Token usage was surprisingly low because most time was spent waiting for training runs between experiments
The same task was also run with Codex for 2 hours using a plain prompt, and it independently converged on the same hyperparameters.
Project repository: https://github.com/kfallah/CLaaS
📖 Read the full source: r/ClaudeAI
👀 See Also

OpenClaw Agent Structure: 5 Core Files and 3 Practical Use Cases
An OpenClaw user found that all agents are built from five core files: User, Soul, Agent, Tools, and Identity. They shared three working agents including a daily AI briefing aggregator, a math coach for children, and a YouTube Shorts generator.

13 Weeks with OpenClaw as Daily Driver: What Worked, What Broke, What Still Hurts
After 13 weeks running OpenClaw on a Raspberry Pi as a personal agent system, a user shares practical wins (cron, memory, subagents) and pain points (model config issues, shell quoting, agent-to-agent history gaps, update drift).

Using a VM with OpenClaw for direct file access and faster iteration
Running OpenClaw in a virtual machine allows developers to directly view, read, edit project files like AGENTS.md and HEARTBEAT.md instead of working exclusively through chat interfaces. This approach speeds up iteration cycles significantly.

Homelab AI Dev Platform: OpenCode + GitOps for Safer Container Updates
A dev sets up OpenCode with Git access, PR review gate, and GitOps deployment for safer homelab container updates. AI writes changes, owner reviews via PR, Arcane deploys.