How to Build an OpenClaw Cyberdeck with Raspberry Pi for Portable AI Agent Work

A cyberdeck is a portable computer built around a single-board computer, a compact display, a keyboard, and a battery. The name comes from William Gibson's science fiction, but the hardware is practical: security professionals carry them into server rooms, field researchers use them for data collection, and makers build them because a pocket-sized Linux box with a real keyboard is more useful than a phone for technical work.

The Raspberry Pi is the most common cyberdeck brain. The Pi 5's quad-core Cortex-A76 processor runs at 2.4 GHz with up to 8GB of LPDDR4X RAM, enough for a full Linux desktop, development tools, and the OpenClaw agent runtime. At $60 to $80 for the board alone, it is the cheapest path to a portable computer that runs real software.

"Raspberry pi cyberdeck" pulls roughly 1,300 monthly searches, and the community behind these builds is active on Reddit, Discord, and Hackaday. Most existing guides focus on the hardware: 3D-printed cases, display wiring, keyboard selection. What they skip is the software layer that turns a portable computer into a portable agent. That is where OpenClaw fits.

OpenClaw is an open-source AI agent framework that runs on a Raspberry Pi and connects to cloud LLMs (Claude, GPT-4, Gemini) for reasoning while executing tasks locally. It separates the Gateway process (always-on, manages sessions and tool access) from the model layer (cloud API calls for inference). The Pi handles orchestration. The cloud handles thinking. The combination gives you a battery-powered AI agent you can carry in a backpack.

Adding OpenClaw to a cyberdeck changes what the hardware can do. Instead of just a portable terminal, you get a device that can run automated workflows, chain command-line tools together, respond to messages on Telegram or Slack, and generate structured reports from field data. The hardware build is the foundation. The agent layer is what makes it useful.

Your hardware choice depends on budget, portability requirements, and how much you want to build yourself. There are three practical paths.

Path 1: DIY from components ($100 to $200)

Buy a Pi 5 (8GB, around $80), a 4-inch or 5-inch touchscreen ($25 to $50), a compact Bluetooth keyboard ($15 to $30), and a USB power bank. Print or buy an enclosure. This is the cheapest route and gives you full control over the layout, but expect 10 to 20 hours of assembly time and some frustration with wiring.

The Bumble Berry Pi is a good starting template for a budget handheld build. It uses a Pi 4, a small display, and a 3D-printed case, with the design files published on GitHub. Adapting it for a Pi 5 is straightforward since the board dimensions are similar.

Path 2: HackberryPi CM5 ($449 to $1,049)

The HackberryPi CM5 is a pre-designed cyberdeck using the Raspberry Pi Compute Module 5. It packs a 4-inch 720x720 touchscreen, a BlackBerry Q20 keyboard with trackpad, dual USB 3.0 ports, full-sized HDMI, an NVMe M.2 slot, and a 5,000 mAh battery into an aluminum shell that measures 143.5 x 91.8 x 17.6mm and weighs 306 grams.

The base configuration with 2GB RAM and a 32GB microSD starts at $449 from Carbon Computers. The 8GB CM5 with an NVMe SSD is the right pick for OpenClaw work, which pushes the price toward $600 to $700 depending on storage. Battery life runs 3 to 4 hours under active use, enough for a field session.

The NVMe slot is the standout feature for agent work. OpenClaw's data directory and any local caching benefits enormously from SSD speeds versus microSD. The BlackBerry keyboard is surprisingly usable for terminal commands once you adjust to the layout.

Path 3: Pi Slate ($282 to $707)

The Pi Slate from Carbon Computers is a larger format cyberdeck with a 5-inch 1920x720 touchscreen, a backlit RGB keyboard, and a 10,000 mAh battery that delivers 3 to 5 hours of runtime. It takes a full Raspberry Pi 5 (not a Compute Module), supports HAT expansion for LoRa radios, SDR modules, and AI accelerators, and ships with 1 to 2 week lead times.

The barebones kit at $282 requires you to supply your own Pi 5 and cooling. Fully assembled units with 8GB RAM run around $500. The larger display and keyboard make it more comfortable for extended sessions, but it is less pocketable than the HackberryPi.

Which board for OpenClaw?

The Pi 5 with 8GB RAM is the recommended baseline. OpenClaw's Node.js runtime, the system daemon, and a comfortable headroom buffer fit within 4GB, but 8GB leaves room for running additional tools alongside the agent. The Pi 4 with 4GB works but is 2 to 3x slower for OpenClaw workloads because of the older Cortex-A72 cores and slower memory bus.

With hardware assembled, the software setup follows the standard OpenClaw Raspberry Pi installation path. Flash Raspberry Pi OS Lite (64-bit) to your SD card or NVMe drive using Raspberry Pi Imager. The Lite image skips the desktop environment, which saves RAM and CPU for agent work. If you need a GUI occasionally, install one later with sudo apt install raspberrypi-ui-mods.

OpenClaw requires 64-bit Raspberry Pi OS. The 32-bit image is not supported.

The official OpenClaw documentation at docs.openclaw.ai covers the full installation procedure. The core steps are: install Node.js, run the OpenClaw installer, complete the onboarding wizard, and configure your LLM provider. The onboarding step installs the OpenClaw Gateway as a systemd service that starts automatically on boot, which is exactly what you want for a cyberdeck that should be ready to work as soon as you power it on.

Storage matters more than you think. An NVMe SSD versus a microSD card makes a dramatic difference in OpenClaw's responsiveness. The Gateway daemon reads and writes to ~/.openclaw/ constantly, and microSD latency adds noticeable lag to every interaction. If your cyberdeck has an NVMe slot (both the HackberryPi CM5 and Pi Slate support this), use it. If you are on a DIY build with only a microSD slot, use the fast card you can find (A2 rated, UHS-I minimum).

Reduce GPU memory for headless operation. If you are running without a display connected most of the time, reducing GPU memory allocation frees RAM for the agent. Add gpu_mem=16 to /boot/config.txt to reclaim the default 76MB. This does not affect the touchscreen on most cyberdeck builds since the framebuffer driver uses system RAM, not GPU memory.

LLM provider configuration. OpenClaw on a Pi delegates inference to cloud APIs. Running local models on Pi hardware is technically possible but impractical: even a 3-billion parameter model takes 10 to 30 seconds per response on a Pi 5. Configure an API key for Claude, GPT-4, or Gemini and budget $20 to $100 per month for API costs depending on usage volume. The Pi's job is orchestration, not inference.

After installation, verify with openclaw status and confirm the Gateway service is running with systemctl --user status openclaw-gateway.service. If both report healthy, your cyberdeck has an always-on AI agent.

Sync your cyberdeck field data to a workspace your team can access

generous storage, no credit card, MCP-ready endpoint for your OpenClaw agent's uploads and file sync. Build in the field, hand off from anywhere.

Start 14-Day Trial

A cyberdeck with OpenClaw installed is a portable automation platform. The specific workflows depend on your field, but several patterns work well on battery-powered hardware with intermittent connectivity.

Network diagnostics and site surveys. Carry the cyberdeck into a client's office or server room. The OpenClaw agent can run network scans, enumerate services, check DNS configurations, and compile the results into a structured report while you focus on the physical inspection. The Pi 5's Ethernet port provides a wired connection for reliable scanning, and a USB Wi-Fi adapter adds wireless survey capability.

IoT sensor monitoring. Connect sensors via the Pi's GPIO pins or I2C bus (the HackberryPi CM5's Stemma QT port makes this tool-free). The agent reads sensor data, applies thresholds, and logs anomalies. Environmental monitoring, equipment temperature checks, and air quality surveys all work well in this pattern. The cyberdeck format means you carry the display, keyboard, and compute in one unit instead of juggling a laptop, cables, and breadboards.

Offline-first data collection with sync. In locations without reliable internet, the agent queues tasks locally and processes them with cached context. When connectivity returns, it syncs results. This pattern works for field inspections, remote site audits, and any scenario where you need to collect structured data away from a desk.

Development and debugging on the move. OpenClaw can read and edit code, run tests, and interact with APIs. A cyberdeck with a real keyboard (even a tiny BlackBerry one) is more productive for quick fixes than a phone or tablet. SSH into remote servers, review pull requests, or prototype scripts while commuting or traveling.

Automated documentation. Point the agent at a task ("survey the network topology of this office," "catalog the serial numbers of equipment in this rack") and it generates structured notes as you work. The combination of a compact form factor and an AI assistant that writes while you observe is genuinely more efficient than typing everything manually.

The common thread across all of these is that the cyberdeck handles the tedious parts (scanning, formatting, logging, reporting) while you handle the parts that require physical presence and judgment. The agent runs in the background on the same device you are already carrying.

A cyberdeck produces data in the field. Reports, scan results, sensor logs, collected files. That data is only useful if it reaches your team, your client, or your future self at a desk. The sync layer is what turns a portable gadget into a professional tool.

Local storage on the Pi is fine for the session, but a cyberdeck's SD card or small SSD is not where you want your only copy of field data. You need a workspace that other people can access, that versions files, and that survives if you drop the cyberdeck in a puddle.

Local options first. You can rsync to a home server, push to a Git repository, or upload to S3. These work and cost nothing beyond what you already pay for infrastructure. The tradeoff is setup: you need to configure credentials, handle authentication, and build the sync script yourself. For a personal project, this is fine.

Cloud storage services. Google Drive, Dropbox, and OneDrive all have CLI tools or FUSE mounts that work on Raspberry Pi OS. They handle sync automatically once configured. The limitation is that they are file storage, not workspaces. Your team gets the files but no context about what the agent did, when, or why.

Fastio for agent-to-human handoff. Fastio is built for the pattern where an agent produces work and a human reviews it. Upload field reports and collected data to a shared workspace through the Fastio MCP server or the REST API. Files are versioned automatically, and enabling Intelligence Mode indexes everything for semantic search and RAG queries, so your team can ask questions about the field data without reading every file.

The Business Trial includes 50GB of storage, included credits, and 5 workspaces with no credit card required. That is enough for most cyberdeck workflows. OpenClaw can authenticate to Fastio and upload results as part of the workflow, so the sync happens automatically at the end of each task rather than requiring a manual step.

The ownership transfer feature lets an agent build and populate a workspace, then hand ownership to a human. For consulting work, this means you can set up a client's workspace from the field, populate it with findings, and transfer it before you leave the site. The client gets a ready-to-use workspace. You keep admin access for follow-up.

For teams that need audit trails, Fastio logs every file operation with timestamps and actor identity. When an agent uploads a scan report at 2:47 PM from a cyberdeck in a server room, that action is recorded. Useful for compliance-sensitive engagements where you need to prove when data was collected and by whom.

Battery life is the hard constraint on portable computing. A Pi 5 draws 3 to 5 watts under typical load and can spike to 12 watts under sustained CPU stress. On a 5,000 mAh battery (like the HackberryPi CM5's), that translates to 3 to 4 hours of active use. On the Pi Slate's 10,000 mAh pack, expect 3 to 5 hours. Neither is enough for a full workday without management.

Reduce idle power draw. Disable Bluetooth if you are not using a wireless keyboard: sudo systemctl disable bluetooth. Disable Avahi/mDNS if you do not need zero-conf networking: sudo systemctl disable avahi-daemon. Each disabled service saves a few milliwatts, which adds up over hours.

Throttle CPU when idle. The Pi 5's default governor ramps to full speed aggressively. Switching to the powersave governor (echo powersave | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor) reduces clock speed when the agent is waiting for API responses, which is most of the time. Switch back to ondemand when you need sustained throughput for scanning or data processing.

Use an external battery pack. MagSafe-compatible power banks snap onto the HackberryPi CM5's rear magnets. A 20,000 mAh external pack effectively triples your runtime. USB-C power delivery means you can charge while operating, so a wall outlet extends your session indefinitely.

Schedule heavy tasks for when you have power. If you know a scan or data processing job will take 30 minutes of sustained CPU, start it when you are plugged in or have a full battery. Queue lightweight tasks (queries, report formatting, file uploads) for battery operation. OpenClaw's task queue does not differentiate by power state, but you can organize your workflow around this constraint.

Monitor battery voltage. The HackberryPi CM5 exposes battery voltage over I2C, which the agent can read programmatically. A simple threshold check before starting a long-running task prevents the cyberdeck from dying mid-operation. If voltage drops below a safe threshold, the agent can pause, sync its current state to a remote workspace, and shut down gracefully.

Realistically, a cyberdeck is not a laptop replacement for all-day desk work. It is a purpose-built field tool for sessions measured in hours, not days. Plan your field work around that constraint, keep a power bank in your bag, and sync data to a remote workspace frequently so nothing is lost if the battery dies unexpectedly.