Skip to main content
The fintheon CLI is the single entry point for managing your Fintheon installation. After the first-time setup, you use it to start and stop the application, pull updates, tail logs, and connect your AI subscription — all without touching the app itself.

​
Command reference

​
Detailed usage

​
fintheon install

Run fintheon install once, on a fresh machine. It handles everything required to get Fintheon running:
  • Installs Homebrew, Node 22, Bun, Python 3, and uv if they are missing
  • Installs the Claude CLI and Hermes agent
  • Configures VProxy for Anthropic OAuth (opens a browser window — click Allow)
  • Installs all JavaScript dependencies
  • Builds the backend and frontend
  • Installs the fintheon command globally at /usr/local/bin/fintheon
  • Starts the backend and opens the app
After install completes, open the app and sign in with Google. No API keys are needed — credentials are loaded from the cloud on first sign-in.
The installer writes the fintheon symlink to /usr/local/bin. After install, you can run fintheon from any directory without ./.

​
fintheon update

fintheon update pulls the latest code from the repository, rebuilds both the backend and frontend, and restarts all services. No manual steps are required.
If the update fails mid-way, run fintheon stop first to clear any stale processes, then retry fintheon update.

​
fintheon start and fintheon stop

fintheon start starts the Fintheon backend service and, if /Applications/Fintheon.app is present, launches the desktop app. The backend log is written to /tmp/fintheon-backend.log. fintheon stop stops the backend process and quits the Electron app.
fintheon restart is equivalent to running stop followed by start with a short pause between them.

​
fintheon logs

fintheon logs tails the backend log file in real time. Use it to watch startup output, monitor incoming events, or diagnose errors.
The log file location is /tmp/fintheon-backend.log. You can also open it directly:
Press Ctrl C to stop tailing.

​
fintheon status

fintheon status checks whether the backend is listening on port 8080 and whether the Fintheon app process is running. It also prints the current version.
Example output:
If the backend is running, status also prints the raw JSON health response from /health so you can see which services are up.

​
fintheon oauth

fintheon oauth opens the VProxy Anthropic OAuth flow. This connects your Anthropic subscription to the local VProxy gateway, which Harper uses for AI inference in the chat panel.
When to run it:
  • During first-time setup if the installer’s automatic VProxy step failed (you will see a warning at the end of fintheon install)
  • When Harper stops responding and the logs show authentication errors against the VProxy endpoint
  • When you switch to a different Anthropic account
The command opens a browser window. Click Allow to authorize the connection. You do not need to manage any API keys manually — VProxy handles token refresh automatically after the initial authorization.
fintheon oauth only affects Harper’s AI inference. If you switch to Nous or ORouter as your AI provider from the chat dropdown, you do not need to rerun this command.

​
fintheon peers

fintheon peers runs the team onboarding script, which walks through the Twitter round-robin setup for adding new members to your shared Fintheon instance. It configures X authentication keys for additional team members so that polling load is distributed across the pool.
Follow the prompts to add each team member’s Rettiwt key to the pool. Once added, their key appears in Settings › API › Feed Pool alongside yours.

​
fintheon version

Prints the current version string, derived from the latest git tag.

​
Log file

The backend writes all output to /tmp/fintheon-backend.log. This file is replaced each time the backend starts. Use it as your first stop when diagnosing startup failures, API errors, or missing data in the feed.