You stay in control. Non-technical teammates ship inside your guardrails.
Falck is a local-first desktop app that reads `.falck/config.yaml` in your repo. You define what can run, what must be installed, and which branches are allowed. Non-technical teammates contribute with real branches, PRs, and CI untouched. You keep control, they keep momentum, and nobody has to learn git rebase on a Tuesday.
Repository rules
.falck/config.yaml
Setup checks
Node 18, Postgres, Docker
Checks confirm setup is complete before launch.
Setup
bun install
Step 1 of 2, the exact command you approved.
Launch
bun run dev
http://localhost:3000
Branch guardrails
projects/*Default branch stays protected. Your rules, enforced.
Control first
You define the rules. Falck enforces them.
Engineers configure Falck once per repo. After that, non-technical teammates can contribute inside the guardrails you already require: branch prefixes, protected defaults, secrets checks, setup gating, and predictable launch commands. No workflow compromises, no surprise scripts.
Setup checks
Node 18, Postgres, Docker
Save queue
3 staged changes + intent notes
PR ready
Clean summary + clean diff
Intent
"Make onboarding calmer"
Falck notes
Why this change matters
Engineer view
Pick up the same branch
Controlled handoff
Let them sketch in code, without losing control
Falck keeps the change in a real branch with a clear summary. You can merge it as-is, tune it, or continue the implementation with full context. It is like pair programming, minus the calendar math.
Config-first
Define the boundaries once
The `.falck/config.yaml` defines setup steps with checks, secrets, launch commands, and access URLs. Falck enforces the rules so every teammate stays inside your approved flow.
See config details ->Workflow-safe
Git stays yours
Falck keeps branches scoped, tracks save queues, and produces clean commits. Your PRs look normal. Your review flow stays normal. Your blood pressure stays normal.
See workflow ->Local-first
Runtime you control
Falck runs locally, uses OpenCode to orchestrate tools, and can spin containers with Lima when you need isolation.
See runtime ->Built on open source
OpenCode + Lima, full transparency
Falck is open source and transparent. It uses OpenCode to orchestrate models and tools, and Lima to run containerized dev servers when you need parity with production. You control the stack, not the other way around.
Built on
OpenCode + Lima
Falck uses OpenCode to orchestrate models, tools, and workflows, and Lima to run containerized dev servers. They are not affiliated, just excellent humans building great tooling.
Visit opencode.ai