mirror of
https://github.com/kamranahmedse/developer-roadmap.git
synced 2026-08-30 17:57:21 +08:00
Delete src/data/roadmaps/open-claw/content directory
This commit is contained in:
Javier Canales
@@ -1,3 +0,0 @@
|
||||
# Adding Daemon
|
||||
|
||||
A daemon is a background process that runs continuously without needing a terminal window open. Configuring Open Claw as a daemon ensures it starts automatically and keeps running even after you log out or restart your machine.
|
||||
@@ -1,7 +0,0 @@
|
||||
# Adding First Channel
|
||||
|
||||
After setting up your model provider, the next step is connecting a communication channel, in other words, the platform where you will actually talk to your agent. Telegram is recommended as the fastest channel to get started with.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Channels](https://docs.openclaw.ai/channels)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Agent Loop
|
||||
|
||||
When Open Claw receives a message, it runs a full agent loop rather than returning a single response. The loop validates the message, resolves the model, assembles the system prompt from skills and context files, and then sends everything to the model for inference. If the model decides to call a tool, like running a command, reading a file, or searching the web, the loop executes it, feeds the result back to the model, and continues until no more tool calls are needed and a final reply is ready. If the session gets too long for the context window, compaction kicks in automatically before retrying.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Agent Loop](https://docs.openclaw.ai/concepts/agent-loop)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Agent Loop
|
||||
|
||||
When Open Claw receives a message, it runs a full agent loop rather than returning a single response. The loop validates the message, resolves the model, assembles the system prompt from skills and context files, and then sends everything to the model for inference. If the model decides to call a tool, like running a command, reading a file, or searching the web, the loop executes it, feeds the result back to the model, and continues until no more tool calls are needed and a final reply is ready. If the session gets too long for the context window, compaction kicks in automatically before retrying.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Agent Loop](https://docs.openclaw.ai/concepts/agent-loop)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Agents
|
||||
|
||||
An agent in Open Claw is a fully isolated unit with its own workspace folder containing its personality and configuration files, its own state directory that holds auth profiles and the model registry, and its own session store that keeps the full conversation history separate from every other agent. Because auth profiles are scoped per-agent, credentials for one agent are never automatically shared with another, which means you can run a personal agent on your WhatsApp number and a work agent on a separate account on the same Gateway without any risk of their sessions, memories, or API keys crossing over.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Agent Runtime](https://docs.openclaw.ai/concepts/agent)
|
||||
@@ -1,8 +0,0 @@
|
||||
# AGENTS.md
|
||||
|
||||
[AGENTS.md](http://AGENTS.md) describes the agents available in your workspace, their roles, and how they relate to each other. It is used when running multiple agents to clarify who does what.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Default AGENTS.md](https://docs.openclaw.ai/reference/AGENTS.default#default-agents-md)
|
||||
- [@official@AGENTS.md Template](https://docs.openclaw.ai/reference/templates/AGENTS)
|
||||
@@ -1,8 +0,0 @@
|
||||
# /allowlist
|
||||
|
||||
`/allowlist` lists, adds, or removes entries from the sender allowlist that controls who can interact with the agent. Add and remove operations require `commands.config: true` to be set in your configuration.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Slash Commands](https://docs.openclaw.ai/tools/slash-commands)
|
||||
- [@official@Allowlists (DM + groups) - terminology](https://docs.openclaw.ai/gateway/security#allowlists-dm-+-groups-terminology)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Anthropic
|
||||
|
||||
Anthropic is the company behind the Claude family of models. Connecting Open Claw to Anthropic lets you use Claude as your agent's underlying model, which is well-suited for reasoning, writing, and tool use.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Anthropic Provider](https://docs.openclaw.ai/providers/anthropic)
|
||||
@@ -1,8 +0,0 @@
|
||||
# Auth & Model Providers
|
||||
|
||||
This section covers how to connect Open Claw to AI model providers like Anthropic, OpenAI, Gemini, or Ollama by entering your API credentials. The model provider is what powers the agent's intelligence.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Provider Directory](https://docs.openclaw.ai/providers)
|
||||
- [@official@Provider Quickstart](https://docs.openclaw.ai/providers/models)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Automating Tasks
|
||||
|
||||
Open Claw supports several mechanisms for running tasks automatically, including hooks, webhooks, heartbeats, and cron jobs, so your agent can act without waiting for a human to send a message.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Automation Overview](https://docs.openclaw.ai/automation)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Azure
|
||||
|
||||
Azure is Microsoft's cloud platform offering a wide range of infrastructure options. It is a valid choice for hosting Open Claw, particularly for users already in the Microsoft ecosystem.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Azure Hosting](https://docs.openclaw.ai/install/azure)
|
||||
@@ -1,7 +0,0 @@
|
||||
# openclaw backup create
|
||||
|
||||
`openclaw backup create` generates a snapshot of your Open Claw configuration and memory files so you can restore your setup if something goes wrong.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@backup](https://docs.openclaw.ai/cli/backup#backup)
|
||||
-8
@@ -1,8 +0,0 @@
|
||||
# Bind the Gateway to Localhost
|
||||
|
||||
Binding to localhost means the gateway only accepts connections from the same machine, not from the open internet. You can then use a reverse proxy or Tailscale to selectively expose it.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Gateway Runbook](https://docs.openclaw.ai/gateway)
|
||||
- [@official@Tailscale](https://docs.openclaw.ai/gateway/tailscale)
|
||||
@@ -1,7 +0,0 @@
|
||||
# openclaw channels add --channel
|
||||
|
||||
`openclaw channels add --channel` adds a new communication channel to your Open Claw setup, specifying which platform to connect.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Add / remove accounts](https://docs.openclaw.ai/cli/channels#add-/-remove-accounts)
|
||||
@@ -1,7 +0,0 @@
|
||||
# openclaw channels list
|
||||
|
||||
`openclaw channels list` displays all the communication channels currently connected to your Open Claw gateway, along with their status.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Common Commands](https://docs.openclaw.ai/cli/channels#add-/-remove-accounts)
|
||||
@@ -1,7 +0,0 @@
|
||||
# openclaw channels login
|
||||
|
||||
`openclaw channels login` initiates the authentication flow for a specific channel, allowing Open Claw to connect to it on your behalf.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Login / logout (interactive)](https://docs.openclaw.ai/cli/channels#add-/-remove-accounts)
|
||||
@@ -1,7 +0,0 @@
|
||||
# openclaw channels remove --channel
|
||||
|
||||
`openclaw channels remove --channel` disconnects and removes a channel from your Open Claw configuration.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Add / remove accounts](https://docs.openclaw.ai/cli/channels#add-/-remove-accounts)
|
||||
@@ -1,7 +0,0 @@
|
||||
# openclaw channels status --probe
|
||||
|
||||
`openclaw channels status --probe` actively checks the connection status of your channels by probing them, rather than just reporting cached status.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Status / capabilities / resolve / logs](https://docs.openclaw.ai/cli/channels#status-/-capabilities-/-resolve-/-logs)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Channels
|
||||
|
||||
Channels are the messaging platforms through which users interact with Open Claw, and each one connects to the single Gateway process that routes incoming messages to the right agent and sends replies back. Every channel runs simultaneously on the same Gateway, so you can be connected to Telegram, WhatsApp, Discord, and Slack all at once without running separate processes. Text is supported across all channels, but richer features like reactions, media, message editing, and group behavior vary depending on what each platform's API supports
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Chat Channels](https://docs.openclaw.ai/channels)
|
||||
@@ -1,8 +0,0 @@
|
||||
# /compact
|
||||
|
||||
`/compact` is a text-only command that compresses or summarizes the current conversation context to free up space in the context window without losing essential information. You can optionally pass instructions to guide how the compaction is done.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Slash Commands](https://docs.openclaw.ai/tools/slash-commands)
|
||||
- [@official@Compaction](https://docs.openclaw.ai/concepts/compaction)
|
||||
@@ -1,8 +0,0 @@
|
||||
# /config
|
||||
|
||||
`/config` reads and writes your on-disk `openclaw.json` configuration file directly from chat. It is disabled by default and requires `commands.config: true` in your config to enable. It supports `show`, `get`, `set`, and `unset` subcommands and is owner-only.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Config updates](https://docs.openclaw.ai/tools/slash-commands#config-updates)
|
||||
- [@official@Gateway Configuration](https://docs.openclaw.ai/gateway/configuration)
|
||||
@@ -1,8 +0,0 @@
|
||||
# Context Window
|
||||
|
||||
The context window is the amount of conversation history, instructions, and tool results the AI model can see at once when generating a response. Open Claw manages this carefully through a context engine and compaction system so long-running agents don't exceed the model's limits.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Context](https://docs.openclaw.ai/concepts/context)
|
||||
- [@official@Context Engine](https://docs.openclaw.ai/concepts/context-engine)
|
||||
@@ -1,7 +0,0 @@
|
||||
# /context
|
||||
|
||||
`/context` explains what context the agent is currently working with. You can use `/context list` for a summary, `/context detail` for a breakdown of per-file, per-tool, per-skill, and system prompt sizes, or `/context json` for machine-readable output.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Slash Commands](https://docs.openclaw.ai/tools/slash-commands#command-list)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Creating Plugins
|
||||
|
||||
You can build your own plugins to add custom functionality to Open Claw, such as integrating a new service or adding a new type of tool the agent can call.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Building Plugins](https://docs.openclaw.ai/plugins/building-plugins)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Creating Skills
|
||||
|
||||
You can write your own skills by creating a `SKILL.md` file with instructions and placing it in your workspace's `skills/` folder. This lets you teach the agent new behaviors tailored to your specific needs.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Creating Skills](https://docs.openclaw.ai/tools/creating-skills)
|
||||
@@ -1,8 +0,0 @@
|
||||
# openclaw cron add
|
||||
|
||||
`openclaw cron add` registers a new scheduled task, letting you define what the agent should do and when it should trigger automatically.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Scheduled Tasks](https://docs.openclaw.ai/automation/cron-jobs)
|
||||
- [@official@Cron](https://docs.openclaw.ai/cli/index#cron)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Cron Jobs
|
||||
|
||||
Cron jobs are scheduled tasks that run at specific times or intervals. They allow you to automate recurring actions like summaries, cleanups, or reports without any human prompt.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Scheduled Tasks](https://docs.openclaw.ai/automation/cron-jobs)
|
||||
@@ -1,8 +0,0 @@
|
||||
# openclaw cron list
|
||||
|
||||
`openclaw cron list` shows all the scheduled tasks currently registered in Open Claw along with their schedules and status.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Scheduled Tasks](https://docs.openclaw.ai/automation/cron-jobs)
|
||||
- [@official@Cron](https://docs.openclaw.ai/cli/index#cron)
|
||||
@@ -1,8 +0,0 @@
|
||||
# Dedicated Hardware
|
||||
|
||||
Running Open Claw on dedicated hardware means using a physical device like a Raspberry Pi or Mac Mini that runs continuously in your home or office. This gives you full control and low ongoing costs with no monthly cloud fees.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Rasberry Pi](https://docs.openclaw.ai/install/raspberry-pi#raspberry-pi)
|
||||
- [@official@macOS VMs](https://docs.openclaw.ai/install/macos-vm#macos-vms)
|
||||
-8
@@ -1,8 +0,0 @@
|
||||
# Deploy on an Isolated VPS, VM, or Dedicated Device
|
||||
|
||||
Running Open Claw on a dedicated, isolated machine rather than your personal computer limits the blast radius if something goes wrong and keeps your agent separate from your sensitive personal data.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Security](https://docs.openclaw.ai/gateway/security)
|
||||
- [@official@Remote Access](https://docs.openclaw.ai/gateway/remote#macos-persistent-ssh-tunnel-via-launchagent)
|
||||
@@ -1,7 +0,0 @@
|
||||
# DigitalOcean
|
||||
|
||||
DigitalOcean is a cloud provider that offers simple, affordable virtual machines called Droplets. It is a popular choice for self-hosting Open Claw due to its straightforward pricing and easy setup process.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@DigitalOcean Hosting](https://docs.openclaw.ai/install/digitalocean#digitalocean)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Discord
|
||||
|
||||
Discord is a chat platform popular in gaming and developer communities. Open Claw connects to it via the Discord Bot API and Gateway, supporting servers, channels, and DMs.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Discord Channel](https://docs.openclaw.ai/channels/discord)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Docker / Isolated Install
|
||||
|
||||
Docker lets you run Open Claw inside a container, an isolated environment that keeps it separate from the rest of your system. This makes installation cleaner, reduces conflicts with other software, and makes it easier to remove or update later.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Docker Install](https://docs.openclaw.ai/install/docker)
|
||||
@@ -1,8 +0,0 @@
|
||||
# openclaw doctor --deep
|
||||
|
||||
`openclaw doctor --deep` is an extended version of `openclaw doctor` that performs a more thorough diagnostic check, scanning system services for extra gateway installs and deeper configuration issues that the standard check might miss. You can add the `--yes` flag to automatically accept any prompts without manual input, which is useful for running the command in a headless or
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Doctor](https://docs.openclaw.ai/gateway/doctor)
|
||||
- [@official@doctor](https://docs.openclaw.ai/cli/doctor)
|
||||
@@ -1,8 +0,0 @@
|
||||
# openclaw doctor --deep
|
||||
|
||||
`openclaw doctor --deep` is an extended version of `openclaw doctor` that performs a more thorough diagnostic check, scanning system services for extra gateway installs and deeper configuration issues that the standard check might miss. You can add the `--yes` flag to automatically accept any prompts without manual input, which is useful for running the command in a headless or
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Doctor](https://docs.openclaw.ai/gateway/doctor)
|
||||
- [@official@doctor](https://docs.openclaw.ai/cli/doctor)
|
||||
@@ -1,8 +0,0 @@
|
||||
# openclaw doctor
|
||||
|
||||
The `openclaw doctor` command checks your Open Claw installation for common configuration problems and misconfigurations. It is the first thing to run when something is not working as expected.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Doctor](https://docs.openclaw.ai/gateway/doctor)
|
||||
- [@official@doctor](https://docs.openclaw.ai/cli/doctor)
|
||||
-8
@@ -1,8 +0,0 @@
|
||||
# Enable Device Pairing and Maintain a Minimal Sender Allowlist
|
||||
|
||||
Device pairing ensures only verified devices can talk to your agent. Keeping the allowlist minimal means only the people or systems you explicitly trust can send it messages.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Pairing](https://docs.openclaw.ai/channels/pairing#pairing)
|
||||
- [@official@Allowlists (DM + groups) - terminology](https://docs.openclaw.ai/gateway/security/index#allowlists-dm-+-groups-terminology)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Event Types
|
||||
|
||||
Open Claw hooks support a range of event types, including command events like `/new` and `/reset`, session events like compaction, agent bootstrap events, gateway startup events, and message received and sent events.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Event Types](https://docs.openclaw.ai/automation/hooks#event-types)
|
||||
@@ -1,8 +0,0 @@
|
||||
# /fast
|
||||
|
||||
`/fast` is a directive that toggles fast mode for the current session. It takes `on`, `off`, or `status` as arguments. Fast mode maps to different provider-level behaviors depending on your model — for example, `service_tier=priority` on OpenAI or `service_tier=auto` on Anthropic. Omitting the argument shows the current effective fast-mode state.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Fast mode (/fast)](https://docs.openclaw.ai/tools/thinking#fast-mode-/fast)
|
||||
- [@official@Slash Commands](https://docs.openclaw.ai/tools/slash-commands)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Gateway Settings
|
||||
|
||||
Gateway settings control how the Open Claw server behaves, including the port it listens on, authentication tokens, and which interfaces it binds to. These settings are critical for both functionality and security.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Gateway Configuration](https://docs.openclaw.ai/gateway/configuration)
|
||||
-8
@@ -1,8 +0,0 @@
|
||||
# openclaw gateway start | stop | restart
|
||||
|
||||
`openclaw gateway start`, `openclaw gateway stop`, and `openclaw gateway restart` control the lifecycle of the Open Claw gateway process, starting it up, shutting it down, or restarting it after a configuration change.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Gateway Runbook](https://docs.openclaw.ai/gateway)
|
||||
- [@official@Manage the Gateway service](https://docs.openclaw.ai/cli/gateway#manage-the-gateway-service)
|
||||
@@ -1,8 +0,0 @@
|
||||
# openclaw gateway
|
||||
|
||||
`openclaw gateway` is the main command for interacting with the gateway process. It is the entry point for all gateway-related operations from the command line.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Gateway Runbook](https://docs.openclaw.ai/gateway)
|
||||
- [@official@gateway](https://docs.openclaw.ai/cli/gateway#gateway)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Gateway
|
||||
|
||||
The Gateway is the single always-on process that handles routing, the control plane, and all channel connections. It runs on a single multiplexed port that serves the WebSocket control and RPC interface, HTTP APIs, the Control UI, and hooks. By default, it binds to localhost and requires an auth token before accepting any connections.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Gateway Runbook](https://docs.openclaw.ai/gateway)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Gemini
|
||||
|
||||
Gemini is Google's family of AI models. Open Claw supports Gemini as an alternative model provider, giving you access to Google's AI infrastructure for powering your agents.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@article@Google (Gemini) Provider](https://docs.openclaw.ai/providers/google)
|
||||
@@ -1,8 +0,0 @@
|
||||
# openclaw gateway
|
||||
|
||||
`openclaw gateway` is the main command for interacting with the gateway process. It is the entry point for all gateway-related operations from the command line.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Gateway Runbook](https://docs.openclaw.ai/gateway)
|
||||
- [@official@gateway](https://docs.openclaw.ai/cli/gateway#gateway)
|
||||
@@ -1,8 +0,0 @@
|
||||
# HEARTBEAT.md
|
||||
|
||||
HEARTBEAT.md is a workspace configuration file where you define what the agent should do during each heartbeat cycle — essentially a set of instructions for proactive, time-based behavior.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@HEARTBEAT.md](https://docs.openclaw.ai/gateway/heartbeat#heartbeat-md-optional)
|
||||
- [@official@HEARTBEAT.md Template](https://docs.openclaw.ai/reference/templates/HEARTBEAT)
|
||||
@@ -1,8 +0,0 @@
|
||||
# Heartbeats
|
||||
|
||||
Heartbeats are periodic signals the Gateway emits on a regular interval. They can be used to confirm the agent is alive and to trigger recurring background tasks without any human input.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Scheduled Tasks (Cron) vs Heartbeat](https://docs.openclaw.ai/automation#scheduled-tasks-cron-vs-heartbeat)
|
||||
- [@official@Heartbeat](https://docs.openclaw.ai/gateway/heartbeat)
|
||||
@@ -1,7 +0,0 @@
|
||||
# /help
|
||||
|
||||
`/help` displays a list of available slash commands and a brief description of what each one does. It also works as an inline shortcut, meaning it can be embedded in a normal message and will be stripped before the model sees the rest of the text.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Slash Commands](https://docs.openclaw.ai/tools/slash-commands)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Hetzner
|
||||
|
||||
Hetzner is a German cloud and hosting provider known for competitive pricing on VPS and dedicated servers, making it a cost-effective option for running Open Claw in Europe.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Hetzner Hosting](https://docs.openclaw.ai/install/hetzner)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Hook Structure
|
||||
|
||||
Each hook is a directory containing a `HOOK.md` file with metadata and a `handler.ts` file with the logic to run. The metadata defines which events to listen for and what requirements the hook needs to be eligible.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Hook Structure](https://docs.openclaw.ai/automation/hooks#hook-structure)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Hooks
|
||||
|
||||
Hooks are small scripts that run inside the Gateway when specific agent events fire, like `/new`, `/reset`, `/stop`, or lifecycle events. They are automatically discovered from directories and can be inspected with `openclaw hooks`.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Hooks](https://docs.openclaw.ai/automation/hooks)
|
||||
@@ -1,10 +0,0 @@
|
||||
# undefined
|
||||
|
||||
#How Open Claw Works
|
||||
|
||||
Open Claw runs a single long-lived Gateway that owns all messaging surfaces and exposes a typed WebSocket API for control-plane clients like the macOS app, CLI, and web UI. When a message arrives, the Gateway routes it to the appropriate agent, which then runs through a full loop of context assembly, model inference, and tool execution before streaming a reply back.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@OpenClaw Overview](https://docs.openclaw.ai/)
|
||||
- [@official@Gateway Architecture](https://docs.openclaw.ai/concepts/architecture)
|
||||
@@ -1,7 +0,0 @@
|
||||
# iMessage
|
||||
|
||||
iMessage is Apple's built-in messaging system. The recommended way to connect it to Open Claw is via BlueBubbles, a macOS server that provides a full-featured REST API for iMessage integration.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@BlueBubbles Channel](https://docs.openclaw.ai/channels/bluebubbles)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Installation
|
||||
|
||||
Installation covers the steps to get Open Claw onto your chosen environment. It requires a recent version of Node.js, an API key from your chosen model provider, and takes around five minutes. The core install command is `npm install -g openclaw@latest`, after which you run openclaw onboard to connect your first model and channel. Always check the official documentation for the current Node.js version requirements before installing, as these may change between releases.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Getting Started](https://docs.openclaw.ai/start/getting-started)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Installation
|
||||
|
||||
Installation covers the steps to get Open Claw onto your chosen environment. It requires a recent version of Node.js, an API key from your chosen model provider, and takes around five minutes. Always check the official documentation for the current Node.js version requirements before installing, as these may change between releases.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Installation](https://docs.openclaw.ai/install)
|
||||
@@ -1,8 +0,0 @@
|
||||
# Installing from ClawHub
|
||||
|
||||
ClawHub is a community repository of pre-built skills. You can browse and install skills from ClawHub directly, saving time compared to building them from scratch.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@ClawHub](https://clawhub.ai/)
|
||||
- [@official@What is ClawHub?](https://docs.openclaw.ai/tools/clawhub)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Installing Plugins
|
||||
|
||||
Plugins are installed via `openclaw plugins install` followed by the package name or path. Once installed, they become available to all agents in your workspace.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Install and Configure](https://docs.openclaw.ai/tools/plugin)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Interval & Active Hours
|
||||
|
||||
You can configure how often heartbeats fire and restrict them to certain hours of the day, so your agent only runs automated tasks during times you define as active.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Heartbeat](https://docs.openclaw.ai/gateway/heartbeat#heartbeat-gateway)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Introduction
|
||||
|
||||
Open Claw is a self-hosted AI agent gateway that connects your messaging apps to AI models you control. You run a single Gateway process on your own machine or server, and it becomes the bridge between platforms like Telegram, WhatsApp, Discord, Slack, Signal, and more, and an always-available AI assistant. It is MIT-licensed, open source, and designed for developers and power users who want a personal AI they can message from anywhere without giving up control of their data.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Open Claw Docs](https://docs.openclaw.ai/)
|
||||
@@ -1,3 +0,0 @@
|
||||
# Limitations
|
||||
|
||||
Running Open Claw on dedicated hardware like a Raspberry Pi or Mac Mini gives you full control and no ongoing cloud fees, but the hardware itself is a constraint. Low-powered devices like a Raspberry Pi may struggle with memory-intensive tasks or multiple simultaneous agent sessions, and any hardware failure means your agent goes offline until you physically fix or replace the device. You are also still dependent on your home internet connection for external access, which may be unreliable, have changing IP addresses, or block incoming traffic by default.
|
||||
@@ -1,8 +0,0 @@
|
||||
# Limitations
|
||||
|
||||
Running Open Claw on a local machine means your agent is completely unreachable whenever your computer is off, asleep, or restarting. Most home internet connections also block unsolicited incoming traffic by default, which makes it difficult for external services to trigger your agent via webhooks. On top of that, your home IP address may change periodically depending on your internet provider, which can break any external connections you have configured. For anything beyond personal experimentation, a VPS or dedicated device is a more reliable choice.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Platforms](https://docs.openclaw.ai/platforms)
|
||||
- [@official@Remote Access](https://docs.openclaw.ai/gateway/remote)
|
||||
@@ -1,3 +0,0 @@
|
||||
# Limitations
|
||||
|
||||
Running Open Claw on a VPS or cloud server solves the uptime problem of a local machine but introduces its own constraints. You are paying a recurring monthly fee for the server, which adds up over time, especially if you need more resources to handle heavier workloads. Performance is also constrained by the size of the VPS you choose, and cheaper tiers may struggle with memory-intensive tasks or multiple simultaneous agent sessions. Finally, you are dependent on your cloud provider's availability, so any outages on their end will take your agent offline until they are resolved.
|
||||
@@ -1,7 +0,0 @@
|
||||
# Local Machine
|
||||
|
||||
Running Open Claw on your local machine means installing it directly on your personal computer. This is the quickest way to get started and is good for experimentation, though it comes with limitations around uptime and accessibility from outside your network.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Getting Started](https://docs.openclaw.ai/start/getting-started)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Mac Mini
|
||||
|
||||
A Mac Mini is a compact desktop computer that works well as a home server for Open Claw. It is more powerful than a Raspberry Pi and runs macOS, which may simplify setup for Mac users.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@macOS VMs Hosting](https://docs.openclaw.ai/install/macos-vm#macos-vms)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Managing & Disabling Jobs
|
||||
|
||||
You can list, pause, and delete cron jobs from the command line, giving you control over which scheduled tasks are active at any given time.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Managing jobs](https://docs.openclaw.ai/automation/cron-jobs#managing-jobs)
|
||||
@@ -1,8 +0,0 @@
|
||||
# /mcp
|
||||
|
||||
`/mcp` manages OpenClaw-managed MCP server definitions from chat. It is disabled by default and requires `commands.mcp: true` to enable. It supports `show`, `get`, `set`, and `unset` subcommands and is owner-only
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@MCP Updates](https://docs.openclaw.ai/tools/slash-commands#mcp-updates)
|
||||
- [@official@mcp](https://docs.openclaw.ai/cli/mcp#mcp)
|
||||
@@ -1,7 +0,0 @@
|
||||
# MCP
|
||||
|
||||
MCP (Model Context Protocol) is an open standard for connecting AI models to external tools and data sources. Open Claw supports MCP, allowing your agent to call tools from any MCP-compatible server.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@mcp](https://docs.openclaw.ai/cli/mcp#mcp)
|
||||
@@ -1,8 +0,0 @@
|
||||
# openclaw memory index
|
||||
|
||||
`openclaw memory index` rebuilds the search index for all memory files, ensuring the agent can efficiently retrieve relevant information from its stored memories.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Memory overview](https://docs.openclaw.ai/concepts/memory#memory-overview)
|
||||
- [@official@memory](https://docs.openclaw.ai/cli/index#memory)
|
||||
@@ -1,7 +0,0 @@
|
||||
# openclaw memory search "query"
|
||||
|
||||
`openclaw memory search "query"` lets you search through the agent's stored memories using a keyword or phrase, useful for checking what the agent has remembered about past conversations or preferences.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Memory](https://docs.openclaw.ai/cli/index#memory)
|
||||
@@ -1,8 +0,0 @@
|
||||
# Memory System
|
||||
|
||||
The memory system allows Open Claw agents to remember information across conversations. Instead of starting fresh every time, agents can store and retrieve facts, past interactions, or user preferences from structured memory files in the workspace. Open Claw also includes a compaction system that automatically summarizes older conversation history when a session grows too long, preserving the essential information while freeing up space for new exchanges.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Memory](https://docs.openclaw.ai/concepts/memory)
|
||||
- [@official@Compaction](https://docs.openclaw.ai/concepts/compaction)
|
||||
@@ -1,8 +0,0 @@
|
||||
# MEMORY.md
|
||||
|
||||
[MEMORY.md](http://MEMORY.md) is a persistent file where the agent stores important facts it has learned over time. It is regularly updated so the agent can recall relevant information in future conversations.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Memory Overview](https://docs.openclaw.ai/concepts/memory#memory-overview)
|
||||
- [@official@MEMORY.md - Your Long-Term Memory](https://docs.openclaw.ai/reference/templates/AGENTS#-memory-md-your-long-term-memory)
|
||||
@@ -1,7 +0,0 @@
|
||||
# memory/YYYY-MM-DD.md
|
||||
|
||||
These are dated memory log files that store a record of what happened on a specific day. They give the agent a chronological history that it can reference when needed, and are created automatically by the session-memory hook.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Memory Overview](https://docs.openclaw.ai/concepts/memory)
|
||||
@@ -1,7 +0,0 @@
|
||||
# /model
|
||||
|
||||
`/model` is a directive that lets you switch the AI model the agent is currently using. You can pass a number from the model picker, a full `provider/model` string, or use `/model list` to see available options.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Model selection (/model)](https://docs.openclaw.ai/tools/slash-commands#model-selection-/model)
|
||||
-8
@@ -1,8 +0,0 @@
|
||||
# openclaw models auth add
|
||||
|
||||
`openclaw models auth add` is the interactive auth helper. It can launch a provider auth flow (OAuth/API key) or guide you into manual token paste, depending on the provider you choose.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Model Providers](https://docs.openclaw.ai/concepts/model-providers#model-providers)
|
||||
- [@official@Auth Providers](https://docs.openclaw.ai/cli/models#auth-profiles)
|
||||
@@ -1,8 +0,0 @@
|
||||
# openclaw models auth add
|
||||
|
||||
`openclaw models auth add` is the interactive auth helper. It can launch a provider auth flow (OAuth/API key) or guide you into manual token paste, depending on the provider you choose.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Model Providers](https://docs.openclaw.ai/concepts/model-providers#model-providers)
|
||||
- [@official@Auth Providers](https://docs.openclaw.ai/cli/models#auth-profiles)
|
||||
@@ -1,8 +0,0 @@
|
||||
# openclaw models auth setup-token
|
||||
|
||||
`openclaw models auth setup-token` stores the authentication token for a model provider, allowing Open Claw to make authenticated API calls on your behalf. It is part of the broader `models auth` command group, which also includes `add`, `login`, and `paste-token`.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Model Providers](https://docs.openclaw.ai/concepts/model-providers#model-providers)
|
||||
- [@official@Auth Providers](https://docs.openclaw.ai/cli/models#auth-profiles)
|
||||
@@ -1,9 +0,0 @@
|
||||
# openclaw models list | set | status
|
||||
|
||||
`openclaw models list`, `openclaw models set`, and `openclaw models status` let you view the AI models available in your setup, switch between them, and check which one is currently active.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@model list](https://docs.openclaw.ai/concepts/models#models-list)
|
||||
- [@official@models status](https://docs.openclaw.ai/concepts/models#models-status)
|
||||
- [@official@Common commands](https://docs.openclaw.ai/concepts/models?search=openclaw+models+set)
|
||||
@@ -1,8 +0,0 @@
|
||||
# Multi-Agents
|
||||
|
||||
Multi-agent mode lets you run several specialized agents in the same Open Claw gateway, each with its own workspace, auth profiles, and session store. They can operate independently or be coordinated through routing rules and shared memory.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Multi-Agent Routing](https://docs.openclaw.ai/concepts/multi-agent)
|
||||
- [@official@Sub-Agents](https://docs.openclaw.ai/tools/subagents)
|
||||
-7
@@ -1,7 +0,0 @@
|
||||
# Never Hardcode API Keys
|
||||
|
||||
API keys stored directly in code or config files can be accidentally exposed through logs, version control, or error messages. Always use environment variables or a secrets manager instead.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Security](https://docs.openclaw.ai/gateway/security)
|
||||
-7
@@ -1,7 +0,0 @@
|
||||
# Never Trust External Content to Prevent Prompt Injection
|
||||
|
||||
Prompt injection is an attack where malicious text in an email, webpage, or file tricks the agent into taking unintended actions. Treating all external content as untrusted input is a core security principle in Open Claw.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Threat Model](https://docs.openclaw.ai/security/THREAT-MODEL-ATLAS)
|
||||
@@ -1,7 +0,0 @@
|
||||
# /new
|
||||
|
||||
`/new` starts a fresh conversation with the agent, clearing the current context so you are beginning from a clean slate. It also triggers the session-memory hook to save the previous session before resetting. You can optionally pass a model name after `/new` to start the session with a specific model.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Slash Commands](https://docs.openclaw.ai/tools/slash-commands)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Ollama
|
||||
|
||||
Ollama is a tool that lets you run open-source AI models locally on your own hardware, making it a natural fit for Open Claw setups where privacy, cost, or offline availability are a priority. It shines most in dedicated hardware setups like a Mac Mini or a capable home server, where you have enough RAM and processing power to run a model comfortably. However, low-powered devices like a Raspberry Pi will likely struggle with most models.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Ollama Provider](https://docs.openclaw.ai/providers/ollama)
|
||||
@@ -1,8 +0,0 @@
|
||||
# openclaw onboard
|
||||
|
||||
`openclaw onboard` walks you through the initial setup process interactively, helping you connect your model provider and first channel step by step.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Onboarding: CLI](https://docs.openclaw.ai/start/wizard)
|
||||
- [@official@onboard](https://docs.openclaw.ai/cli/onboard)
|
||||
@@ -1,8 +0,0 @@
|
||||
# Onboarding
|
||||
|
||||
Onboarding is the guided first-run process that walks you through connecting your first AI model provider and communication channel so your agent is ready to receive and respond to messages. You can run it with `openclaw onboard`.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Onboarding Overview](https://docs.openclaw.ai/start/onboarding-overview)
|
||||
- [@official@Onboarding CLI](https://docs.openclaw.ai/start/wizard)
|
||||
@@ -1,8 +0,0 @@
|
||||
# Onboarding
|
||||
|
||||
Onboarding is the guided first-run process that walks you through connecting your first AI model provider and communication channel so your agent is ready to receive and respond to messages. You can run it with `openclaw onboard`.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Onboarding Overview](https://docs.openclaw.ai/start/onboarding-overview)
|
||||
- [@official@Onboarding CLI](https://docs.openclaw.ai/start/wizard)
|
||||
@@ -1,8 +0,0 @@
|
||||
# Open Claw vs Claude Code
|
||||
|
||||
Claude Code is Anthropic's official CLI tool for AI-assisted coding, tightly integrated with Claude models and designed for developer workflows. Open Claw is a community-built alternative that runs independently, supports a wide range of AI providers beyond Anthropic, and extends beyond coding to general agent automation across messaging platforms.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Open Claw vs Claude Code](https://docs.openclaw.ai/help/faq#what-are-the-advantages-vs-claude-code-for-web-development)
|
||||
- [@video@OpenClaw vs Claude explained simply in 8 minutes](https://www.youtube.com/watch?v=b773XfpS7fw)
|
||||
@@ -1,7 +0,0 @@
|
||||
# OpenAI
|
||||
|
||||
OpenAI provides access to models like GPT-4o. Open Claw can use these models as the AI brain behind your agent by configuring your OpenAI API key in the model provider settings.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@OpenAI Provider](https://docs.openclaw.ai/providers/openai)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Other Workspace Files
|
||||
|
||||
Open Claw recognizes several other special markdown files that are automatically injected into the agent's context at startup. [BOOT.md](http://BOOT.md) contains instructions that the agent runs once when the Gateway starts. [TOOLS.md](http://TOOLS.md) describes the tools available to the agent and how they should be used. [IDENTITY.md](http://IDENTITY.md) is an alternative or complement to [SOUL.md](http://SOUL.md) for defining the agent's persona. [BOOTSTRAP.md](http://BOOTSTRAP.md) is a general-purpose file for injecting additional context into every session. On top of these recognized filenames, you can also add any other markdown files to your workspace, such as project notes, reference documents, or custom instructions for specific tasks.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Agent Workspace](https://docs.openclaw.ai/concepts/agent-workspace)
|
||||
@@ -1,7 +0,0 @@
|
||||
# VPS & Cloud Providers
|
||||
|
||||
Open Claw runs on any VPS or cloud server that supports Node.js, so you are not locked into a specific provider. The official docs include setup guides for several popular options, including DigitalOcean, Render, Hetzner, Fly.io, Google Cloud Platform, Azure, and exe.dev, each with different trade-offs around pricing, location, and ease of setup
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Hosting and Deployment](https://docs.openclaw.ai/install#hosting-and-deployment)
|
||||
@@ -1,8 +0,0 @@
|
||||
# /plugins
|
||||
|
||||
`/plugins` lets you inspect discovered plugins and toggle their enablement from chat. It is disabled by default and requires `commands.plugins: true` to enable. It supports `list`, `show`, `install`, `enable`, and `disable` subcommands. Write operations are owner-only. Alias: `/plugin`.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Slash Commands](https://docs.openclaw.ai/tools/slash-commands)
|
||||
- [@official@Install and Configure](https://docs.openclaw.ai/tools/plugin)
|
||||
@@ -1,9 +0,0 @@
|
||||
# Plugins
|
||||
|
||||
Plugins are packages that can register any combination of capabilities: channels, model providers, tools, skills, speech, image generation, and more. Some are bundled with Open Claw, and others are published by the community on npm.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Tools and Plugins](https://docs.openclaw.ai/tools)
|
||||
- [@official@https://docs.openclaw.ai/tools/plugin](https://docs.openclaw.ai/tools/plugin)
|
||||
- [@official@https://docs.openclaw.ai/plugins/community](https://docs.openclaw.ai/plugins/community)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Proactive Core
|
||||
|
||||
The proactive core is what allows Open Claw agents to act on their own initiative rather than just responding to messages. Using heartbeats, cron jobs, and standing orders, the agent can run tasks on a schedule or trigger automatically based on conditions you define.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Automation & Tasks](https://docs.openclaw.ai/automation)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Railway
|
||||
|
||||
Railway is a modern cloud deployment platform that simplifies hosting by handling much of the infrastructure configuration for you. It is a good option if you want a fast, low-friction cloud deployment.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Railway Hosting](https://docs.openclaw.ai/install/railway)
|
||||
@@ -1,7 +0,0 @@
|
||||
# Raspberry Pi
|
||||
|
||||
A Raspberry Pi is a small, low-cost single-board computer that can run Open Claw 24/7 with minimal power consumption. It is a popular self-hosting choice for hobbyists who want a home server.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Raspberry Pi Hosting](https://docs.openclaw.ai/install/raspberry-pi#raspberry-pi)
|
||||
@@ -1,8 +0,0 @@
|
||||
# /reasoning
|
||||
|
||||
`/reasoning` is a directive that enables or disables extended reasoning mode. It takes `on`, `off`, or `stream` as arguments. When set to `on`, the agent sends a separate message prefixed with `Reasoning:` before its final reply. `stream` enables Telegram draft streaming only. Alias: `/reason`.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Slash Commands](https://docs.openclaw.ai/tools/slash-commands)
|
||||
- [@official@Reasoning visibility (/reasoning)](https://docs.openclaw.ai/tools/thinking#reasoning-visibility-%2Freasoning)
|
||||
@@ -1,7 +0,0 @@
|
||||
# /reset
|
||||
|
||||
`/reset` resets the agent's current state, clearing any ongoing task or context and returning it to its idle state. Like `/new`, it triggers the session-memory hook before resetting.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Slash Commands](https://docs.openclaw.ai/tools/slash-commands)
|
||||
@@ -1,3 +0,0 @@
|
||||
# Risks
|
||||
|
||||
Running Open Claw on a VPS exposes your Gateway to the public internet, which makes it a potential target if not properly secured. A misconfigured auth token, an exposed port, or a weak allowlist can give unauthorized users access to an agent that has tool access to your files, commands, and API keys. Since you are storing API credentials on a remote machine you do not physically control, a compromised server means those keys need to be rotated immediately.
|
||||
@@ -1,7 +0,0 @@
|
||||
# Risks
|
||||
|
||||
Running Open Claw locally or on shared hardware introduces certain risks like accidental exposure of API keys, lack of encryption, or the agent having access to sensitive local files. Understanding these helps you make informed decisions about your setup.
|
||||
|
||||
Visit the following resources to learn more:
|
||||
|
||||
- [@official@Security](https://docs.openclaw.ai/gateway/security)
|
||||
@@ -1,3 +0,0 @@
|
||||
# Risks
|
||||
|
||||
Dedicated hardware sitting in your home or office is physically accessible, which means anyone with access to the device could potentially tamper with it or extract credentials stored on it. If the device is connected to your home network without proper isolation, a compromised agent could have access to other devices on the same network. Power outages, hardware failures, and accidental resets can also cause data loss if your workspace and memory files are not backed up regularly.
|
||||
-3
@@ -1,3 +0,0 @@
|
||||
# Rotate All Credentials Immediately if a Breach is Suspected
|
||||
|
||||
If you think your setup has been compromised, changing all API keys, tokens, and passwords immediately limits how long an attacker can maintain access.
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user