There is no public support channel yet. Existing private testers can contact their original inviter. Other users can start with the User guide, the common questions below, and the Changelog.
Common situations
My task keeps waiting
Read the waiting reason in the conversation first. The execution device may be busy, waiting for review, or missing a configured project or model. Check whether the local queue is paused or the task is on hold. Waiting does not mean sending failed; you do not need to create the same task again.
I cannot find another device
Make sure Rivloom is running on both devices and they are on a trusted network where they can reach each other. Check discovery and pairing in Nodes & Brain. Do not disable the firewall or expose local business services to troubleshoot. If discovery still fails, record the network setup and exact message for your private test contact.
The result of sending or a queue action is uncertain
Keep the original conversation and check the latest state and messages. If the queue action offers Retry confirmation, use it to confirm the original action instead of creating a replacement task.
AI finished, but no file diff is shown
Diffs show only what the execution engine actually returns, so there may be no diff available. Check the actual files and relevant tests on the execution device. AI's completion reply does not replace human review.
A task still needs confirmation after stopping or restarting
Stopping does not roll back file changes. When execution is unconfirmed, the application retains an interrupted or waiting state to avoid blindly running the task again. Check the files and task records before deciding what to do next.
Include this information in feedback
- Your Rivloom version, Windows version, and whether the task ran locally or on a paired device.
- What you did, what you expected, the exact message you saw, and whether you can reproduce the problem.
- Relevant screenshots of the conversation state or a short error message, with keys, personal information, and sensitive project content removed first.
You do not need to send a complete data directory, model credentials, or private project. For sensitive issues, agree on a suitable way to handle the information with your existing private test contact first.
For a new task, see the User guide. For authorization and data handling, read the Security boundaries and Privacy notice.