How do I connect a support chat to the right project?
Each chat instance can be bound to one of your projects. In the chats tab, open ▶ instances, expand the instance, and choose your project in the project dropdown. Binding does two things: the instance's conversations show up in that project's sidebar, and the support agent answers from that project's code, so its replies match what your product actually does. When you create an instance from a project's chats tab, it is bound to that project for you.
Before you start
- You need the Support module and to be signed in to codus cloud. See What is codus Support?.
- The project you want to bind to should be open in codus, so it appears in the dropdown. You can still bind to a repository that is not currently open, but open projects are easiest to pick.
Why binding matters
The support agent gives better answers when it can read the actual product it is answering for. Binding an instance to a project points the agent at that project's code, so when a visitor asks "how do I export my data?" the answer reflects how your product really does it, not a guess.
Binding also decides where conversations appear. Each project's chats tab shows the conversations for the instances bound to that project, plus any instance that is not bound to anything. That keeps a busy account tidy: the right conversations sit with the right project.
Step 1: open the instance
- Click the chats tab in a project's sidebar.
- Click ▶ instances.
- Click the instance you want to bind, to expand it.
Step 2: choose the project
Use the project dropdown inside the instance card.
- Pick a repository or folder from the list to bind the instance to it.
- Pick no project (shows everywhere) to leave it unbound. An unbound instance's conversations show in every project's chats tab, so it stays findable until you assign it.
Your choice saves as soon as you pick it. Binding is by repository where possible, so it follows any copy of that repository you have open, whatever the folder is called.
Answering while you are away
Binding is also how the agent gets the knowledge it needs to answer when your Mac is closed. From the instance card you can generate a support brief, a short distilled description of the product taken from the bound project. codus shows its age next to a generate brief or regenerate brief button. The brief is what lets codus keep answering after hours. This has its own page: see How does support answer when my desktop is closed?.
How do I know it worked?
The instance card's summary line shows the bound project with a small house marker, for example ⌂ your-repo. Conversations for that instance now appear in that project's chats tab. If you bound to a repository that is not open in codus, the dropdown shows it labelled "(repo not open in codus)" so you know it is still set.
Common problems
My project is not in the dropdown. Open it in codus first. Folders without a Git remote appear too, labelled "(folder, no git remote)". If you know the repository name, an instance already bound to it keeps that binding even when the project is closed.
Conversations are showing in the wrong project's tab. The instance is either bound to that project or unbound (unbound shows everywhere). Open instances, expand it, and set the project dropdown to the one you want.
The agent's answers are vague or generic. Check the instance is bound to the right project, and that a support brief exists and is not stale. A missing or old brief is the usual cause of thin answers when your desktop is not online to read the code directly.