claude-wrap-ConPTY
Skill1 starsChanged 11 days agoAGPL-3.0View on GitHub
Drive a REAL Claude Code TUI from code on Windows — spawn `claude.exe` on a pseudo-console (ConPTY), render its ANSI output into a readable screen, inject prompts as bracketed paste, and verify what actually landed in the session transcript on disk. This is the black-box test harness for Claude Code itself: what a headless `claude -p` can NEVER exercise (the Ink TUI's input box, startup modals, draft/type-ahead behavior, paste framing, the eaten-Enter class of bug). Ships a verified driver (`scripts/conpty_claude.py`, pywinpty + pyte) with a `selftest` that proves the whole chain on this machine in one tiny turn, plus `probe` / `send` / `raw` CLI verbs. Encodes the measured facts that make it work: `\r` submits while `\n` is a literal newline in the box; bracketed paste is the only atomic multi-line delivery; an inherited `CLAUDE_CODE_CHILD_SESSION` SILENTLY DISABLES transcript saving (so every on-disk verification fails for a reason nothing on screen explains) — the trap for any wrapper launched from inside a Claude session; a startup modal (malformed settings.json, workspace trust, login) parks the TUI forever and is invisible-by-design unless you render the screen; conversation identity is the transcript's CREATION time, never newest-mtime; and the raw Win32 CreatePseudoConsole P/Invoke path is a reproducible dead end. Use when asked to test/automate/drive/script the Claude Code TUI, wrap claude.exe in a pty, inject or send a prompt programmatically, reproduce a TUI bug, verify a prompt reached the transcript, or debug why a wrapped claude hangs, starts no session, writes no transcript, or ignores injected input.
- Installs packages
In this repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- build-installSkill
- debug-dumpsSkill
- release-notesSkill
- release-versionSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.