What is the issues tab, and how is it different from a GitHub issue?

The issues tab is a queue of problems raised from your customer-support conversations, waiting to be fixed. It only appears if your team has the Support module. An issue here is not a GitHub issue; it is a codus support escalation tied to a project. From an issue you can send it straight to that project's agent to work on, and when a chat-born issue is fixed, the customer who reported it is told automatically.

Before you start

Two things need to be true for the issues tab to work:

• Your team has the Support module. Without it, the tab does not appear at all. See What are the modules, and what does each one add?.
• You are signed in to codus cloud. If you are not, the tab shows "Sign in to codus cloud to use the issues queue".

Where issues come from

An issue lands in the queue in any of these ways:

• A support agent handling a live chat escalates a bug it cannot answer.
• You right-click a message in a support chat and raise it from there.
• Any agent files one using its create_issue tool.
• You type one yourself, in the box at the top of the tab that reads "New issue… title on first line (↵ to file)". The first line is the title; press Enter to file it.

When the queue is empty it reads:

No issues. They arrive when a support agent escalates a bug, when you right-click a chat message, or when any agent calls create_issue — and the dev agent works them like tasks.

It is not a GitHub issue

This trips people up, so it is worth stating plainly. The issues tab is codus's own support queue. Filing one here does not create an issue on GitHub, and it is not connected to your repository's issue tracker. It is a to-do list of customer-reported problems that the project's agent can pick up.

Working an issue

Click an issue to expand it. At the top you see a coloured dot for its severity (critical, high, med or low), its title, a status chip, and how long ago it changed. Inside, if it came from a chat, you see a short quote from the customer so you have the context. The actions are:

• ▶ start with agent: sends the issue to the project's agent as a job and marks it in-progress. This is the main one: it is how the fix gets worked, the same way a task does.
• resolve: mark it fixed yourself.
• won't fix: close it without a fix.

When a chat-born issue is marked fixed, codus posts a short "fixed, try again" reply into the customer's conversation for you, so you do not have to go back and tell them. A closed issue that came from a chat shows the note "visitor was notified of the fix".

Statuses and the tab badge

An issue moves through these statuses: open and triaged (waiting), in-progress (an agent is on it), and fixed or wont-fix (closed). Open issues sit at the top, sorted with the most severe first. Closed ones fold into a "▶ N closed" row at the bottom that you can expand.

The issues tab itself carries a small amber number showing how many issues are still open, so you can see there is a queue without opening the tab.

How do I know it worked?

After ▶ start with agent, the issue's chip changes to in-progress and the job appears in the project's terminal for the agent to work. After resolve, it drops into the closed section, and a chat-born issue shows that the customer was notified.

Common problems

"I don't have an issues tab." It only appears with the Support module. Its absence is normal if your team does not have that module. See What are the modules, and what does each one add?.

"The tab says to sign in to codus cloud." The issues queue lives in the cloud, so it needs you signed in. Sign in and the queue loads.

"Will this show up on GitHub?" No. These are codus support issues, separate from your repository's issue tracker.