Nanobot installed

Congratulations, your Nanobot is ready for first tests

Use the messaging channel you configured. These starter tests are intentionally small so you can verify the Claw-style harness without burning through free-tier model or search limits.

← Back to install guide Slides
First contact

Verify connectivity from your messaging app

Do not start by running VM commands. Open the channel you configured and send a single low-cost message:

Message to send
hello
Telegram
Send /start, then hello.
Discord or Slack
DM the bot, or mention it in the allowed channel with hello.
Email
Send an email with subject/body hello from the allowed sender.
WhatsApp
Send hello after the bridge login is already connected.
Vertex AI path: your message still starts in the messaging app. Nanobot sends the model request to local LiteLLM on the VM, and LiteLLM calls Vertex AI using the VM service account.
If there is no reply: first check that you are using the allowed sender/account, the right bot or channel, and the right messaging service. Wait for one reply before retrying; repeated rapid messages can make troubleshooting harder.
Starter apps

Three small apps that show the value of a Claw harness

Each prompt is designed to run from chat, stay small, and demonstrate something beyond a normal chat interface: workspace files, web/tool use, and local CLI/script work.

Workspace files

App 1: Markdown Todo Tracker

Start a persistent todo list in Nanobot's workspace and ask it to summarize the result.

Prompt
Create a markdown todo tracker in your workspace named todos.md.

Add these sections:
- Today
- Waiting
- Done

Add 3 starter todos:
- Test Nanobot reply
- Choose one useful automation
- Review logs only if something fails

Reply with only the file name and a 3-bullet summary.
Web lookup Scheduled plan

App 2: Stock Price + Daily Alert

Ask for one lightweight price lookup, then have Nanobot draft a daily alert workflow without running a loop.

Prompt
Research the latest AAPL stock price with one web lookup.

Then create a short daily alert plan in your workspace named stock-alert-plan.md.

The plan should say how to send me one daily price summary at 9:00 AM.
Do not activate any recurring job unless I confirm.

Reply in 3 bullets. This is not financial advice.
Local file CLI script

App 3: Sort Notes by Date

The sample text is short enough to type manually into Telegram or another chat app.

Prompt
Create a workspace file named date-notes.txt with this text:

Dinner with Alex - Jun 7 2026
Pay rent 2026-06-01
Dentist 5 Jun 2026
Submit report 2026/06/03

Now create a reusable local script to sort similar notes by date.
Use local CLI tools or Python if helpful.
Save the sorted result as sorted-date-notes.md.

Reply with only:
1. files created
2. sorted order
Free-tier habits

Keep first tests small

  1. Send one prompt at a time and wait for the reply.
  2. Prefer 3-5 bullet answers instead of long reports.
  3. Use one ticker, one small file, and one tiny todo list for starter tests.
  4. Avoid rapid retries and broad research loops while validating the install.
  5. If a task fails, adjust the next prompt instead of sending the same prompt repeatedly.
What these tests prove

What to look for

Persistent workspace

The bot can create and update files that survive beyond a chat reply.

Tool use

The bot can use web search and local tools when the task needs external context or computation.

Automation path

The bot can prepare scripts and scheduled-workflow plans that can later become recurring jobs.

Created by Commune.AI.