SKILL learned
preview-log-safety
used in 12 runs
Coding is becoming abundant, but we still lose time between a prompt and a change we can trust. Arcplane keeps the team and AI agents in one workflow, from rough intent to confident delivery.
Software development is entropy reduction.
webhook retries are confusing
change accepted
build webhook retry history
webhook retries are confusing
build webhook retry history
change accepted
Arcplane keeps the plan, the branch, the review, and the proof of what shipped in one place, so the work can keep moving without losing context.
// yet another chat interface? no.
Agent work has to survive handoff, retry, review, and shipping. A chronological thread is a poor container for that. The work needs its own state, with conversation attached when it helps.
Arcplane keeps chat inside the workflow, not the other way around.
Most agent work should happen in the background. Arcplane keeps agent runs moving until something needs a real call from the team: a policy was touched, evidence is missing, or the agent is about to decide something it shouldn’t.
The comment a reviewer left, the policy the team agreed on, the test that finally passed: these don’t live in your head or in old PR threads. They settle into the right memory layer, ready to become context when the next run needs it.
/* one last thing: the thesis. */
cat journal/software-is-not-solved.mdx
git remote add inbox https://arcplane.ai/journal
Subscribe and we'll git push build notes, product updates, and changelog entries
to your inbox.
# Coding is solved? Software is not.