# PicoClaw runs on a $10 board. Change one setting before it touches Stripe.

DevFeed: [PicoClaw runs on a $10 board. Change one setting before it touches Stripe.](<https://devfeed.tech/articles/picoclaw-runs-on-a-10-board-change-one-setting-before-it-touches-stripe-96064.md>)

Original publisher: [Read original article](<https://www.swytchcode.com/content/picoclaw-runs-on-a-usd10-board-change-one-setting-before-it-touches-stripe>)

Author: Swytchcode Team

Published: 2026-10-22T04:35:40Z

Content type: tutorial

Language: en

Sources: [Swytchcode](<https://devfeed.tech/sources/swytchcode.md>)

Topics: [Single Board Computer](<https://devfeed.tech/topics/single-board-computer.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [developer setup](<https://devfeed.tech/topics/developer-setup.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-assistant](<https://devfeed.tech/tags/ai-assistant.md>), [android](<https://devfeed.tech/tags/android.md>), [api](<https://devfeed.tech/tags/api.md>), [board](<https://devfeed.tech/tags/board.md>), [chat](<https://devfeed.tech/tags/chat.md>), [command](<https://devfeed.tech/tags/command.md>), [command-line](<https://devfeed.tech/tags/command-line.md>), [config](<https://devfeed.tech/tags/config.md>), [container](<https://devfeed.tech/tags/container.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-image](<https://devfeed.tech/tags/docker-image.md>), [go](<https://devfeed.tech/tags/go.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [rules](<https://devfeed.tech/tags/rules.md>), [shell](<https://devfeed.tech/tags/shell.md>), [shell-tool](<https://devfeed.tech/tags/shell-tool.md>), [stripe](<https://devfeed.tech/tags/stripe.md>), [tool](<https://devfeed.tech/tags/tool.md>)

## AI overview

PicoClaw's file sandbox keeps its file tools within the workspace, but its shell `exec` tool can reach beyond it. In a native setup, disable `exec` in `~/.picoclaw/config.json` and keep `restrict_to_workspace` enabled; the excerpt reports that all 12 shell attempts were refused and seven checks still passed. Scheduled jobs that run commands through `exec` stop working, and chat users otherwise have `exec` access by default. In Docker, PicoClaw connected to Swytchcode on the host through an enabled HTTP MCP server; the excerpt says reads ran and writes waited for approval. This required a Swytchcode account, with Business or Enterprise for approvals. Testing used PicoClaw 0.3.1, a scripted model, mocked Stripe, and a small Linux image; no real board, model, chat channel, or phone approval was tested.

## Source excerpt

PicoClaw worked with Swytchcode on the first try in Docker. Running directly on a board, its shell tool could still reach Swytchcode's rules. One line in its config closes that.