Plain language works. The agent is not a search box and it does not need magic words. It needs the same things a colleague would need.
Give it three things:
| Tell it | Example |
|---|---|
| Where | "the footer on the contact page", "the chat module", "the admin page for news" |
| What is wrong | "the heading is cut off on mobile", "the button does nothing" |
| What you expect | "it should wrap to two lines", "it should open the form" |
Good:
On the news page, the date under each article is in English. It should be Danish, like the rest of the page.
Weak:
Fix the dates.
If your message is too thin, the agent asks instead of guessing. That is on purpose.
Paste a screenshot straight into the chat. Paste the preview link of the page you are looking at. Both save a round of questions.
Paste the ticket number and the agent reads the whole ticket first — description, comments, screenshots:
Look at PM-1234 and tell me what you think the problem is.
Fix PM-1234.
Post a summary of what you found on PM-1234.
The first time, the agent asks you for a Tickets API key. Open Tickets → Settings → API keys, create a key named worker, and paste the gp_… value into the chat. From then on it acts in Tickets as you.
The agent knows the code, but Brain knows how GoPublic wants things to work: how a module should look, our editorial conventions, past decisions. It searches Brain on its own when a question is about "how we usually do this". You can also nudge it:
Check Brain for how the chat module headline is supposed to look before you change it.
Some words trigger things. Use them when you mean them.
| You say | What happens |
|---|---|
| push the changes / commit and open a PR / publish / ship it | The agent puts the work on GitHub on a branch and, if asked, opens a pull request. See Branches and publishing. |
| merge it | Merges a pull request. Only after review. Publishing never merges by itself. |
| reset to default / reset the preview | Wipes your preview back to the blank template. Unpublished content is gone. |
| restore Trafikstyrelsen from silver (a client and an environment) | Copies a real client's content into your preview. Heavy and slow. See Preview, restore, and reset. |
| discard the local code changes | Throws away unpublished code on the worker. Reset does not do this. |
| show me the agent wiki | Recreates this wiki as pages on your preview and gives you the links. |
| run the tests / verify this | Runs the automatic test suite against your preview. The agent offers this after bigger changes; it does not run it after every small tweak. |
"Done", "looks good", "thanks", "perfect", "ok". The agent reads these as you are happy with the preview, not as put it on GitHub. If you want it on GitHub, say so.
About one in four support reports is the product working as designed (the classic: upload a .webp, then complain that "download original" gives you a .webp). The agent reproduces every bug before it touches code. If it cannot reproduce it, it asks you for more. If it reproduces the behaviour and the behaviour is correct, it says so and explains why. That is a valid answer, not the agent being lazy. If you still want the behaviour changed, say "treat this as a change request".
A new chat for a new job keeps things clean. Inside one chat, the agent remembers everything you said.