Install Craft Anything on Steam Deck

Install path

1. 01

   1 · Switch to Desktop Mode

   Download and launch from the desktop session. Gaming Mode is not a documented target for this app.

2. 02

   2 · Use the Linux x86_64 AppImage

   Do not pick aarch64, Windows, or the macOS disk image. The Deck’s CPU is x86_64.

3. 03

   3 · Make it executable and start it

   chmod +x the AppImage, then run it. The Linux page covers deb, rpm, and Flatpak if you would rather not use an AppImage.

4. 04

   4 · Then the same setup as any Linux PC

   Doctor, a coding agent, and Clean room are unchanged. A Deck does not get a different project folder or a different engine.

What this page will not claim

There is no EmuDeck installer, no controller profile, and no “add to Steam” script published for Craft Anything that this guide can honestly repeat. If you add the AppImage to Steam yourself, you are outside the project’s install notes. Desktop Mode is the path that matches the Linux build.

This site is not official. We do not host installers. Downloads go to GitHub Releases for storytold/craft-anything. Examine only software you own or are allowed to examine.

Desktop Mode download steps

Switch to Desktop Mode from the Steam menu. Open a browser on the Deck, go to the GitHub release this site links, and save the linux-x86_64 AppImage into a folder you own, such as Home or Downloads. Mark it executable, then start it from the file manager or a terminal. Craft Anything needs a pointer, keyboard, or on-screen keyboard for the first session; a controller-only Gaming Mode session is not documented. Storage on the Deck is limited: keep one AppImage and delete older tags once the new file launches. Checksums still live in SHA256SUMS.txt on the same release.

Same engine as a Linux desktop

Doctor, Claude Code, Clean room, and the Documents project folder work the same as on any x86_64 Linux PC. A Deck does not get a lighter study engine or a different installer brand. If you already installed Craft Anything on a laptop, you still need a separate AppImage on the Deck; settings do not roam unless you copy them yourself. You need a network to fetch the release. Building with a cloud coding agent usually needs a network too. Inspection of a local target can still run after the app is on disk, but Build will wait for the agent.

When the AppImage will not start on Deck

Confirm the filename contains linux-x86_64, not aarch64, windows, or macos. Confirm chmod +x succeeded. If the file sits on an SD card mounted noexec, copy it to home. If the window is tiny or off-screen, that is a desktop session issue, not a missing “Deck edition.” Read the Linux page for Flatpak and tarball options if you refuse AppImage. For agent PATH problems, update to the current tag before reinstalling the agent. Bugs in the app go to GitHub, not to this mailbox. SteamOS updates can remount cards; if an AppImage that ran last month now says permission denied, chmod +x again before you redownload. A keyboard or the Steam on-screen keyboard is enough to run doctor and the first prompt. Do not expect a Game Mode shortcut, an EmuDeck recipe, or a verified Steam store page. Those are not published for this app. Leave disk space for Study captures and a generated project. Then follow Setup as you would on a Linux laptop: doctor, a coding agent, Clean room, and the Documents folder.

FAQ

Why is the Craft Anything download the Linux file?

SteamOS on Deck runs x86_64 Linux software. The AppImage is that build.

Will Craft Anything show up in Gaming Mode by itself?

No. Launch it from Desktop Mode.

Is there a Windows MSI for Steam Deck?

No. Use the Linux AppImage. Proton is not an install path this guide describes.

Do I need a coding agent on the Deck?

Only if you want Build. Inspection can run without an AI account. Setup has the details. Desktop Mode still needs a keyboard or on-screen keyboard for doctor and the first project prompt. Leave disk space for captures. Copy the AppImage off a noexec SD card into home if chmod does not stick after a SteamOS update. Then treat the rest of the session like any x86_64 Linux PC: same engine, same Clean room default, same Documents folder unless you change it.