Report issues on GitHub. Report a bug or suggest an improvement, or first check the guide and existing issues. A GitHub account is required to submit feedback. Maintainers review reports manually, with no guaranteed response time.
Common situations
My task keeps waiting
Read the waiting reason in the conversation first. A task may be waiting for a dependency, execution slot, approval, or input, or it may lack a configured project or model. Check whether the 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 that they share a trusted, reachable network. From 0.1.18, open “Connection diagnostics” on each device to check the listener and communication rules. If rules are missing, follow the page to allow LAN connections and retest. Public networks require explicit consent, and Windows may request administrator authorization. If connection still fails, share a redacted diagnostic summary and the exact message.
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.
Do not send full data directories, model credentials or private projects. GitHub issues and pull requests are public, so use minimal reproductions and synthetic data. Use the private reporting link below for security vulnerabilities.
Source code
Rivloom’s own desktop code is licensed under Apache-2.0. You can inspect the source, study the implementation, and use and modify it under the license. Upstream code, fonts and dependencies retain their own licenses.
Report security vulnerabilities privately
Report a vulnerability privately on GitHub (sign-in required). Include the affected version, a minimal reproduction and potential impact using synthetic data. Do not disclose exploit details in public issues or pull requests. Only the latest release is maintained; separate backports to older releases are not promised.
For a new task, see the User guide. For authorization and data handling, read the Security boundaries and Privacy notice.