• Set up for your team. The Providers tab has a second team card for whoever has the models: the quick-start command and a link to the gateway page on twinny.dev. The same link is the command Twinny - Set up for your team.
• One notice, once. Two weeks after first use on a machine that is not connected to a team, one information message says the gateway exists, with See how and No thanks. It is recorded as shown before it appears, so dismissing it is also the end of it. A machine connected to a team never sees it.
• The Marketplace description and both READMEs name the team gateway, the price, and the free 30-day trial at twinny.dev. twinny-server is republished for its README only; the gateway itself is unchanged.

Plugins

Plugins are features the gateway ships with but that stay off until an admin switches them on from Plugins → Store on the admin page. Each has its own routes, files and page. They are a licence feature: without one the store lists them but none can be switched on, and plugins that were on stop when a licence lapses and start again when one is installed.

• GitHub and GitLab pull requests. Watch repositories with a token or a GitHub App and the admin page lists every open pull request across them: checks, merge state, review state, drafts. Open one to read the description and highlighted diffs. Review now sends it to one of the gateway's own chat aliases and keeps the review on the server; auto-review does it in the background for new and updated pulls while no developer request is running.
• Gitea, Forgejo, Codeberg and Bitbucket Cloud on the same pull-request core.
• Reviews posted back to the host as a comment, a change request or an approval, with a footer naming the model; auto-post per repository. A review in progress shows as a status row.
• Issue triage. Open issues are listed beside pulls; a model suggests labels, a duplicate, a priority and a first reply, kept on the server until someone posts the reply or applies the labels. Auto-triage suggests while the models are idle.
• Pull-request pages have one listing toolbar on every forge: one-click views with live counts, selects for repository, author, label, target branch and activity, a search, order by, sortable headers, all remembered per host. Each pull carries its approvals as the host reports them, and the page tags each pull with the operator's part in it ("waiting for me"). Drafts stay out of the list until a toggle brings them in.
• Reasoning models are asked not to think when reviewing (think: false on Ollama); reasoning deltas and inline <think> blocks are recognised, and a thinking-only answer fails with the reason.
• Slack, Discord and Microsoft Teams post chosen events to webhooks (Mattermost and Rocket.Chat take the Slack shape): a review finished or asked for changes, a pull opened, checks failed, a backup made or failed, a backend down or back. A test button and a delivery log per webhook; URLs are kept secret. Plugins share one event bus.
• SSO sign-in (OIDC). Developers sign in with Okta, Entra ID, Google Workspace, Keycloak or any OpenID Connect provider: PKCE, nonce, RS256 id_token verified against the provider's keys, a domain allow-list, admin emails, and a key minted through a replacing invite that opens VS Code. Signing in again replaces the key, so it doubles as lost-key recovery.
• Shared context. Repositories are cloned shallow onto the gateway, chunked, embedded with an embeddings alias it serves, and re-indexed on a schedule while the models are idle, embedding only what changed. Connected extensions search it with their key and merge the hits into the relevant code their chat already gathers.
• Backups. A nightly copy of configuration, keys, licence, invites, plugins and usage (recordings on request) to a directory or an S3-compatible bucket, optionally encrypted, with retention and a CLI restore (twinny-server backup restore).
• Plugin logos on the store, navigation and pages; skeleton loaders while a page loads; themed scrollbars on panels and code blocks.

Gateway operations

• Audit log. Every admin change (keys, invites, sign-ins, configuration, licence, plugins on or off, plugin writes) goes to audit/YYYY-MM.jsonl, each line carrying the hash of the line before it. Team → Audit log shows whether the chain is intact, filters by period, actor and kind, and exports.
• Read-only admins. keys create <name> --admin --read-only (or the box on People) opens the admin page and every GET admin route and refuses anything that changes state.
• Prometheus metrics at GET /metrics for admin keys: requests by route, alias and outcome, a latency histogram, tokens, in-flight and queued requests, backend health, refused authentications, seats, plugin events.
• Costs. Give an alias a price per million input and output tokens and a currency, and Usage and Overview show what each developer, model and period cost.
• Bounded request queue. A chat or autocomplete request that finds every slot taken waits, oldest first, for up to limits.queue.fimWaitMs or chatWaitMs before it is refused; at most limits.queue.maxWaiting may wait. A client that goes away while waiting is dropped as request.abandoned. Refusal logs say whether the gateway, the queue or the key's own limit refused; twinny_queued_requests is exported.
• Data-directory format marker. format.json names the layout; migrations run in order at start, a newer format than the build knows exits with code 6, and a directory with files but no marker is taken as format 1. Backups carry the marker along.
• Routing rules in team policy keep a workspace on local backends or on named aliases, matched on the workspace name the extension now sends. Team system prompt in policy is put before every chat's system prompt on connected extensions and shown on the consent card.
• Helm chart under deploy/helm/twinny-server: one pod, one volume, an optional Ingress with TLS, a ServiceMonitor for /metrics.
• The admin shell widens to 1480px and folds the sidebar into tabs below 960px.

• twinny-server, a dependency-free Node package built from src/gateway: quickstart finds a local model server, writes a configuration, makes an admin key and serves; init, serve, keys, invites, usage, license, recordings, reset. Any OpenAI-compatible backend, Ollama, LM Studio, llama.cpp, QVAC or a hosted API behind named aliases.
• Protocol v1 at /twinny/v1: models, chat, fim and embeddings streamed as NDJSON, with typed error kinds; the extension's Twinny gateway provider speaks it with a token kept in VS Code secret storage.
• A key per developer, stored as a hash, created and revoked live on the admin page or the CLI; per-key limits; a shared token that can be retired.
• Invite links (vscode:// URI handler) that open VS Code and connect with nothing to paste; one use, seven days, no seat until opened. Sign-in with a short code as the alternative.
• Usage per person and per model: requests, failures, token counts, indexing runs; retention you choose; never the content.
• Admin page at /admin: overview, usage charts, people, policy, providers and models (edited live), plan and licence, recordings.
• Team GPU pooling. A developer flips Share this computer and their local server serves the team through a WebSocket to the gateway: no port to open, consent shown, least-loaded first, failover when a sharer goes offline.
• Seat licensing. Five seats free for good; a signed twl1. token bought by card raises the count and switches on policy and recording. Checked locally, no call home, 30-day notice and 14-day grace.
• Team policy (licence): team-gateway-only providers and locked defaults, shown for consent before connecting and enforced by the extension while connected. Leave team is one click.
• Recording (licence): keep chat, autocomplete and embedding content on the gateway, disclosed to every developer, reviewed and exported as training data from the admin page.
• Docker image ghcr.io/twinnydotdev/twinny-server with a compose file; demo mode (serve --demo) for a read-only public admin page with one-hour guest keys.
• Autocomplete fix: a client that hung up after the first chunk no longer logs the request as cancelled.

• Autocomplete rebuilt: a per-request completion stream with a termination policy (stop words, blank line, dedent, bracket depth, suffix duplicate, max lines), type-through continuation, stop sequences sent server-side, plain continuation at end of file, imports first in the context budget. Template bugs for qwen2.5-coder, CodeGemma and DeepSeek fixed.
• Devices: use the GPU in another of your computers over an encrypted peer-to-peer link with a pairing code; no account, no relay. Symmetry is removed.
• First run discovers a local model server instead of assuming Ollama; a welcome view and a reset command.
• Next edit as its own provider type for the Sweep next-edit model.
• QVAC located at runtime with an in-tab install guide.
• Status bar rewritten; the commit-message command restored; chat lifecycle and error fixes; macOS 15 Intel build.