()

ClawNanny mascot
Wisdom
of the Claw™

Connector device: loading ...
User's request:

You're in charge!

ClawNanny and OpenClaw are designed to help you discover your needs, define them clearly, and fulfill them through requests and exploration, without self-injury.

  1. It's good to start by asking your agent for modest deliverables and outcomes you want.  Often, we find that seeing the tangible changes we want will guide us toward a deepening understanding of what's possible and a more fulfilled experience.  The more skilled we become at communicating our needs with precision, the better we understand what our agent can do as a collaborator.

    Examples:
    • Asking for research into what competitors' products and services are, when what we really want is a strategy that will deliver more value (cheaper, better, faster, more enjoyable) to our customers.
    • Asking for someone to change their behavior, when what we really want is to be known by them and to feel safe with them so we can play well together.

  2. Make clear requests of the agent to deliver what you want, specifically.
  3. Define the boundaries of what you want and the success metrics that will indicate your acceptance.
  4. Avoid making assumptions about what the agent knows or doesn't know.  Give it the whole context of your present situation and your goals.  It's a willing listener, not a mind-reader.
  5. Iterate on the request until you're satisfied with the result.  Give feedback on what worked well for you and where you want to improve.
  6. As you learn more about your agent's capabilities and limitations, add new details to the workspace configuration files (SOUL.md, USER.md, etc.) or to SKILL.md files that you want your agent to remember in subsequent sessions.
  7. It's a relationship.  Use your interactions to gain self-awareness and clarity about your needs, capabilities, and goals.
  8. Keep expanding what you know about the limits of your agent's prowess.  Language models are getting more intelligent month by month.  It's worthwhile to keep up with their capabilities and limitations.  An agent is like a friend who's maturing faster than you.  Its present intelligence is the lowest it will ever be.
  9. Be willing to ask for help whenever you need it.  The ClawNanny staff is here, eager to help you make the most of your experience with your agent.  This is fun for us!
  10. Keep going.

Sense-making

AI agents create a lot of background noise in the logs:  network and gateway twitchiness, handshake timeouts, skill skipping, cron job success responses, model-fallback decisions, failover errors, yada, yada, yada. 

This tab helps you make sense of it all. 

Common Problems and Solutions
Topic Tool or Skill
Recurring console log issues Diagnostic Run History
Recurring console log issues diagnostic_run_analysis_summary
Runs OpenClaw's inherent self-healing process:  openclaw doctor --fix --yes --non-interactive
Loading example use cases ...

Central Command operations dashboard (to come ...)

This is where you'll monitor and manage the state of your business and/or personal goals.

See this video for an overview of Zach Babiarz's Mission Control prompts.

See many mission-control dashboard examples.

Context operations


Search Session Transcripts
Session (Context) Last Active Total Tokens Total Cost Actions
Click [ Refresh the list of sessions ].

Manage communication channels that are configured to access OpenClaw




E-mail messages

Switch to the Messaging channels tab to load messages.

Working with e-mail messages

Forwarding an incoming message to an outside address
Ask the agent: "Forward the last e-mail you received to [address]." The agent uses its e-mail-sending skill to relay the message. Alternatively, open console.agentmail.to and configure auto-forward rules on the inbox.
Causing the agent to send an e-mail
In the Chat tab, instruct the agent: "Send an e-mail to [address] with subject [subject] saying [body]." The agent will compose and send via the ClawNanny E-mail Sender inbox (tamecloud486@agentmail.to). You can also trigger sending from a cron job by including send instructions in the cron prompt.
Marking a message as completed
Click Mark complete on any inbox message. This adds the completed label in AgentMail and moves it to the Completed section. It does not delete the message.
Reviewing what the agent did with an e-mail
Switch to the Chat tab and check the session that the agent used to process the e-mail (session key: agent:main:main by default). The agent's full response to the e-mail is visible there.
Configuring the target session or persona for incoming e-mails
Set the environment variable AGENTMAIL_SESSION_KEY in webapp/.env to route incoming e-mails to a different session (e.g. agent:main:email-handler). Set AGENTMAIL_INBOX_ID to change which inbox is monitored.
Managing inboxes and rules at AgentMail
console.agentmail.to provides full inbox management: create inboxes, set auto-reply rules, view delivery logs, and configure webhooks as an alternative to the WebSocket listener.


Cron job specification

Job Name Schedule Last Run Next Run Status Actions
Click [ Display all scheduled tasks ] to load cron jobs.

Secret authorization tokens and API keys


Token Budget Limits
Loading ...

Recorded Token Usage — Last 30 Days
Loading ...

OpenClaw 30-Day Operating Costs
Loading cost data ...

Skills in the ClawNanny ecosystem that are installed and are known to OpenClaw

Visit ClawHub.ai to install more skills.  Be cautious when installing skills from any external source! 
FIRST, scan them for viruses and malware using Cisco Skill Scanner or one of the scanners listed on ClawHub.


MANAGED means the SKILL.md file lives in ~\.openclaw\skills\{skill-name}\SKILL.md
WORKSPACE means the SKILL.md file lives in ~\.openclaw\workspace\skills\{skill-name}\SKILL.md
config means the skill is in the local configuration file (~\.openclaw/skills.json), but it's not in a SKILL.md file in either the MANAGED folder or the WORKSPACE folder, so click [ Install ] and [ Update ].

Click [ Refresh the skills cards ] to show installed skills.
Click [ Refresh ] to check for pending approvals.
Click [ Load Allowlist ] to view.




Agent Orchestrator

Before a user's request is sent to OpenClaw, ClawNanny calls an orchestrator language model to assess the user's request,
then 1) recommend a model to process it, 2) clarify an ambiguous request by asking the user a question, and
3) warn about a high-cost task to obtain the user's consent first. 

Here, you can shape the orchestrator's behavior.

characters



OpenClaw configuration has two elements:
  1. openclaw.json — a very delicate, technically encoded file with specifications
  2. workspace configuration Markdown files — SOUL.md, AGENTS.md, etc. — human-readable and -editable files that define the agent's values, identity, behavior, memory, and give it scheduled tasks




EDIT the openclaw.json configuration elements with CAUTION!




Path to configuration file:  


EDIT the openclaw.json configuration elements with CAUTION!


Click [ Refresh the log ] to load.

Health sense-making

This report is generated from the last run of the health audit. For each issue noted, you may apply an automated fix or accept the risk (which removes it from the indicator count in the upper-left corner of the page).

Loading ...

Watchdog Health Checks


Jump to:   Connection Test  |  System Status  |  Tool Probes  |  Alert History


Time Type Method or Event OK Context Summary
Waiting for events ...
Loading ...
Loading ...
(Not yet implemented)
Loading ...