Cannot submit comments in task UI – no POST request is sent
prfk · 2026-09-20
Hi,
after migrating my Paperclip installation to a new Docker host, I can no longer submit comments/messages in any task through the web UI.
Environment
Self-hosted Paperclip Docker Paperclip stable v2026.916.0 Tested with Firefox and Edge
Observed behavior
I can enter text into the task chat composer. The Send button appears enabled. Clicking Send does nothing. Ctrl+Enter also does nothing. This affects existing and newly created tasks.
What I have verified
The click event reaches the actual task-chat-composer-send button. No POST /api/issues/.../comments request is generated when clicking Send. The normal live-runs / interactions polling continues. Calling POST /api/issues/{id}/comments manually from the browser console succeeds with HTTP 201 and creates the comment. Therefore the API endpoint, authentication/session and database write appear to work. Tested after restarting the Paperclip container. Tested in another browser and a private browser session. Temporarily disabling local DNS/ad blocking made no difference. I also switched to a clean build of stable v2026.916.0; the issue remains.
It therefore looks as if the UI stops somewhere between the Send action and calling the comments API.
Has anyone seen this behavior, or is there a known client-side state/configuration issue that can cause TaskChatComposer.submit() to return without calling onAdd()?
Answers
4D 61 6E 78 6D 61 6E · 2026-10-03
I can reproduce this on stable v2026.1001.0, and I have now done a fairly extensive elimination exercise. Posting the details in case they help narrow this down.
Environment
Paperclip stable 2026.1001.0 Ubuntu 24.04.5 LTS, aarch64 Self-hosted on a Dell Pro Max GB10 Embedded PostgreSQL Paperclip running as the managed per-user systemd service Private-network deployment Tested from multiple browsers
Observed behaviour
I can create tasks normally.
In an existing task:
I can type text into the comment/composer box the black Send/up-arrow button appears enabled clicking Send does nothing no visible UI error is produced no comment is created
Network inspection
I opened DevTools and filtered the Network tab while attempting to submit a comment.
I see normal GET/polling traffic, including requests such as:
prfk · 2026-09-23
Thanks, Nora. I upgraded the installation to v2026.916.1, but unfortunately the issue persists.
I verified the checkout and running Docker image as carefully as possible:
v2026.916.1 resolves to commit d554c4789 (fix(ui): keep task composer available while pause state loads (#13562)). The Docker image was rebuilt after checking out that tag. I verified that the currently running container uses exactly that newly built image.
One detail that confused me during verification: git tag --points-at HEAD shows both v2026.916.1 and beta/v2026.921.0-beta.0 pointing to the same commit. So while I believe I am running the correct v2026.916.1 code, I wanted to mention this in case there is some release/tagging detail I am overlooking.
After the upgrade:
the composer still accepts text; clicking Send still does nothing; no POST /comments is sent; a manual POST /api/issues/{id}/comments from the browser console still succeeds.
So #13562 does not appear to resolve the issue in my installation.
I’ll check /tree-control-state specifically as you suggested. Is there any other client-side state or request you would recommend checking if /tree-control-state completes successfully?
Nora · 2026-09-22
Sorry this bit you after the host move — it's a known client bug on stable v2026.916.0, not your API or Docker volume.
What's happening
On 916.0 the task page disables the chat composer until /tree-control-state (pause check) finishes. In React Query v5 that pending flag stays true until the first successful response. If that call is slow or never settles — common after a host/network change — TaskChatComposer.submit() returns on if (disabled) and never calls onAdd(), so no POST /comments leaves the browser. Manual console POSTs still work because the API path is fine.
In streamlined chat the Send control can still look primary (disabled:opacity-100), so it feels clickable while it is blocked. Placeholder text is often Checking task status….
Patched in [#13562](https://github.com/paperclipai/paperclip/pull/13562) and shipped as stable [v2026.916.1](https://github.com/paperclipai/paperclip/releases/tag/v2026.916.1) (2026-09-21). Patch only; no migrations.
Fixes
1. Upgrade to v2026.916.1 (or newer stable). Follow [Update Paperclip](https://docs.paperclip.ing/#/how-to/update-paperclip) for your install path (Docker image tag / compose).
2. Confirm the stall before you upgrade (optional). DevTools → Network: does …/tree-control-state hang or error on task open? Composer placeholder = Checking task status…?
After 916.1, send works while that check is still pending; a real pause still blocks via the pause card / server 409.
My bet is the pending pause check on 916.0. After you land on 916.1+, does Send fire a POST /comments again?