DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to build a local macOS package and smoke test it with Errand

Produce ad-hoc signed Errand builds in release/ and run the smoke check for testing.

Short answer: Run git clone https://github.com/runta-dev/errand.git and cd errand, then run npm ci; then run npm run package; run npm run smoke. All steps.

Who it is forA developer or tester who changed the desktop client and needs a local installable build to check before a release.

The problemTesting packaging only through a public release is slow, and the signed release path is not meant for local experiments.

The outcomeLocal macOS artifacts are written to release/ and the smoke script reports on the packaged build.

What you need first

  • A Mac running macOS 13 or later on Apple Silicon
  • Node.js 22 to 26 and npm 10 or later
  • A Runta account with model access configured for your agents
  • Git to clone the repository

Steps

  1. Run git clone https://github.com/runta-dev/errand.git and cd errand, then run npm ci
  2. Run npm run package
  3. Run npm run smoke
  4. Open the artifacts in the release/ folder and confirm the DMG and ZIP are present

Prompt for your agent

In the runta-dev/errand repository, run npm ci, then npm run package and npm run smoke. Expected output: artifacts in the release/ directory and a passing smoke run. Verify that the DMG contents and blockmap are present before reporting success.

Caveat. Local builds are ad-hoc signed for testing only, so the README says distribution must go through the signed release workflow.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for runta-dev/errand and "Build a local macOS package and smoke test it"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer