The Slack channel does not respond#
Confirm you used the installed app mention in a project-bound channel. Ask the administrator to check the channel binding and the registered project. A newly registered project revision applies to new threads.
My mention got a card instead of an answer#
On mainline, a plain top-level mention is routed and a change gets a Quick/Full card. Press Just answer, or start the request with chat: to always reach the chat agent. Mentions inside a thread the chat agent already answers need no prefix.
AgentX asks an admin to turn on shared tasks#
Starting tasks from Slack needs shared tasks (SHARED_TASKS) on for the Slack service, and the project’s developer tasks enabled. Other refusals name the reason: the open-task limit, a thread that already has a task, or a channel not connected to a project you can use. Anything else comes with a reference to give an admin.
Thread replies are not reaching the task#
Replies without an @AgentX mention need the Slack app’s channels:history and groups:history scopes and the message.channels and message.groups events. Ask an admin to update the app from the manifest agentx init generates and reinstall it. Until then only @AgentX replies are saved.
The coding tool asks me to sign in#
Complete the installed client’s sign-in flow. Ask the client to use agentx_whoami to confirm the environment and identity. If a tool reports a version mismatch, use the CLI version matched to that deployment.
My project is missing#
Ask for agentx_list_projects. Project access may depend on membership in its Slack channel. Ask an administrator to check access and whether developer tasks are enabled. A Slack-unavailable notice can mean some channel-derived projects are temporarily missing.
The wait timed out#
Ask for agentx_get_task with the same task ID. The task can still be running. Cancelling a wait only stops the wait.
A follow-up says TASK_BUSY#
The previous run is still active. Wait for it to end, or explicitly cancel the task if you want to stop that work. Send the follow-up afterward.
The result says not verified#
Read the reason and identify which check is missing. Missing setup, an unavailable command or a stopped task can leave no usable result. Ask for the required check instead of assuming the change passed.
The workspace will not close#
Inspect the unpublished-work report and preserve the remaining changes. Close again after the work is published or otherwise safely kept. Do not confuse cancel with close.
Publishing is refused for my repository#
Read the refusal: it names the cause. Git LFS files, checked-out submodules, extra url.*, http.* or remote.* keys, and dev container settings that reach the host are refused. Repository and dev container rules →
My task did not use my ChatGPT plan#
Check chatgpt status. The task falls back to the installation’s model when your plan hits its usage limit (for an hour), the connection was revoked or expired, or the plan no longer allows the model. AgentX says so in the task’s Slack thread. Admins can check doctor. Fallback rules →
The environment itself is unhealthy#
An operator with access can run:
npx @preplabsai/rovara-code --env <env> doctor --region <region>
When asking for help, include the CLI version, task ID, exact error and relevant redacted output. Keep credentials out of reports.
The approval says it is stale#
Open the latest task prompt and document. The workflow revision or document digest has changed; decide on the current version. Do not keep submitting the old approval.
Checks or reviews blocked the task#
Read the failed check or blocking finding and the current candidate. Only problems the change introduced block. Send the change back to coding, retry the reviews on the same code, or accept a finding with a reason from a coding tool (agentx_resolve_review_findings).
A review that could not run or be read never counts as a pass. agentx_retry_workflow restarts blocked planning or coding, or reruns checks. If the draft PR did not open, retry opening it.
The task page asks me to sign in#
Sign in with the identity the task authorizes and return to the same page. “You don’t have access to this task” means you are not the owner or in the task’s channel with access to its project, or the task does not exist. Possessing the link does not grant decision rights.
A merged PR did not finish the task#
Check the full required PR set and current GitHub state. Other required PRs may still be open or reopened. Inspect any delivery/reconciliation blocker before repeating work.
Rovara loop ignores my comment#
Check that your GitHub login is in the repository’s .rovara/loop.yaml collaborators, that the repository was added with rovara loop add on the computer running the loop, and that rovara loop status shows the daemon running. Comments made before the repository was added are never replayed. rovara loop check <issue> shows where the loop stands.