Docs / Features
Tips for good requests
How to write requests that get the best result at the lowest cost.
On this pageDescribe the outcome, not the stepsGive key details up frontPaste the full errorLet it testSplit big jobsKeep cost downWork from your phone
Describe the outcome, not the steps
Instead of “create index.html, then CSS…”, say what you want in the end:
Example request
I want a landing page for my course where sign-ups go into a Google Sheet.
Give key details up front
Language, brand colours, a specific technology or constraints — say them at the start so nothing has to be rebuilt later.
Paste the full error
If something breaks, paste the complete error and say what you did when it happened.
Let it test
Say “run it and check it works”. The agent runs it, reads the output and fixes what’s wrong.
Split big jobs
For a large project, first ask for a plan, then go step by step. Do each part in its own chat.
Keep cost down
- New job, new chat
- Simple work with Haiku or GPT-6.1
- Write a HARNES.md so the agent doesn’t search for project info every time
Work from your phone
When you’re out, give it a task from your phone and check the result later.