`@leitwerk-dev/process-analysis` adds a UI launcher for read-only analysis of an existing leitwerk process.

`@leitwerk-dev/dev-tools` provides the `leitwerk-dev` CLI for an extension workspace. Install it alongside matching `@leitwerk-dev/server`, `@leitwerk-dev/ui` and SDK versions. Node 26, npm and POSIX are required. Git is needed only for source mode.

Import a Leitwerk process workspace and Pi conversation into local Pi

Server-side extension that exposes leitwerk processes through a Telegram bot.

Registration placeholder only. Not a usable Leitwerk release.

`@leitwerk-dev/gitlab` supplies GitLab v4 API access and repository-scoped HTTPS Git authentication from one server-owned profile. Load this optional extension on the server and worker.

`@leitwerk-dev/dev-sandbox` runs the application with an explicit `SandboxCompositionFactory`. It imports no extensions. The factory receives paths, scripted/real mode, UI/backend origins, and the selected model profile. It supplies the catalog, process c

`@leitwerk-dev/local-shell` provides `local_shell_process`, a no-LLM process for running trusted shell commands on the local leitwerk server machine.

`@leitwerk-dev/github-repo-change` plans, implements, reviews, and publishes a repository change as a GitHub pull request. Load `github`, `git-ssh`, `coding`, and this extension on the server and worker. The extension is opt-in.

`@leitwerk-dev/forgejo-repo-change` plans, implements, and delivers repository changes through a Forgejo pull request. It is opt-in and requires the `forgejo`, `woodpecker`, `coding`, and `git-ssh` extensions. Enable `ticket-creation` when the Forgejo int

`@leitwerk-dev/gitlab-repo-change` plans, implements, reviews, and publishes a repository change as a new GitLab merge request. Load `gitlab`, `coding`, and this extension on the server and worker. The extension is opt-in.

`@leitwerk-dev/pi-shell` provides `pi_shell_process`, a minimal linear Pi session for trusted recovery work focused on a configured local directory.

Shared repository-change planning, review, implementation, state, commit-message, and feature-branch publication support used by provider-owned processes and development compositions.

Provides pinned, non-interactive Git-over-SSH credential profiles to repository processes. Configure profiles under `extensions.git-ssh.credentials`. Private keys and `known_hosts` are delivered only in authenticated `worker.start` IPC; ambient SSH config

The root export contains `ConflictEvidence`, `conflictEvidence`, `validateConflict`, `describeConflict`, `conflictKey`, and `createConflictReporter`. Provider polling can import it without loading Git execution or repair prompts. Evidence shapes and dedup

Provides the generic `ticket_creation_process`. Operators launch it from a durable parent result through the ticket-creation HTTP API. The server snapshots parent context, records a derived-process relation, exposes only the selected capability-marked int

Server-owned Forgejo API profiles, issue discovery, pull-request external sources, and workflow-focused LLM tools. API tokens never enter workers.

Server-owned GitHub API profiles, pull-request state polling, and project-scoped LLM tools. Tokens never enter workers. Reads cover issues, pull requests, reviews, inline comments, Actions check runs, and releases. Pull-request creation, comments, and upd

Server-owned Woodpecker profiles, pipeline external sources, bounded log access, and workflow-focused LLM tools. Tokens never enter workers.

Final approval generates and persists a commit message from the accepted plan before deterministic Git finalization. Repository-specific formatting is selected by the server's `commit_messages` locator mapping and pinned when the process launches. Git com