Quick start // the VS Code extension
Install & first review
Six steps from installing the extension to writing your first verified proof back into Jira or Linear. Most teams are set up in under ten minutes.
Step 01
Install the VS Code extension
Tyne installs from the Visual Studio Code Marketplace like any other extension. You'll need VS Code and Git installed and configured on your machine. Tyne is currently in private beta — you'll need an approved account to sign in, so request access if you don't have one yet.
Step 02
Authenticate with the device flow
Open the Tyne sidebar and click "Continue with GitHub". You'll be shown a short device code. Open the device page in your browser, enter the code, and approve — the extension picks up the session automatically. No password is typed into the editor.
> ABCD-1234 # enter at tyne.io/device
Step 03
Connect your project board
In Tyne Settings, click Connect next to Jira or Linear and authorise over OAuth in your browser. Map your project once, and your active tickets — with their acceptance criteria — appear in the sidebar. This is the connection Tyne verifies your code against.
Step 04
Start a Thread and code
Pick a Jira or Linear task — or set a Solo goal on the Thread tab — and Tyne starts an isolated tyne/<task> branch. Work as normal and commit checkpoints (“stitches”) as you go; Tyne watches the Thread for scope drift while you write.
> tyne/PROJ-482-stripe-checkout # isolated branch, anchored to your task
Step 05
Validate & Review, then tie the knot
Run Validate & Review from the sidebar or with Cmd/Ctrl+Shift+T. You get one combined report — scope alignment against the ticket, code review, and security findings with file/line evidence. Fix findings in-editor, then Tie the Knot to merge once you accept the residual risk.
Step 06
Bring your own key (optional)
Prefer your own model account? Add a Claude or OpenAI key in Tyne Settings. In BYOK mode, requests go directly from your machine to that provider and your code never touches Tyne's servers. Leave it unset to use the managed review service instead — your choice, per workspace.