Localized reading guide
deploy-open-harnessPurpose, usage and source
Guides a user through collecting the credentials needed to deploy their own copy of Open Harness, deploying this repo on Vercel, and completing first-run setup. Use for requests about deploying, self-hosting, configuring credentials, or getting started with a fork of this app.
Source retrieved:
- Source repository
- vercel-labs/open-agents
- SKILL.md
.agents/skills/deploy-open-harness/SKILL.md- Repository stars
- 5,871
- Repository updated
- 2026-08-29
- Categories
- Agent workflows
- Last collected
License: MIT
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
Guides a user through collecting the credentials needed to deploy their own copy of Open Harness, deploying this repo on Vercel, and completing first-run setup. Use for requests about deploying, self-hosting, configuring credentials, or getting started with a fork of this app.
How the upstream workflow works
Overview
You are helping a user deploy their own copy of Open Harness. Base your guidance on the current codebase, not on older Harness-era setup assumptions.
Upstream passage · L6 ↗Goals
Help the user: Decide whether they want a minimal deploy or the full GitHub-enabled coding-agent flow.
Upstream passage · L31 ↗openssl rand -base64 32 | tr '+/' '-_' | tr -d '=\n'Requirements and setup
First rule: verify current requirements from the repo
Before giving deployment advice, read these files if you have not already: If the code and the docs disagree, trust the code and say so.
Upstream passage · L10 ↗Limits and quality checks
Safety rules
Never ask the user to paste secrets into chat. Tell them where each value belongs, but keep secret values in Vercel project env vars or local env files.
Upstream passage · L42 ↗Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
- Overview
- First rule: verify current requirements from the repo
- Goals
- Safety rules
- Scope the deployment first
- 1) Minimal deploy
- 2) Full deploy
- Credential checklist
- Required for the app to run
- Required for a usable hosted deployment
- Required for GitHub-enabled repo flows
- Optional
- PostgreSQL
- JWE secret
- Encryption key
- Vercel OAuth app
- GitHub App
- Redis / KV
- Deployment flow
- First-run verification
- Response format
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
cf865e94de7729751c747171785b6ce57e7b178c- Source SHA-256
0f010ea4c3bb8c6a54751bc35cac9b1ab7fead7db61709bbbf6afdb9fd3ab7c6