Skip to content

Add REPL-first runtime flow#82

Open
section9-lab wants to merge 2 commits into
devfrom
repl-first-browser-automation
Open

Add REPL-first runtime flow#82
section9-lab wants to merge 2 commits into
devfrom
repl-first-browser-automation

Conversation

@section9-lab

Copy link
Copy Markdown
Contributor

Summary

  • Add the REPL-first nodejs runtime flow with interactive cell handling.
  • Isolate output boundaries so hard-stop guidance is printed once and buffered output is discarded correctly.
  • Update docs and real-browser/unit coverage for the REPL flow.

Testing

  • npm test
  • pre-commit: code-check, e2e-test, site-skill-validation, smoke-test, style-check, vulnerability-audit

section9-lab and others added 2 commits July 6, 2026 17:37
…ndaries

The update-notice probe is fire-and-forget and resolves during bootstrap,
long before the first REPL cell arrives, so beginOutputBoundary's per-cell
reset silently dropped the pending trailer and the notice never surfaced
in interactive mode. Preserve the pending trailer across the per-boundary
reset, and clear it once written so a long-lived REPL process shows the
hint at most once instead of repeating it after every cell.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@WUXM5
WUXM5 force-pushed the repl-first-browser-automation branch from f2c48ff to 429c00d Compare July 6, 2026 09:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant