← back to runpane.com

blog

the series

1.

Before Your First /discussion: The Repository Setup That Makes Everything Else Work

The repository setup that makes AI agent workflows actually work — monorepo structure, AGENTS.md, mechanical invariants, and the .claude directory that every agent session boots from.

2.

Two Founders, 300k Lines, Zero Engineers: Our AI-Native Development Workflow

The specific, repeatable process two non-traditional founders use to ship a 300k line Next.js monorepo with 3-6 AI coding agents running in parallel.

3.

How We Use Claude Code at Dcouple

The actual Claude Code workflow behind Pane: discussion, planning, implementation, worktrees, and the parts we refuse to automate away.

4.

Building a Software Factory: 3 Commands, Custom Agents, and the Harness That Runs It

How we built a repeatable software factory with Claude Code and Codex — three slash commands, custom agents, voice-first development, and the harness engineering that ties it all together.

5.

A Turing Award Winner Just Described Our Exact Workflow

Pat Hanrahan — Turing Award winner, GPU computing co-creator, Stanford professor — independently verified our exact development workflow: spec, read, verify.

6.

Same Chef, Six Hats: What a Viral Agent Post Gets Right and Wrong

A post comparing three Claude Code tools went viral. The author found the right layers but the wrong conclusion — three tools when three commands do the same job.

7.

The Cobbler's Children Have No Shoes

Claude Code's source code leaked. The company building the most popular AI coding agent ships code that violates every principle that makes codebases agent-readable.

8.

They Gated the Fix. We Open-Sourced the Whole Harness.

Anthropic built fixes for every way Claude Code breaks — hallucination, context decay, lazy fixes — then gated them behind an employee flag. We built the same fixes into an open-source harness.

9.

Voice Went Mainstream. We've Been Talking to Our Agents for Six Months.

Every major coding agent shipped voice input in the last sixty days. Here's what the speed-focused framing gets wrong, and why voice works — the ramble is the signal, not the noise.

10.

What's the Business Equivalent of a Codebase?

We built an agent pipeline that ships software almost hands-off — discussion, plan, implement, review. Here's how we turned that same machine into a business factory, and the one piece that was missing.

all posts

What's the Business Equivalent of a Codebase?

We built an agent pipeline that ships software almost hands-off — discussion, plan, implement, review. Here's how we turned that same machine into a business factory, and the one piece that was missing.

Parsa · 2026-05-27

Your Laptop Is a Window, Not the Engine

Pane's remote daemon runs your AI agents on powerful hardware while you control them from any device. One command to set up.

Parsa · 2026-05-18

Which AI Coding Tools Still Use Your Claude Subscription After June 15, 2026

Anthropic’s June 15 programmatic-credit change splits subscription usage from API/Agent-SDK usage. Here’s the full map: every popular AI coding tool, affected or not, with sources.

Parsa · 2026-05-13

How We Use Claude Code at Dcouple

The actual Claude Code workflow behind Pane: discussion, planning, implementation, worktrees, and the parts we refuse to automate away.

Parsa · 2026-05-07

Voice Went Mainstream. We've Been Talking to Our Agents for Six Months.

Every major coding agent shipped voice input in the last sixty days. Here's what the speed-focused framing gets wrong, and why voice works — the ramble is the signal, not the noise.

Parsa · 2026-04-18

Before Your First /discussion: The Repository Setup That Makes Everything Else Work

The repository setup that makes AI agent workflows actually work — monorepo structure, AGENTS.md, mechanical invariants, and the .claude directory that every agent session boots from.

Parsa · 2026-04-16

Same Chef, Six Hats: What a Viral Agent Post Gets Right and Wrong

A post comparing three Claude Code tools went viral. The author found the right layers but the wrong conclusion — three tools when three commands do the same job.

Parsa · 2026-04-09

A Turing Award Winner Just Described Our Exact Workflow

Pat Hanrahan — Turing Award winner, GPU computing co-creator, Stanford professor — independently verified our exact development workflow: spec, read, verify.

Parsa · 2026-04-06

The Cobbler's Children Have No Shoes

Claude Code's source code leaked. The company building the most popular AI coding agent ships code that violates every principle that makes codebases agent-readable.

Parsa · 2026-03-31

They Gated the Fix. We Open-Sourced the Whole Harness.

Anthropic built fixes for every way Claude Code breaks — hallucination, context decay, lazy fixes — then gated them behind an employee flag. We built the same fixes into an open-source harness.

Parsa · 2026-03-31

Building a Software Factory: 3 Commands, Custom Agents, and the Harness That Runs It

How we built a repeatable software factory with Claude Code and Codex — three slash commands, custom agents, voice-first development, and the harness engineering that ties it all together.

Parsa · 2026-03-29

Two Founders, 300k Lines, Zero Engineers: Our AI-Native Development Workflow

The specific, repeatable process two non-traditional founders use to ship a 300k line Next.js monorepo with 3-6 AI coding agents running in parallel.

Parsa · 2026-03-06