Privacy and network

LlamaTree runs on your machine and has no account. Your code, prompts and conversations stay between you and the agents you run, exactly as they would in any terminal. This page lists everything LlamaTree itself connects to.

What LlamaTree connects to

WhatWhereWhat's sent
Update check, at start and every 15 minutesGitHub's API for this repository's latest releaseAn anonymous request. Nothing about you or your sessions.
Downloading an update, when you click UpdateGitHub releasesAn anonymous download, checked against GitHub's SHA-256 before it runs.
Tips, offers and news, at start and every 30 minutesdownloads.llamachant.comAn anonymous request. Only notices signed with our code-signing certificate are shown. Tips and offers can be turned off.
Sessions on a server, when you connect to oneThe server you name, through your own sshWhatever the server's sessions need: their output, your typing, files you open or paste. Nothing goes through Llamachant.
Pull request chipGitHub or Azure DevOps, for a branch's own remoteThe credential Git Credential Manager already holds for that remote, over HTTPS, to that service only. Cached for 3 minutes.

Fetch, pull and push are ordinary Git commands you run. Suggest runs your own Claude Code or Codex with the diff, as described in Git and diffs.

On your machine

This website

llamatree.dev sets no cookies and has no analytics. To show the latest version, download links and star count, your browser asks GitHub's public API directly, and remembers the answer for an hour in local storage.

Questions

Email support@llamachant.com. The source is all on GitHub, if you'd rather check for yourself.