Deploy SSH doesn't use remote-worker.sh #1

New issue

Closed

opened 2026-03-02 02:02:55 +00:00 by Mark · 2 comments

Mark commented

2026-03-02 02:02:55 +00:00

Owner

The deploy-ssh.sh script runs picoclaw with '&' then exits. No task mechanism, no result return.

Fix: Deploy remote-worker.sh which stays running and accepts tasks via stdin

The deploy-ssh.sh script runs picoclaw with '&' then exits. No task mechanism, no result return. **Fix:** Deploy remote-worker.sh which stays running and accepts tasks via stdin

Mark referenced this issue from a commit

2026-03-02 22:04:32 +00:00

Phase 1.1: Implement callback receiver and client

Mark referenced this issue from a commit

2026-03-03 05:28:20 +00:00

Phase 1.3: Update deploy-ssh.sh to use remote-worker.sh

Mark commented

2026-05-11 20:12:58 +00:00

Author

Owner

Feature work — requires implementing worker task queue, SSH deploy improvements, and callback mechanism. Tabling as feature-request.

Mark added the

feature-request

label

2026-05-11 20:12:58 +00:00

Mark added the

quickfix

label

2026-05-19 01:39:58 +00:00

Mark removed the

quickfix

label

2026-05-28 03:30:06 +00:00

Mark referenced this issue from a commit

2026-05-28 03:34:44 +00:00

fix #1: Deploy SSH uses remote-worker.sh with --poll instead of stdin mode

Mark closed this issue

2026-05-28 03:34:44 +00:00

Mark commented

2026-05-28 03:34:50 +00:00

Author

Owner

Fixed in 97cc10f. Deploy SSH now passes --poll to remote-worker.sh so it uses HTTP polling instead of stdin mode. Stdin mode was broken with nohup (stdin is /dev/null, causing immediate exit). With --poll, the worker polls the callback receiver for tasks and stays running.

Fixed in 97cc10f. Deploy SSH now passes `--poll` to `remote-worker.sh` so it uses HTTP polling instead of stdin mode. Stdin mode was broken with `nohup` (stdin is /dev/null, causing immediate exit). With `--poll`, the worker polls the callback receiver for tasks and stays running.