Build with a coding agent
read as.mdGive your coding agent this page’s link with your task, or copy the prompt on the home page. The steps below are written for the agent.
Before you write anything
Section titled “Before you write anything”Read these as raw markdown before you change anything:
- llms.txt and the pages it lists under “Start here”.
- The CLI guide, for every
guueycommand. - The HTTP API, for any HTTP call.
Follow those pages exactly. Don’t invent commands, flags, routes or fields they don’t contain. If the task needs something they don’t cover, tell the person you’re working for and ask before you go further.
The build loop
Section titled “The build loop”-
If
guueyisn’t found, install it:Terminal window npm install -g @guuey/cli -
If there’s no project yet, scaffold one. Pass the framework so it doesn’t stop to ask (
openai-agents-sdkandgoogle-adkwork too):Terminal window npx @guuey/create-agentic-app <name> --framework claude-agent-sdk -
Run
guuey whoami. If it printsNot logged inorEXPIRED, stop and ask the person to runguuey loginthemselves. -
guuey deploycreates the app only from an interactive terminal, and yours most likely isn’t one. So ask whether the agent is for them or for their customers, and create the app:Terminal window guuey apps create --name "<name>" --for personal # or --for customersapps createprints the App ID but doesn’t write it into the project. Set it inguuey.jsonasappIdyourself, orguuey deploystops withNo app linked. -
Deploy, then check it:
Terminal window guuey deployguuey test "hello"guuey logsDeploy and test again after each change.
Distribute it
Section titled “Distribute it”When guuey test answers, ask the person how people will reach the agent, then follow one path:
- They want people using it quickly, with nothing else to build: share it through Portal.
- They’re building their own product or site around it: build it into their own app, and run it locally first.
- They aren’t sure: start with Portal. The same agent can go into their own app later.
Share it through Portal
Section titled “Share it through Portal”Portal (app.guuey.com) is Guuey’s app where people find agents and chat with them, so there’s no frontend to build or host.
-
guuey deployends with a Portal link,https://app.guuey.com/agent/<appId>. Anyone with the link can open the agent. It isn’t listed in Portal until you publish it. -
For a readable link, claim a slug (3 to 50 lowercase letters, digits and hyphens). The agent then also opens at
https://app.guuey.com/agent/<slug>, and the command prints the address of the agent’s own page:Terminal window guuey slug claim <slug> -
Ask whether people can chat without signing in, and set it:
Terminal window guuey apps access --guests on # or --guests off -
To list the agent in Portal’s Explore tab, ask the person first, then publish:
Terminal window guuey apps publish --name "<name>" --description "<one line>"The listing goes live right away, with no review step. It needs a plan on the app. Without one, the command is refused and the listing is saved without being published. List only an agent that can’t change anyone’s data, and share an agent that uses connected accounts by its link instead. Guuey doesn’t check this for you.
guuey apps unpublishtakes the agent out of Explore, and its link keeps working.
Build it into their own app
Section titled “Build it into their own app”Run it locally first, then deploy it and connect the frontend. These steps are for a project scaffolded from the default template.
-
Install and set up the project:
Terminal window pnpm installpnpm bootstrap -- --yes -
Locally, the agent calls the model with the person’s own key. Ask them to fill in the key
.env.localnames for their framework:ANTHROPIC_API_KEY,OPENAI_API_KEYorGEMINI_API_KEY. Don’t write a key yourself. -
Start the local stack:
Terminal window pnpm devThe web app runs at
http://localhost:6890and the agent athttp://localhost:6790. Locally, the agent runs as a plain process with the person’s shell environment, without the isolation it has on Guuey. A project without the web app runs the agent alone withguuey dev --serve. Plainguuey devdoesn’t start a server. -
When it works locally, deploy and connect the frontend to the deployed agent. Pass the origins the frontend will be served from:
Terminal window guuey deploypnpm bootstrap -- --link --domains https://<their-site>Guuey hosts the agent, not the web app. The person hosts the built frontend wherever they host their sites.
To put the agent on a site they already have, add the widget (one script tag) or @guuey/chat, and allow the site’s origin with guuey apps update --domains https://<their-site>.
Keep in mind
Section titled “Keep in mind”- Keep secrets out of
guuey.json. Set them withguuey env set KEY=VALUE. - You don’t need a model key: Guuey supplies the model by default. To use their own provider key, the person adds it in the console under Behavior → Model.
- New projects start with Generative UI off. To turn it on, delete
"ggui": falsefromagent.mcpServersinguuey.json(see Generative UI).