Give it a starting point
Once you’ve set up BotHearth, paste a task into the home screen and choose Start task. Tell it which pages or information to use and what you want back. Follow the work and open its saved result when it finishes.
These are prompts to try, with clear ways to check the result. Use pages and data you’re allowed to share with your model provider. Privacy and approval boundaries and model usage costs still apply.
Task 01 / Research
Get up to speed on a topic
You’re learning about a hobby, planning a project at home, or trying to understand something new. Give BotHearth two or three relevant public pages and ask for a brief you can come back to.
You provide: the topic and exact page URLs. Ask for: topic-brief.md, with key points, sources, and open questions.
A prompt to try
I’m learning about TOPIC. Read the public pages at PAGE_URL_1 and PAGE_URL_2. Save topic-brief.md with a short overview, five useful points in your own words, and three questions I might want to explore next. Put the source URL beside each factual point. Use only these pages and mark anything they disagree on or don’t explain. Do not sign in or submit anything. Finish by naming the saved file.
Replace the topic and URLs before starting. You might use two guides to growing herbs, learning photography, or starting a home project.
Make the brief useful to you
Open the saved brief and follow its source links. Check that the key points are supported by those pages and that questions are presented as questions. If something matters to your decision, read that part of the original source. The brief should help you find your way through the material.
Task 02 / Comparison
Put your options side by side
Comparing courses for a hobby, supplies for a personal project, or places to visit? Give the agent the pages you’re looking at and the details you care about.
You provide: two or three public pages and your comparison criteria. Ask for: options.md, a table you can use to make your own choice.
A prompt to try
Compare the options at PAGE_URL_1, PAGE_URL_2, and PAGE_URL_3 for my personal use. I care about MY_CRITERIA. Save options.md with a table of the option name, the relevant details shown on each page, any listed price and currency, and a source link. Write “not stated” when a detail is missing. Add the differences that seem most relevant to my criteria and questions I should check myself. Do not sign in, contact anyone, add anything to a cart, or buy anything. Finish by naming the saved file.
Replace the URLs and criteria. For example, you could compare beginner photography courses by subject, format, and time commitment.
Use the comparison to decide
Open the table and check a few entries against the pages. Pay attention to missing details, price conditions, and dates: a page may be incomplete or change later. The agent can organize the information you give it; you make the final choice.
Task 03 / Live website audit
Find what a new visitor cannot answer
Ask BotHearth to browse your public website as a prospective customer. It can find unclear answers, broken journeys and gaps in your getting-started pages, then save concrete corrections.
You provide: your website URL and the people it serves. Ask for: website-audit.md, with page links, observed problems and the five most useful fixes.
A prompt to try
Audit the live website at MY_WEBSITE_URL for someone considering MY_PRODUCT. Open the homepage, getting-started, pricing and FAQ pages. Check whether a visitor can answer what it does, what setup needs, what it costs and what data it uses. Save website-audit.md with the five highest-impact fixes, each with the exact page URL, observed problem, suggested wording and a way to check the improvement. Separate observations from assumptions. Do not publish changes or submit forms.
Replace the URL and product before starting. Review the proposed changes against your actual product. For search discovery, check indexing and sitemap status in your own search-console account; a public-page audit cannot establish private indexing data or guarantee search rankings.
Keep control where it matters
If you include Search Console in the task, take control for sign-in and property verification. You can review the sitemap or indexing report there, then give control back. Keep account credentials out of the task message.
Task 04 / Separate computer
Review a temporary environment and its logs
A prepared Linux VM can keep a troubleshooting session away from your everyday computer. Use its browser to inspect a staging site, uptime dashboard or log viewer while keeping a timestamped record of what changes.
You provide: a prepared host, the dashboard URLs you may access, the observation window and the symptoms to watch. Ask for: environment-review.md, with timestamps, evidence and a cleanup checklist.
A prompt to try
Use the browser to review STAGING_URL and LOG_DASHBOARD_URL for 20 minutes, checking about every two minutes. Record visible errors, health changes and timestamps in environment-review.md. Ask me to take control if sign-in is needed. Do not change the server, restart services or delete resources. Finish with observed problems, checks that were unavailable and a cleanup checklist for this temporary environment.
Replace the URLs. This is a bounded observation task: the host and model connection must remain available, and usage limits or a human handoff can pause it. BotHearth's standalone API mode has scheduled routines; the normal Codex and Claude Code task interface does not yet provide a recurring monitoring service. Use your server's existing alerting for unattended coverage.
Creating a VM, installing server software and running shell diagnostics require the corresponding host access and configured tools. The default browser task does not provision them from a prompt. Prepare the host with the remote deployment guide. At the end, review saved work and delete temporary resources in the provider console when you are ready; stopping a VM may leave billable storage or other resources.
More help: complete quickstart, following a task, security and privacy. Example prompts reviewed 2026-09-10 for v0.0.1 alpha.