Devory Documentation

The fastest way to get started is the VS Code extension. The terminal path works too. Either way, Devory operates against the repository itself rather than hiding state in a chat session.

If you start from an idea in VS Code, use Devory: Generate Tasks from Idea. It opens a Task Builder webview where you describe the work, generate a Devory-standard task draft, preview the markdown, and save to backlog when ready.

# Day-one terminal path
npx @devory/cli init
npx @devory/cli task new --id factory-001 --title "My first task" --project my-repo
npx @devory/cli task move --task tasks/backlog/factory-001.md --to ready
npx @devory/cli run --validate

Devory uses a controlled lifecycle so work stays visible and reviewable. A task should only move to `ready` when the scope is clear enough to execute safely.

backlog -> ready -> doing -> review -> done
                 \-> blocked
                 \-> archived

• backlog: defined work that is not yet execution-ready
• ready: bounded work that can be picked up safely
• doing: work currently being executed
• review: waiting for human inspection
• done: accepted work
• blocked: work that needs clarification or external input
• archived: intentionally removed from the active flow

The CLI is the main repo-first interface for Devory. The commands below reflect the current wired command surface rather than historical or planned commands, and they are grouped here so an engineer can see what is actually invokable today.

# Common patterns
npx @devory/cli setup --governance-repo ../my-repo-governance --enable-governance
npx @devory/cli init
npx @devory/cli task validate --file tasks/backlog/factory-001.md
npx @devory/cli run --validate
npx @devory/cli governance doctor
npx @devory/cli worker
npx @devory/cli pr-prep tasks/review/factory-001.md
GITHUB_TOKEN=... npx @devory/cli pr-create --task tasks/review/factory-001.md --branch feat/factory-001 --confirm

The extension is a first-class Devory control surface. It is not just a task list. It exposes workspace setup, lifecycle movement, review controls, run execution, doctrine, and skills.

Run start now shows a dry-run/cost estimate summary (advisory only), and generation/refinement flows support deterministic enrichment plus AI-assisted refinement in the task assistant.

The current run-start path is a routing control plane, not just a launch button: it profiles ready tasks, applies routing policy, chooses a provider class, resolves concrete targets, checks readiness, resolves an adapter, and records selected-versus-actual execution metadata truthfully.

Local-first remains the baseline. Cloud is not treated as casual fallback: policy can require confirmation, block execution entirely, or stop automatic escalation when local targets are unavailable. Outcome records are written under artifacts/routing-outcomes/ and can be reviewed with Devory: Show Routing Outcome Summary.

Public npm releases are published from the devory-public GitHub workflow when a matchingv*.*.* tag is pushed. The VSIX stays a manual artifact: build it locally or package it from the optional vscode-v*.*.* workflow path, then upload the resultingdevory-vscode-<version>.vsix yourself.

Devory also has operator-facing web surfaces. These do not replace the local runtime. They submit governance commands, expose review and planning state, and make shared coordination inspectable across machines while `devory worker` remains the runtime that actually applies governance commands.

Truth in behavior: web surfaces handle governance and hosted coordination. VS Code is still the richer local authoring and run-control surface for deterministic generation, AI-assisted refinement, Show Work, dry-run/cost estimate review, local-first routing, and routing outcome review.

Devory can surface situations where a human needs to step in. This matters when a run blocks, a task needs review, or the system needs an explicit answer before continuing.

• Core gives you local repo-first operation and direct inspection in the CLI or editor.
• Pro adds better hosted visibility and factory notifications across devices.
• Teams extends that into shared coordination for multiple people.
• If you need stricter notification routing or controlled-environment handling, contact Devory directly.

Devory supports a guarded GitHub path instead of silently opening PRs. The workflow stays explicit: prepare metadata, inspect it, then create the PR with confirmation.

Devory can run in local and controlled environments. The local repo-first workflow is already a strong fit for teams that do not want normal cloud dependency in the middle of day-to-day engineering.

• Core supports local, repo-first operation and bring-your-own model or API usage.
• You can self-host the runtime path for stricter environments.
• For larger offline or walled-environment deployments, contact Devory directly so the setup can be routed appropriately.