Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Docs: Add 'Out-of-the-Box Capabilities' reference page per platform [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#51033•Fetched 2026-04-08 01:05:17
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
0
Author
SQLOPTIMISESQLOPTIMISE
Participants
astroclawastroclawSQLOPTIMISESQLOPTIMISE
Timeline (top)
commented ×1

Root Cause

  • Reduces user frustration and drop-off in the first week
  • Sets correct expectations before installation
  • Helps users plan what integrations they need
  • Makes the value proposition clearer for different use cases
RAW_BUFFERClick to expand / collapse

Problem

New users install OpenClaw expecting it to "just work" with their local devices, smart home, network services, etc. The current Getting Started guide covers installation and first message, but nowhere in the docs does it clearly state what the agent can and cannot do out of the box — or what requires additional setup.

Real-world example

A non-technical user installed OpenClaw on a NUC running Linux. After 5 days of trying to get the agent to interact with local devices and services, they hit a wall — not because it was impossible, but because nothing told them what was included vs. what needed configuration.

The gap between "installed and chatting" and "actually useful for my use case" is invisible in the current docs.

Proposed Solution

Add a new docs page (e.g. docs/capabilities/out-of-the-box.md or docs/start/what-can-it-do.md) that clearly documents:

1. Built-in capabilities (no extra setup)

  • File system access (workspace)
  • Shell command execution (sandboxed)
  • Web search (Brave API — requires key)
  • Web fetch / URL reading
  • Browser automation (Playwright)
  • Image/PDF analysis
  • Memory system
  • Cron jobs and heartbeats
  • Multi-channel messaging (once channels configured)

2. Capabilities requiring additional setup

  • MCP servers (for external service integrations)
  • Skills (ClawHub installable extensions)
  • SSH access to other machines
  • Smart home / IoT (Home Assistant MCP, etc.)
  • Google Workspace (OAuth setup)
  • CRM integrations (API keys)
  • Custom API integrations

3. Platform-specific notes

  • macOS: iMessage via BlueBubbles, native browser, full exec
  • Linux (server/NUC/Pi): headless browser, full exec, ideal for always-on
  • Windows: WSL2 recommended, native support available
  • Docker: sandboxed, networking considerations

4. "What do I need for X?" quick reference

A table mapping common user goals to what is needed:

I want to...Built-in?What you need
Chat with AI from my phone✅ (after channel setup)Telegram bot token or WhatsApp pairing
Read/write local files✅Nothing extra
Search the web✅Brave API key
Control smart home devices❌Home Assistant MCP server
Access Google Drive❌OAuth setup (gog CLI or similar)
Monitor a website✅Web fetch + cron
Run code✅Sandboxed by default

Why This Matters

  • Reduces user frustration and drop-off in the first week
  • Sets correct expectations before installation
  • Helps users plan what integrations they need
  • Makes the value proposition clearer for different use cases

Additional Context

This would sit naturally in the Getting Started flow — after installation, before channel setup. Could also be linked from the main README.

Happy to contribute the initial draft as a PR.

extent analysis

Fix Plan

To address the issue, we will create a new documentation page that clearly outlines the capabilities of OpenClaw. Here are the steps:

  • Create a new Markdown file out-of-the-box.md in the docs/capabilities directory.
  • Add the following sections:
    • Built-in capabilities
    • Capabilities requiring additional setup
    • Platform-specific notes
    • "What do I need for X?" quick reference
  • Use the proposed solution as a starting point for the content.

Example code for the quick reference table:

### "What do I need for X?" quick reference
| I want to... | Built-in? | What you need |
|---|---|---|
| Chat with AI from my phone | | Telegram bot token or WhatsApp pairing |
| Read/write local files | | Nothing extra |
| Search the web | | Brave API key |
| Control smart home devices | | Home Assistant MCP server |
| Access Google Drive | | OAuth setup (gog CLI or similar) |
| Monitor a website | | Web fetch + cron |
| Run code | | Sandboxed by default |
  • Link to the new documentation page from the Getting Started guide and the main README.

Verification

To verify that the fix worked, check that:

  • The new documentation page is accessible and easy to understand.
  • The quick reference table is accurate and helpful.
  • New users can find the information they need to get started with OpenClaw.

Extra Tips

  • Keep the documentation up-to-date with new features and capabilities.
  • Consider adding screenshots or diagrams to illustrate the capabilities and setup process.
  • Use clear and concise language to make the documentation accessible to non-technical users.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#installation#tensor shape#autograd error#parallel task#integration issue#index setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING