Basic idea
This playbook is a companion to the NemoClaw on DGX Spark install playbook. It walks through four ready-to-run applications you can stand up on top of an existing NemoClaw sandbox — a personal morning news digest, a software development agent, a doc and deck red-team, and a calendar negotiation chief-of-staff.
Each application is presented as a self-contained tab with the same three sections:
- Policy setup — the exact NemoClaw / OpenShell sandbox policy changes the workflow needs (channels, network egress, filesystem mounts).
- Example prompt — a copy-pasteable prompt that exercises the workflow end-to-end so you can see it work the first time.
- How to personalize — the knobs to turn (paths, schedule, audience, persona) to adapt the recipe to your real use case.
All applications run inside the OpenShell sandbox that NemoClaw created during onboarding, so the agent's filesystem, network, process, and inference access stays bounded by the policy you grant.
What you'll accomplish
You will run four practical NemoClaw workflows on your DGX Spark:
- Daily Personal News Digest — a scheduled morning briefing that wakes up on a cron, sweeps the topics you care about across an allowlisted set of sources, and posts a structured digest (Top 3, headlines by topic, deep dive, skip-the-noise, on-your-radar, local) to your Telegram home channel.
- Software Development Agent — reads a single project directory, builds an execution plan for the features you specify, implements them, reviews its own work, and writes a
develop-and-review.md you can read before merging. No outbound network beyond the local inference endpoint.
- Deck Reviewer — a Doc & Deck Red-Team that scans the artifact you're about to send for inconsistent numbers, unsourced claims, missing data, accessibility issues, and prior-version contradictions, then returns a severity-ranked punch list with proposed edits.
- Calendar Negotiator — a scheduling chief-of-staff that turns "when can we meet?" threads into a confirmed meeting on your calendar, respecting your focus blocks, energy patterns, and time-zone fairness with the other party.
A separate NemoClaw Policy Setup tab covers the one-time Telegram channel wiring that two of the applications (News Digest and Calendar Negotiator) require and the other two (Software Development Agent and Deck Reviewer) can optionally use for "ready for review" notifications. The Troubleshooting tab collects symptom/cause/fix entries specific to these workflows.
For each application you will be able to read the policy YAML, modify it, hot-reload network changes, and re-create the sandbox when filesystem mounts change.
What to know before starting
- You have completed the NemoClaw on DGX Spark playbook and have a working sandbox (the examples use
my-assistant).
- Basic comfort with the Linux terminal and YAML files.
- Awareness of the agent risk surface — see the Important: security and risks section in the NemoClaw overview.
Prerequisites
Hardware and access:
- A DGX Spark (GB10) with a working NemoClaw install (see NemoClaw on DGX Spark).
- A running OpenShell gateway and a sandbox created by the NemoClaw onboard wizard (
nemoclaw list shows at least one sandbox).
- A Telegram bot wired into the sandbox at onboard time for the Daily Personal News Digest and Calendar Negotiator applications. If you skipped Telegram during onboard, re-run the NemoClaw installer to recreate the sandbox with Telegram enabled. See NemoClaw Policy Setup for the one-time wiring steps.
Software:
- Ollama serving the model you selected during NemoClaw onboard (Nemotron 3 Super 120B in the install playbook).
- A working public webhook tunnel (
nemoclaw tunnel start) for any Telegram-driven application.
Verify the sandbox is healthy before you start:
nemoclaw list
nemoclaw my-assistant status
Expected: your sandbox appears in the list and status reports the sandbox as Running with the inference provider pointing at your local Ollama model.
Have ready before you begin
| Item | Where to get it | Used by |
|---|
Sandbox name from NemoClaw onboard (e.g. my-assistant) | nemoclaw list | All applications |
| Telegram bot token and numeric user ID | @BotFather (/newbot), @userinfobot on Telegram for your user ID | Policy Setup, News Digest, Calendar Negotiator; optional for Software Development Agent and Deck Reviewer |
Allowlist of news source hostnames to add under network_policies | Pick the sites you trust | News Digest |
| A host directory containing the project you want built and reviewed | A copy/clone of the project, e.g. ~/nemoclaw-projects/my-app/ | Software Development Agent |
A queue folder, a canonical corpus folder, and a profile.yaml for red-team rules | Curate from prior decks, brand guide, and canonical metric files, e.g. ~/nemoclaw-redteam/ | Deck Reviewer |
A calendar.ics export and a profile.yaml with working hours, focus blocks, and timezone | Export from your real calendar (Google: Settings → Import & export) into ~/nemoclaw-calendar/ | Calendar Negotiator |
Ancillary files
All policy snippets and example prompts in this playbook are inline in the application tabs — there are no external assets to clone. The bundled sandbox policy is shipped with NemoClaw and OpenShell; the application tabs only modify it.
Time and risk
- Estimated time: 30–45 minutes to walk through all four applications. Each application individually takes 5–10 minutes once the prerequisites are in place. Plan an extra 10 minutes for the one-time Policy Setup tab if you have not enabled Telegram yet.
- Risk level: Medium. Every application grants the agent additional capability beyond the default sandbox — outbound network for the news digest, filesystem access for code review, deck red-team, and calendar negotiation. Risk is reduced by tight per-application policies (split read-only / read-write mounts, explicit egress allowlists, in-prompt safety rules that survive single-message overrides) but is not eliminated. Do not point these recipes at sensitive data, production accounts, or personal files without reviewing the policy first.
- Rollback: Each application tab includes a rollback section that either reverts the policy (network changes are hot-reloadable) or destroys and recreates the sandbox with the original policy. The Troubleshooting tab covers common stuck-state recovery. You can always run
nemoclaw uninstall to remove everything.
- Last Updated: 2026-05-18
- First publication — four starter applications (Daily Personal News Digest, Software Development Agent, Deck Reviewer, Calendar Negotiator) plus a shared NemoClaw Policy Setup tab.
