Skip to content

LlamaTree 1.3.1

Choose a tag to compare

View all tags
@azure-pipelines azure-pipelines released this 06 Nov 03:12
v1.3.1
4a636d3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Your other Windows PCs as servers

Sessions on servers now work with Windows PCs too, not just Linux servers: run sessions on your desktop and work with them from your laptop.

  • Let my other computers connect… (click the version at the top right) sets up the PC you want to connect to: one Windows permission prompt turns on Windows' own SSH server, makes it start with Windows, opens it in the firewall, and turns off password sign-in. Paste your other computer's public key into it, and it shows what to type there (you@that-pc) and the PC's addresses. Turn off undoes it.
  • Sessions run in your desktop session on that PC, so Git's sign-ins work as usual and LlamaTree opened there shows the same sessions. They keep running when the connection drops.
  • The account on that PC must be a local, Microsoft or on-premises domain account; Windows' SSH server can't sign in a work or school (Entra ID) account with a key. See A Windows PC as the server in the guide.

Get plugins and Get themes

Get plugins… and Get themes… in the palette menu list what LlamaTree-Plugins and LlamaTree-Themes publish, with Install, Update, Open and Remove. Downloads are checked against the catalog's SHA-256 before they're unpacked.

Projects as tabs

Layout › Projects as tabs (off unless you turn it on) shows the Top layout's projects as tabs: All, then one per project. Click one to see only its sessions, Ctrl+click to add another, and unpin the ones you use less to move them into a ▾ menu, as in Visual Studio.

Safer

A security review of LlamaTree led to these changes:

  • Updates are checked against signed checksums and the installer's signature, by the updater and by the one-line install scripts, so a copy of an installer from anywhere but us is refused.
  • A repository whose own Git settings can run programs (filters, an SSH command, a credential helper) asks before LlamaTree runs Git there.
  • A server can't get a program run on your computer through a file name it chooses, and a server's sessions, messages and plugin files have limits, so a misbehaving server can't take down your local sessions.
  • Remove Worktree lists ignored files (.env, local settings, build output) before deleting them, and only tidies up that worktree.
  • A damaged sessions.json is kept aside and restored from its backup, not replaced with an empty list.
  • Panel buttons and Refresh type only plain text into a session, never control keys.
  • Plugins: a plugin page that navigates away loses the plugin's permissions, plugin pages can't use the clipboard, and a plugin whose files changed since you allowed it asks again. A plugin's ask is answered by Claude with no tools, even for a Codex session.
  • Terminal links open only web addresses, and a link whose text differs from where it goes shows both first.
  • On Linux and macOS, pasted pictures and the app's connection to its session host stay in your own folders, not the shared /tmp.
  • LlamaTree keeps a log of what it refused or dropped, in its local data folder under logs.

Fixed

  • Codex sessions sometimes left a message or prompt from LlamaTree sitting in the box until you pressed Enter.
  • A session sometimes stayed wrapped at a narrow width while its terminal filled the window.
  • A server session that stopped without saying so (when its server's LlamaTree was updated, say) still showed as running.
  • Down the left, a session whose branch is longer than its name had its name centred over the branch.
  • New session's list of other worktrees showed large empty boxes instead of check boxes and paths.
  • The side panel button now has the side panel's icon, the same as Show/Hide the side panel in its menu, not Git's.
  • Reading a conversation with an unexpected line in it could show its turns more than once.

Install

If you're on 1.0.8 or later on Windows, this update installs itself: click Update to 1.3.1 at the top right. On Linux, a copy installed from the .deb, .rpm or .tar.gz does the same.

Windows: run in PowerShell

powershell -c "irm https://github.com/LlamachantTechnology/LlamaTree/releases/latest/download/install.ps1 | iex"

or download LlamaTree-Setup-1.3.1.exe below and run it.

Linux:

curl -fsSL https://github.com/LlamachantTechnology/LlamaTree/releases/latest/download/install.sh | sh

or download the package for your distribution below: llamatree_1.3.1_amd64.deb (Ubuntu, Debian…), llamatree-1.3.1-1.x86_64.rpm (Fedora, openSUSE…), or LlamaTree-1.3.1-linux-x64.tar.gz (any distribution, for your account only).

On a server, install it the same way, or let LlamaTree do it the first time you connect.

The Windows installer is signed by Llamachant Technology Ltd. If SmartScreen still shows "Windows protected your PC" for this new release, check that the publisher says Llamachant Technology Ltd, then choose More info → Run anyway.

SHA-256 (also in SHA256SUMS, signed in SHA256SUMS.p7s, which the install scripts and the updater check)

85096042d26febb0e905489c2e222845bc8fd83c7ac06d1fd5f5e146fb3dcf28  LlamaTree-Setup-1.3.1.exe
589f938c429532558eec8082c81d97a5699967e602bb2fcad96d160c3b326630  llamatree_1.3.1_amd64.deb
cd7ef7c5e73ff18d79f9962d42ff69da69523dacb5bc95ec2b8ee212f302165d  llamatree-1.3.1-1.x86_64.rpm
f5b7ef2bbeb716db84f0d209a14be491429ae404d93758364af4c1156cb950c9  LlamaTree-1.3.1-linux-x64.tar.gz
Assets 11
Loading