Data, connections and limitations

A local application

The Buddies engine runs on your computer, or in WSL2 on Windows. Conversations are read from available provider data, and managed sessions have their own local registry.

This does not mean Claude Code and Codex work offline: their communication with services depends on your provider, account and configuration.

Accounts and integrations

Displayed quotas come from data exposed by the provider, with the time of measurement. Unavailable information is not estimated from tokens.

GitHub and Linear integrations can import issues. Having a saved credential does not, by itself, prove that a connection is valid. Never copy secrets into conversations or public logs.

Remote access

SSH access and the mobile companion are optional. The companion uses a dedicated token and listens on the loopback interface by default. Access from another device requires explicit configuration, such as an SSH tunnel. Installing Buddies does not activate a public service.

Human control

Mission approval, a read receipt and provider permission are three different actions. Buddies never turns one into automatic authorization for the others.

About this website

This website presents the product and its documentation. It does not connect to your agents. No analytics tool or data collection form is installed. Theme and language choices stay in your browser’s local storage; the hosting provider may process technical logs needed to provide the service.

Documentation tied to the code

Public guides live in docs/guide/ (French) and docs/guide/en/ (English) in the same repository as the app. The website is rebuilt from these files; application and engine versions come directly from their manifests.

The guide version and date appear on each page. Changes merged into main trigger continuous deployment. Tests check internal links and generation before publication. A functional change must also update the relevant guide in both languages: this rule is part of the project instructions.

Changes proposed in a pull request have a separate preview. The production website updates through the Git workflow on main after merging; manual production publishing is disabled.