Gitsi repositories

This machine: for you alone

Create a local remote

Install git on your computer, then open Gitsi → This machine. Enter a Repository name and press Create. The bare repository goes into ~/termiyo-repos by default; this is free, nothing is uploaded, and teammates cannot reach it through this feature.

Push or clone locally

Use Copy both lines and run the two lines in the project you want to push. Use Copy the clone line for another checkout on this same computer.

On a host — New in 0.4.22

1. Connect to your server

Open an SSH session to the host in Termiyo, verifying its host key; sharing by link also needs the host saved in Termiyo, not a quick connection. The host needs git; granting access also needs OpenSSH 7.7 or later. Each teammate needs a network route to that host, including their own VPN or jump host when necessary.

2. Prepare and create

Open Gitsi → On a host and select the session if more than one is open. Press Prepare this host when offered, then enter a Repository name and press Create. Termiyo keeps the bare repository in ~/termiyo-repos/<name>.git on that host; preparation uses the SSH account’s home directory and needs no root access or extra daemon.

3. Add your key or a deploy key

Choose Add a key (yours, or a deploy key), enter a name and the public .pub key, choose read only or read and write, then press Grant. This checks only the owner’s paid plan; a trial does not count, and the key has an end date tied to that plan. Copy the invitation supplies the git commands; the recipient can use plain git.

Share by link — New in 0.4.22

Check availability first

Both people must sign in under Account and have a paid plan; a seat on a paid Team, Business or Enterprise team counts, but a trial does not. Sharing by link is off by default and needs the server operator to enable TERMIYO_GITSI_LINKS=on. A paid plan alone does not switch it on.

1. Make the link

On the host’s repository, press Share by link. Choose Access, Who may use it and How long the link lives (1, 3 or 7 days), and check Where they connect (the host's address). An optional passcode needs at least 8 characters; five wrong tries lock the link. Press Make the link, then Copy the link: it is shown only once. Send any passcode separately.

2. Ask for access

The recipient opens Gitsi → Shared with me, pastes the link and presses Look at this link. They enter the passcode if needed, choose their key under Which key to be let in with and press Ask to be let in. The link alone grants no access.

3. Approve and connect

The owner checks the confirmed email address and key fingerprint, selects the name and access, then presses Let them in. The recipient uses the displayed SSH configuration and clone or remote lines; Termiyo does not write their ~/.ssh files for them. Test access checks whether the repository can be reached.

4. End or renew access

Take back removes access from the host before revoking the link. A link’s expiry does not remove an already granted key: that key ends at the earlier of the two paid-plan end dates. Renew can update those end dates on the host after the plans are renewed, until the access is taken back with Take back or the recipient leaves.

Limits

Repository access, with a defined scope

Termiyo’s local/SSH repository mode has no web repository browser, pull requests, issues, code review or package registry. Its grants control fetch and push for the keys it installs; anyone with ordinary shell access to the host account can reach the repositories directly. A push identifies a key, not the author of a commit.

Validation so far

The full share-by-link flow has not been verified with live paid accounts.

In preview · not yet released

Your Gitsi account, inside Termiyo

Create or sign in to your own Gitsi account, then connect through browser consent or your own personal token. The dashboard appears after account validation; Termiyo supplies no shared account or owner repositories. OAuth starts with read access; repository creation needs explicit extra consent, and pull requests currently need a personal token with the appropriate issue scopes. Private and shared repositories follow your account’s permissions. Tokens use OS-protected local storage, and disconnect clears the local connection.

Browse your repositories, create a new one and work with pull requests from your own Gitsi account.

The preview includes repository browsing and creation, pull-request creation, descriptions, diffs and commit checks. Pull-request merge is unavailable. Native HTTPS clone is for macOS and Linux; Windows clone, native pull/push, LFS downloads and submodule initialization are not included.

Watch a pull request while the app is open

Explicitly watch one Gitsi pull request for one hour, polling every 60 seconds while Termiyo stays open and unlocked. Use your own account’s personal token with read:issue and read:repository. Observed changes can become an editable text draft only: no AI call or repository mutation. After restart or permission denial, old cards stay hidden until a fresh successful Start.

Create a Gitsi account Sign in on Gitsi

Git on your own server