Add one reviewed manifest to tell PicoRunner exactly how to prepare, run, check, and update your app. Repositories without a manifest still use automatic discovery.
01
Add picorunner.toml
The root manifest is authoritative when present. Commands are argument arrays, paths stay inside the repository, services bind to loopback, and secret values never belong in the file.
schema = 1
name = "Example App"
[runtime]
kind = "node"
version = "22"
package_manager = "pnpm"
workspace = "."
[[setup.steps]]
kind = "dependencies"
locked = true
[launch]
command = ["pnpm", "run", "start"]
host = "127.0.0.1"
host_env = "HOST"
port = 3000
port_env = "PORT"
[health]
type = "http"
path = "/"
timeout_seconds = 90
[persistence]
paths = ["data", "uploads"]
[[inputs]]
name = "OPENAI_API_KEY"
kind = "secret"
required = false
description = "Required only for AI features."
This prompt makes the agent inspect the real project instead of guessing a generic launch command.
Add PicoRunner support to this repository.
Inspect the existing documentation, lockfiles, package manifests, workspaces, runtime requirements, startup scripts, environment examples, health endpoints, and persistent data directories. Create a root-level picorunner.toml using schema version 1.
Use only commands already supported or documented by this repository. Express every command as an argument array and do not use shell pipelines. Bind network services to 127.0.0.1, declare how PicoRunner supplies the port, list required configuration and secrets without including their values, and list every relative data path that must survive an update. Add a readiness check that proves the app is usable. Do not write outside the repository or invent setup steps. Perform a clean installation, launch the app, verify readiness, and report anything PicoRunner cannot provide.
03
Validate the complete setup
Check TOML syntax with taplo check picorunner.toml.
Open PicoRunner and import the repository or local folder. PicoRunner performs semantic validation and fails closed if the manifest is unsafe or incomplete.
Approve the displayed setup, then confirm the declared health check succeeds.
Test an update and confirm every declared persistence path survives.
A valid file is not a PicoRunner endorsement. Catalog verification remains a separate review.
04
Add the README button
Enter the canonical public GitHub repository. The generated HTTPS link opens a review in PicoRunner and provides a download fallback; it never installs silently.
What the manifest controls
Runtime Node or Python version, package manager, and workspace.
Setup Locked dependencies and explicit no-shell build steps.
Launch Command, local host, port, and non-secret environment values.
Readiness TCP or HTTP health check and timeout.
Updates Relative data paths PicoRunner must preserve.
Inputs Names and descriptions of configuration or secrets, never their values.
