FAQ
Short answers. Add new questions at the bottom: a heading, then a few lines.
Short answers. Add new questions at the bottom: a heading, then a few lines.
The one named after you in the Cursor environment dropdown. If you do not have one, ask whoever runs the workers. Do not pick someone else's worker — you would be working on their preview.
https://<your-name>.agent.gopublic.dk for the website, https://admin.<your-name>.agent.gopublic.dk for the admin. Or ask the agent: "What is my preview address?"
Only if you said push, PR, publish or ship it. Otherwise it is only on your worker. Details: Branches and publishing.
Not unless someone said merge it or pressed Merge on the ticket. A PR being open, approved, or green is not merged.
Wipes your preview content back to the empty template. It does not touch GitHub and it does not delete unpublished code. Details: Preview, restore, and reset.
No. The agent fixes the shared code on the current preview. Say "restore X from production" (or silver / gold / POC) if you want their data copied in — and expect it to ask first.
It reproduced what the ticket describes and the product did what it is designed to do. Read its explanation. If you still want the behaviour changed, say "treat this as a change request" and it will proceed as a feature.
Open Tickets → Settings → API keys, create a key named worker, and paste the gp_… value into the chat. The agent then acts in Tickets as you. Once per worker.
A ticket with the Worker label is handled by an automatic bugfix worker with nobody in the chat. It reproduces, fixes, stands up a test site, and comments on the ticket. If it needs a human, it writes a Worker handoff (waiting) comment and removes the label. Reply in the ticket and add Worker back to send it on its way again. Details: Everyday tasks.
eph-… site?A temporary Staging site a bugfix worker creates to show a fix: https://eph-<branch>.agent.gopublic.dk. Template content only, gone after the PR merges or after 7 days.
Yes — it searches Brain for conventions, module look-and-feel, and past decisions before it invents anything. If Brain has nothing, it tells you it is making an assumption.
Only if you name that site and ask for content work there. A site with real visitors needs an extra explicit yes in the chat. Production sites are closed to the agent during the current testing phase. Product code always goes preview → PR → merge → normal deploy.
The product is four repos. One change can need more than one PR. Review each link the agent posted.
Not for different jobs. One preview, one job at a time.
Ask: "What client is on the preview right now, and which branches are checked out?" Then restore the client you want, or reset to default and start clean.
On your worker. Preview uploads never go to the real CDN. Reset removes them.
On GitHub, in the wiki of beru-org/Agent. Ask your agent "show me the agent wiki" and it puts these pages on your preview under Agent wiki. Ask again after a reset or when the wiki has been updated.
Tell the person who operates the workers. Do not keep sending the same prompt to a dead machine.
Say "Post the result to Tickets" and give the PM number if it is not already in the chat.
New questions go below this line.