The logger utility in this project is a file-only logger — every call to logger.log() / logger.error() writes to ~/.routstrd/logs/YYYY-MM-DD.log and produces no terminal output whatsoever. This is intentional and correct for the background daemon (daemon/, start-daemon.ts), which has no attached terminal. However, the onboarding and integration code was mistakenly using logger.log instead of console.log for all of its user-facing output: - setupIntegration() printed the 1-6 integration menu with logger.log, so the user only ever saw the bare prompt 'Select integration [1]: ' with no options above it. The selection appeared to be broken. - Every install*Integration function (opencode, openclaw, claudecode, hermes, pi) reported all progress and results with logger.log, so after picking an integration nothing appeared to happen. - initDaemon() used logger.log for 'Initialization complete!' and the follow-up wallet instructions, so those were also silently dropped. - installCocodOrExit() used logger.log for the 'cocod not found, installing' message and the success/failure result. Fix: replace logger.log/logger.error with console.log/console.error in all CLI-facing code paths (cli.ts, integrations/index.ts, and all five integration installers). Remove the now-unused logger import from the five integration files. The logger import in integrations/index.ts is kept because refreshModelsAndIntegrations() is called by the daemon's internal scheduler and correctly logs to file there. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
routstrd
Routstr daemon - A CLI tool for managing routstr processes, similar to cocod (a Cashu wallet daemon).
Overview
routstrd is a Bun-based CLI tool that provides a background daemon for the Routstr protocol. It integrates with cocod for wallet management and uses the Routstr SDK to handle provider routing and model discovery.
Features
- Daemon Mode: Run routstrd as a background HTTP server
- Wallet Integration: Works with cocod for Cashu token management
- Provider Routing: Automatically discovers and routes requests to available providers
- Config Management: Stores configuration in
~/.routstrd/
Requirements
- Bun runtime
curl -fsSL https://bun.com/install | bash
Installation
Step 1: Install
Global with bun:
bun i -g routstrd
OR - From source:
git clone https://github.com/routstr/routstrd.git
cd routstrd
bun install
bun link
Step 2: Setup & Fund
routstrd onboard
routstrd receive <cashu> # receive a Cashu token
routstrd receive 2100 # to top up 2100 sats with lightning
Step 3: Integrate with Claude Code
routstrd clients add --claude-code # or --pi-agent / --opencode
Use Routstrd Skill
Tip: You can also install the routstrd skill so the agent can manage routstrd for you.
More Commands
Start Daemon
Start the background daemon:
routstrd start
With custom port:
routstrd start --port 9000
With specific provider:
routstrd start --provider https://your-provider.com
CLI Commands
Check daemon status:
routstrd status
Get wallet balance:
routstrd balance
Test connection:
routstrd ping
Stop the daemon:
routstrd stop
Daemon API
The daemon exposes an HTTP server (default port 8008) with the following endpoints:
Health Check
GET /health
Route Request
POST /
Request body:
{
"model": "model-id",
"messages": [...],
"stream": false
}
Response:
{
"choices": [...],
"usage": {...}
}
Configuration
Configuration is stored in ~/.routstrd/config.json:
{
"port": 8008,
"provider": null,
"cocodPath": null
}
Environment Variables
ROUTSTRD_DIR- Config directory (default:~/.routstrd)ROUTSTRD_SOCKET- Socket path (default:~/.routstrd/routstrd.sock)ROUTSTRD_PID- PID file path (default:~/.routstrd/routstrd.pid)
Development
Install dependencies:
bun install
Run CLI:
bun run start
Run daemon:
bun run start
Typecheck:
bun run lint
Project Structure
routstrd/
├── src/
│ ├── index.ts # Entry point with shebang
│ ├── cli.ts # Commander CLI commands
│ ├── cli-shared.ts # IPC utilities
│ ├── daemon.ts # HTTP server daemon
│ └── utils/
│ └── config.ts # Path configuration
├── package.json
└── tsconfig.json
License
MIT