48 articles connected to this topic.
Agent lifecycle management gets safer when one process owns restarts, state writes, and repair. Learn when OpenClaw external supervisor mode fits and how to hand over safely.
OpenClaw SQLite backup commands create verified global or per-agent database artifacts. Use this release-aware workflow to test recovery without overwriting a live agent.
AI agent SSRF protection keeps browser automation from reaching private services by default. Use a narrow hostname allowlist, explicit exceptions, and network egress controls.
OpenClaw extended-stable is a monthly package channel for backported security and reliability fixes. Use this guide to choose it, preview the change, and verify the Gateway after updating.
Local AI agent setup starts with a routing decision: fully local, hybrid, or node-local inference. Compare the OpenClaw paths before downloading a model.
OpenClaw plugins need a restart, runtime verification, and a clear source trail after an update. Use this safe workflow for official correction releases.
OpenClaw Control UI setup should keep the Gateway private: open the local dashboard, authenticate the browser, approve only the requested device scope, and use a protected route for remote access.
AI agent dead-letter queues give failed messages a visible recovery path: preserve the event, capture why it failed, review it safely, and replay only after the cause is fixed.
AI agent onboarding turns a promising assistant into accountable work: define its job, grant narrow access, test real tasks, and make escalation visible before you rely on it.
AI agent scheduling needs more than a fixed cron expression when work arrives unevenly. Use dynamic cadence, durable job state, and explicit delivery rules to control cost and timing.
OpenClaw local models can run short tasks on a paired node's Ollama runtime. Learn when node-local inference fits, what it isolates, and how to test it safely.
OpenClaw Wear OS companion support brings agent, session, model, and realtime Talk controls to a phone-proxied watch surface. Learn the practical boundary between fast control and full agent work.
OpenClaw iOS app users can read cached chats offline and queue text for the right Gateway, then reconnect without losing the session context or sending a message twice.
AI agent data recovery protects durable sessions, schedules, and configuration when a database or publish step fails. Use a quarantine, recoverable snapshots, and a controlled restore path.
OpenClaw Android is a companion app, not a phone-hosted Gateway. Learn the safe pairing sequence, what the app can control, and how to keep mobile access private.
OpenClaw mobile app pairing connects an iOS or Android companion to your Gateway with a short-lived setup code, explicit scopes, and a private network path.
OpenClaw skills can live in a workspace, a personal agent directory, or a shared managed directory. Learn how precedence and allowlists shape the right scope.
AI agent crash loops turn a transient failure into lost work and runaway restarts. Learn how bounded restart policies, repair states, and observability keep self-hosted agents recoverable.
OpenClaw Control UI turns an agent gateway into a browser workspace for sessions, live tasks, usage, approvals, and safe device pairing without juggling terminal windows.
OpenClaw onboarding verifies that a model can complete a real turn before it saves credentials or configures your workspace, Gateway, channels, and agents.
AI agent crash recovery keeps a bad restart from becoming a wider outage. See how OpenClaw's Gateway safe mode separates diagnosis from automatic recovery.
What an AI gateway actually does, how it differs from a normal API gateway, and why a local gateway matters when you run self-hosted AI agents on macOS.
OpenClaw Attach in v2026.7.1-beta.1 lets you launch Claude Code against an existing Gateway session with a scoped temporary MCP grant, making interrupted coding workflows easier to resume.
AI agent reliability often breaks at the provider-response boundary: an error payload, an oversized body, or an out-of-credits message. How the runtime reads that response decides whether the agent recovers or hangs.
AI agent update safety means treating version checks, release tags and dependency patches as control-plane decisions, not background maintenance noise.
Anthropic extended thinking can fail after cache expiry or Gateway restarts. OpenClaw's beta fix shows how agents should recover without deleting session history.
Interrupted tool calls expose whether an AI agent can preserve state, resume safely and report failure clearly instead of leaving a user-facing run half-finished.
AI agent timeouts prevent stuck provider, plugin and tool calls from freezing a run; OpenClaw 2026.6.1 turns more wait states into bounded recovery.
Windows AI agent hosting is moving from browser tabs to native nodes. Here is what OpenClaw 2026.6.1 changes for self-hosted Windows automation.
AI agent tool call errors usually come from malformed arguments, not bad reasoning. Here is how OpenClaw v2026.5.28 repairs smart-quoted edit arrays and quarantines unsupported tool schemas instead of failing the turn.
AI agent rate limits break scheduled jobs when a 429 lands mid-run. Here's how retry budgets, exponential backoff with jitter, and preflight model fallback keep cron automations finishing instead of silently skipping.
Codex app-server reliability is the quiet half of OpenClaw 2026.5.27. Here is how shared clients survive startup failures, hook relays live through restarts, and workspace memory routes through tools.
AI agent auth profiles separate model credentials by provider, runtime, and operator so self-hosted agents can migrate logins, recover cleanly, and reduce credential blast radius.
A meeting notes agent is only useful when its summaries trace back to clean transcripts, source chunks and replayable context. OpenClaw 2026.5.26 moves that path into the core runtime.
OpenClaw gateway performance improved in 2026.5.22 through cached model metadata, leaner startup paths, locked npm packages, and sharper operator diagnostics.
On-device Android AI agent architectures like X-OmniClaw move perception, memory, and app control onto the phone. Here is what that means for self-hosted assistants.
xAI device code OAuth lets headless AI agents authorize from SSH, containers, and remote hosts without a localhost browser callback or pasted API key.
OpenClaw plugin SDK lets teams ship typed tool plugins without loading runtime code for discovery; this guide explains the build flow and where it fits beside MCP.
Agent provider plugins keep self-hosted AI agents lighter by moving heavy channel and model dependencies out of the core install until operators need them.
AI agent tool policies should vary by sender, channel, and action risk. OpenClaw 2026.5.12 adds sender-scoped controls for safer self-hosted agents.
Provider plugins in OpenClaw 2026.5.12 move heavy Slack, Bedrock, Anthropic Vertex, and sandbox dependency cones out of core installs so operators only pull what they use.
An LLM idle watchdog catches silent model streams before they hang an agent turn. The 2026.5.12 fix escalates through profile rotation and configured model fallback instead of leaving the turn stuck.
Agent runtime fallbacks let an ACP turn try a backup model or runtime when the primary is unavailable, so a single dead backend stops killing user-facing replies.
Telegram bot reliability improves when polling, queueing and reply delivery are isolated from the main agent loop instead of sharing one fragile event path.
How to run a self-hosted Discord voice agent on OpenClaw v2026.5.7: permission audit via channels capabilities, the new 2.5s capture silence grace default, and STT tuning that stops the bot interrupting people.
How /steer and active-run steering work in OpenClaw v2026.5.3+: send guidance to a running session without queuing a new turn, with worked examples and the safer queue defaults from v2026.4.29.
Microsoft's Semantic Kernel RCE research shows why prompt injection in AI agents is no longer just a text problem. Here's how self-hosted agent builders should think about tool boundaries.
OpenAI now says prompt injection may never be fully solved for browser agents like ChatGPT Atlas. Here is what that means for chat-channel agents and self-hosted setups.