GitHub meets App Store for agent-operable software

Apps your agent can install, use, fork, and improve.

Forkbase is a marketplace of working iOS apps designed for personal AI agents. You open the Forkbase app, connect Hermes, OpenClaw, or another agent, and let it build apps on your Mac, install them into the container, operate them through UI control or app tools, and remix the source when the app almost fits.

See the demo loop What ships first

source-backed Mac-built container-run agent-operated

forkbase://install/workout-os

Marketplace

Workout OS

verified build

$ forkbase build

clone repo xcodebuild archive package ipa

Forkbase App

Agent Linked

Agent choice

UI tap, type, scroll

Tools create_workout()

The bet: Forkbase is the app the user opens. Inside it, they connect any agent they trust. That agent should start from real working software, install it, use it like a human, call tools when available, and fork the source when it needs to change.

Pitch Packet

Four doors into the idea.

Send the homepage if someone needs the quick hit. Send a subpage if they care about a specific piece of the machine.

MVP demo

The exact first loop: agent finds, builds, installs, opens, fills, and customizes a workout app.

Agent control

How UI control, accessibility, app tools, and source edits fit together inside the container.

Trust receipts

Why the early marketplace should prove apps with build evidence instead of star ratings.

Long-term vision

The creator economy: paid source, paid installs, remix royalties, bounties, and fork lineage.

The Shareable Demo

“Install a workout tracker and create my first push day.”

This is the first magic loop. No payments. No ratings. No giant ecosystem. Just an agent turning a marketplace app into a filled-out app on the phone.

01User opens the Forkbase app.
02User connects Hermes, OpenClaw, or another agent.
03User asks for a workout tracker and first push day.
04Agent browses the Forkbase registry.
05Agent chooses an app, explains permissions, and builds it on the Mac.
06IPA imports into Forkbase Container.
07Agent launches the app inside Forkbase.
08Agent uses UI control to complete onboarding.
09If tools exist, the agent switches to tools.
10User sees the workout app actually filled out.

9:41 Agent active

Workout OS

Push Day A

Bench press 4 x 6

Incline DB 3 x 10

Triceps rope 3 x 12

Used UI for onboarding. Used create_workout() for the routine.

The Important Part

The agent is not trapped behind APIs.

Tools are great when they exist. But if an app has no perfect tool, the agent can still move through it step by step like the user would.

Visual control

The agent sees the current app screen and reasons from pixels.

Accessibility control

The agent reads labels, fields, buttons, and coordinates.

Tool control

The agent calls explicit actions like log_set or export_data.

Source control

The agent edits the repo, shows the diff, and prepares a fork.

Product rule

The agent chooses the best control path for the job.

UI when it needs to behave like a user. Tools when the app gives clean handles. Source edits when the app needs to become yours.

MVP Architecture

Small enough to build. Weird enough to matter.

Forkbase Registry

A web catalog of repos, manifests, screenshots, build status, permissions, and agent affordances.

App Manifest

Each app ships a machine-readable recipe for building, installing, testing, and operating it.

Mac Builder

The user's Mac clones the repo, runs Xcode, packages the app, and hands it to the container.

Forkbase App

The iOS app users open to browse the market, connect their agent, and run installed apps.

Agent Driver

A bridge between the connected agent and Forkbase for screenshot, UI tree, tap, type, scroll, launch, and tool calls.

Remix Loop

The agent can make one small source change, show the diff, and prepare a publishable fork.

App Contract

Every app gets a small manifest the agent can understand.

The manifest is the bridge between GitHub-style source and App Store-style installation. It tells the agent how to build the app, what it can touch, and which shortcuts are safe to call.

{
  "name": "Workout OS",
  "platform": "ios",
  "build": {
    "scheme": "WorkoutOS",
    "project": "WorkoutOS.xcodeproj"
  },
  "agent": {
    "uiControl": true,
            "tools": ["create_workout", "log_set"]
  },
  "agentHosts": ["Hermes", "OpenClaw", "custom"],
  "permissions": ["local_storage"]
}

Trust Without Ratings

Skip stars. Show receipts.

Ratings are easy to game. The first marketplace should prove apps with verifiable evidence, not vibes.

Builds on current Xcode Last verified today Permissions: local storage only UI tree readable Tools: 7 exposed Smoke test passed Source linked to GitHub Fork lineage visible

What We Do Not Build Yet

The restraint is part of the strategy.

No payments in MVP No ratings No royalty enforcement No blank-slate app generator pitch No giant social graph

Long term

Where This Goes

A forkable software economy, not just an app launcher.

The MVP proves the Forkbase app can connect to a user's preferred agent, install apps, operate them, and remix them. The longer arc is bigger: users can pay for source ownership, creators can earn when their apps are reused, remixes can carry upstream credit, and agents can request or build the exact variants people need.

Read the long-term vision

The Line

Forkbase is an app store for agents, where every app is usable by humans and operable by AI.

See the full vision Product thesis Rendered brief