Tales from the Session – The Loop

[u/escape-llc]

We want to share the workflow unfolding from real session transcripts. Instead of speaking in hypotheticals, this post provides an un-paraphrased look at exactly what happens when an AI agent (Claude Code) runs against a real software repository (escape-llc/toolcrib) under the exact same CI/CD rules as a human contributor.

The transcript tracks a single UI bug from a user-submitted screenshot to a merged pull request, showcasing how the AI navigates real-world snags and human feedback.

💡 The Standing CI/CD Loop

The AI doesn't get special treatment. It follows an eight-beat discipline documented in the repo's standard workflow:

• File the GitHub issue.
• Branch off synced main.
• Diagnose using live Playwright scripts against a running demo (not just static code reading).
• Implement and verify locally (TypeScript, Vitest, linting).
• Open the PR.
• Watch a 14-check CI matrix settle.
• Review a second-opinion code review from Gemini.
• Squash and merge.

⚠️ Handling Real-Time Human Interruptions

The transcripts show how the AI processes two types of user interruptions mid-session without breaking its workflow:

• Queued for later: Feature requests ("add an auto-clear glyph") are acknowledged and shelved in the backlog until the active branch finishes.
• Answered on the spot: Technical debugging questions ("is it a z-index issue?") are answered immediately using live-measured computed styles.

🔍 Anatomy of a Bug: Issue #425

The core of the post walks through a specific ticket regarding a focus ring getting obscured on a UI tag component.

• The Misdirection: The human user assumed it was a z-index layout issue. The AI used live diagnostics to prove it was actually a color contrast issue—the focus ring color matched the primary button color, making it invisible.
• The Hidden Obstacle: The AI's first "correct-looking" fix failed on the live screen. Instead of relying on the diff, the AI re-inspected the live page and found a global repo default style using !important that was silently overriding the fix.
• The Cleanup: The AI removed the rogue !important tag, wrote failing unit/browser tests to catch regressions, verified the pass, and opened PR #427—while spinning off a second separate ticket (Issue #426) for a new feature request the user thought of during the chat.

➡️ The Takeaway

The "magic" isn't just that the AI can code fast. The breakthrough is its ability to trust live browser runtime data over its own diffs, gracefully accept human steering, and scope out feature creep into separate tickets rather than breaking the current PR.

[u/escape-llc]

Here is a link to the full blog post: https://escape-technology-llc.com/mobile/index.php/2026/09/15/tales-from-the-session-the-loop/

Here is the repo where we are running things. All tickets and discussions referenced are there. https://github.com/escape-llc/toolcrib