How to use the GoPublic Agent

This wiki is for everyone at GoPublic, coder or not. It explains how to get work out of the agent and how to avoid the two mistakes that cost people time: resetting the preview by accident, and thinking something is published when it is not.

The four things to know

  1. You have your own agent and your own test site. Nobody else sees your changes until you publish.
  2. The agent edits, you look. After every change it gives you a link. Open it. Your eyes are the test.
  3. Nothing is published until you say so. "Looks good" is not "publish". Say push or make a PR.
  4. Reset wipes your test site. Only say "reset to default" when you mean it.

Start here

  1. Open cursor.com/agents and sign in with your GoPublic Google account.
  2. Pick the worker named after you (for example daniel). That is your agent.
  3. Start a new chat and describe what you want in plain language.

Your test site (we call it the preview) follows your name:

WhatAddress
The websitehttps://<your-name>.agent.gopublic.dk
The admin (Backoffice)https://admin.<your-name>.agent.gopublic.dk

Daniel's preview is https://daniel.agent.gopublic.dk, Kristian's is https://kristian.agent.gopublic.dk, and so on. Not sure? Ask the agent: "What is my preview address?"

Pages in this wiki

PageRead it when
How to talk to the agentYou want phrases that work and phrases that backfire
Everyday tasksYou have a real job to do: fix a bug, change a text, work on a Tickets ticket
Preview, restore, and resetYou need a client's real content, or you want a clean slate
Branches and publishingYou want to know when something actually leaves your test site
FAQSomething feels off

What the agent is

A GoPublic developer that never sleeps and never assumes. It works inside a worker: a machine with the GoPublic code and a live copy of the product running on it.

It can:

  • change code and content, and show you the result on your preview
  • read a Tickets ticket when you paste its PM- number, and write back to it
  • look up how GoPublic normally does things in Brain (our knowledge base)
  • look at a client's public website to check a bug report
  • check or set up content on a real Staging or POC client site, when you ask

It will not, unless you clearly ask:

  • publish to GitHub (commit, push, open a pull request)
  • merge a pull request
  • copy a real client's content into your preview
  • reset your preview
  • change anything on a live client site

One worker, one job

Your worker holds one set of unfinished changes at a time. Finish or publish one job before you start an unrelated one, or the changes get mixed together.

Where this wiki lives

The source is the GitHub wiki of beru-org/Agent. Ask your agent "show me the agent wiki" and it recreates these pages on your own preview under Agent wiki, so you can read them next to the product. If a page here contradicts what the agent does, tell the agent — the wiki is what gets fixed.