mirror of
https://github.com/Ark0N/Codeman.git
synced 2026-11-14 10:39:32 +01:00
Codeman maintainer
938c213552
Measured on opencode 1.3.0 in a private tmux socket, with a fake OpenAI-compatible endpoint streaming the reply a character or two at a time: the marker was on the screen, but the stripped client stream read D, spinner, O, spinner, N, ... because opencode redraws its spinner between the streamed pieces, so wait-output never matched it. sendmark then waited its whole timeout and answered 2 for a reply that had finished, with the answer file already written (opencode's write tool wrote it without asking). The marker wait now runs in rounds of at most 10 s, and between rounds the answer file is a way out too: a non-empty regular file whose checksum held still for one round is read, with matched false. The marker stays the fast path. The answer-file wait after a marker no longer spins when the exit wait gets no answer, and treats an ended wait as the worker gone. The same run measured the readiness mark: with a fresh home and a custom provider, the first composer bar came with the composer and a prompt pasted with its Enter at that moment was submitted, so the docs say so instead of "not measured". The example keeps its input in a subfolder, apart from the case's CLAUDE.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>