DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run the pinned OpenCode engine on a project with Pixelcrabs

Install the locked OpenCode dependencies with Bun and start its dev command against a chosen project folder.

Credentials. Model providers are configured with your own API keys, so keep those keys out of the repository and out of any commit made while working in the project.

Who it is forA developer who wants the coding agent engine that PixelCrabs is built on, pointed at their own project directory.

The problemGetting the agent engine running from source requires the correct Bun version and a locked dependency install.

The outcomeThe OpenCode engine starts against the target project directory, with dependencies installed from the preserved lockfile.

What you need first

  • A computer with Node.js 24 or later installed
  • Bun 1.3.14 installed, for the pinned OpenCode engine
  • A local copy of the johnzhaors-bit/pixelcrabs repository
  • A static site folder containing index.html, or a project directory to point OpenCode at

Steps

  1. Install Bun 1.3.14.
  2. Run cd upstream/opencode from the repository root.
  3. Run bun install --frozen-lockfile
  4. Run bun dev --help to see the available options.
  5. Run bun dev /absolute/path/to/your/project

Prompt for your agent

In the pixelcrabs repository, change into upstream/opencode, run `bun install --frozen-lockfile`, then run `bun dev <absolute-path-to-project>`. Expected output: the OpenCode dev process starts against that project. Verify with `bun dev --help` that the command runs before pointing it at a project.

Caveat. The README notes that some tests download packages and need a native compiler toolchain, and that online model providers receive the context needed for their requests.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page