Celeborn Code User Agreement

1. Celeborn Code is a tool

Celeborn Code has no mind, agency, or intent of its own. It is software that performs only the actions you turn on by installing it, wiring it into your coding agent, and running it. Every behavior described below is deterministic and configurable. By installing, wiring, and using Celeborn Code you instruct it to act on your behalf and direct it to perform the automations you leave enabled. Celeborn Code does not decide what to do — it carries out what you have configured.

2. What Celeborn Code does for you, and why

Each item below removes an approval click. All are enabled by default; you may opt out of any of them at install time or any time afterward by running celeborn consent.

1. Pre-approve safe read-only commands and enable acceptEdits modeSo you stop clicking “Allow” for ls / grep / git-status and routine file edits.Safety: Your editor and the safe-listed commands then run without a per-action prompt. The allow-list is read-only/reversible commands only; acceptEdits lets the agent write files in the working tree without asking each time.
2. Generalize your repeated approvals into reusable allow-rules (celeborn permissions)A command you approve more than once becomes a wildcard rule you never re-approve again.
3. Capture and restore project context automatically across sessionsOrient load, per-turn capture, and checkpoint reminders — so a /clear or compaction never makes you re-explain the project.Safety: Project context is written to a local .context/ directory in your repo. Signing in uses your GitHub account for identity; your context stays on your machine unless you enable sync.
4. Steer an un-approvable cd … > file write to the Write tool (PreToolUse guard)Turns a recurring manual approval into an invisible, statically-safe file write.
5. Auto-allow a marked cd … > file write with no promptA command tagged # celeborn:allow-redirect runs without asking.Safety: Significant: a shell write whose target the permission system cannot statically verify then runs with no human check. This is OFF unless you keep it enabled; it exists for the rare case a shell redirect is genuinely required. The default posture denies the pattern and steers to the Write tool.
6. Auto-launch your local kanban board on orientThe board comes up on a local port without a manual command.
7. Auto-claim a task card when you paste its markerPasting a card assigns it to you without a separate claim step.
8. Run tests / typecheck automatically after edits (opt-in via wire-quality)Surfaces failures without you remembering to run the suite.

3. Safety considerations

Reducing prompts means Celeborn Code (and the coding agent it serves) takes some actions without asking you each time. You should understand and accept the following before enabling them:

• Celeborn Code acts with your permissions. It runs as you, on your machine, and can read and modify files and run commands that your agent and your permission settings allow. It never grants itself more access than your configuration permits.
• Pre-approval and acceptEdits. The safe permission baseline lets read-only commands and in-tree file edits proceed without a per-action prompt. This is convenience at the cost of per-action review; the baseline excludes destructive, network, and non-reversible commands.
• The auto-allow redirect bypass is the most significant risk. When enabled, a command explicitly tagged # celeborn:allow-redirect performs a shell write whose destination the permission system cannot statically verify — with no human approval. Leave it disabled unless you specifically want that.
• Context capture is local by default. Celeborn Code writes project notes to a local .context/ directory. Nothing is transmitted off your machine unless you separately create an account and enable sync.

4. Your control

You remain in control at all times. Run celeborn consent to review or change which automations are enabled. Manage the underlying agent permissions with your agent's permission settings (for example /permissions in Claude Code). Re-running celeborn wire never removes anything you added, and you can unwire or uninstall Celeborn Code to stop all of its behavior.

5. Acceptance

By typing your name into the consent prompt you confirm that you have read this agreement, that you understand the automations and safety considerations above, and that you direct Celeborn Code to perform the automations you have left enabled. Your name, the time, the agreement version, and your opt-out selections are recorded locally to ~/.context/consent.json.

6. No warranty

Celeborn Code is provided “as is”, without warranty of any kind, express or implied. To the maximum extent permitted by law, the authors and contributors are not liable for any claim, damages, or other liability arising from its use. You are responsible for the actions you authorize Celeborn Code and your coding agent to take. This agreement supplements, and does not replace, the project's open-source license.