Questions, answered.

Yes. stkd is an open-source, Apache-2.0-licensed CLI that uses the same gt command, the same stacked-branch metadata model, and supports both GitHub and GitLab (including self-hosted). Existing Graphite users can migrate in a single command.

Yes. stkd has first-class support for GitLab.com and self-hosted GitLab instances, including merge requests, draft MRs, approvals, and pipelines. It is one of very few stacked-diff tools that does.

Plain git only restacks a single branch at a time and forgets the parent relationship between branches. stkd keeps a DAG of your stack, restacks every dependent branch automatically when you edit one, and submits the whole stack as linked PRs in one command.

Yes. stkd ships an MCP (Model Context Protocol) server that exposes gt_create, gt_submit, gt_restack, gt_sync, and gt_land as tools to any MCP-capable AI agent, including Claude Code and Cursor. Agents create branches, submit stacks, and resolve conflicts natively.

Yes. The full source is on GitHub at github.com/neul-labs/stkd under the Apache-2.0 license. The CLI, core engine, web dashboard, and MCP server are all open source — no proprietary components, no paid tier.

macOS, Linux, and Windows. The binary is written in Rust and installable via Homebrew, Cargo, npm, pip, or a one-line curl install script. Same binary, every platform.

Run gt sync. stkd detects the merged branch on the remote, deletes it locally, and restacks the branches that sat on top of it onto the updated trunk. The remaining PRs retarget automatically, so the stack keeps flowing without manual rebasing.

gt restack walks the stack and stops at the first branch that conflicts, leaving you in a normal git conflict state. Resolve the files, run gt continue, and stkd resumes rebasing the rest of the stack from where it paused. gt restack --abort backs the whole operation out.

Yes. gt move re-parents a branch onto a different point in the stack and restacks the affected branches. To split, check out the branch, make commits into new child branches with gt create, and stkd rewires the dependency chain for you.

stkd-server is an optional Rust service that gives a team a shared, live view of every open stack, PR status, and merge queue — running on your own infrastructure behind your own SSO. It is SQLite-backed by default and Postgres-backed for multi-replica deployments. It is entirely optional; the CLI works standalone.

No. stkd has no telemetry or tracking endpoints enabled by default. It talks only to your git remote and, when you run it, your GitHub or GitLab API. The whole source is Apache-2.0 on GitHub for you to audit.

Yes, because both read and write the same git-config stack metadata. A team can migrate incrementally, with some developers on stkd and others still on Graphite, and the stacks stay consistent for everyone.