| FMRS | 51 / 100 · D | 77 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 |
|---|
| Security and permissions | 10 / 20 | 16 / 20 |
|---|
| Maintenance | 11 / 20 | 16 / 20 |
|---|
| Documentation | 12 / 20 | 18 / 20 |
|---|
| Setup experience | 10 / 20 | 15 / 20 |
|---|
| Best for | - People who want a team of specialist agents coordinated by a Commander rather than a single chatbot
- Users who insist their data, keys, and agents stay on their own disk instead of a vendor cloud
- Users who want to mix multiple model providers or local model endpoints
- Users who want agents with private skills and memory that improve through reflection
| - Hevy PRO users who want AI assistants to directly access their workout data
- People who prefer using MCP clients like Claude, Cursor, Codex for fitness tracking
- Anyone needing summaries and insights from their training data
|
|---|
| Not for | - People who just want a single all-purpose chatbot
- Users who want a fully hosted/cloud multi-agent team and don't mind their data living on a vendor's servers
- Developers who want a pure code library to embed in their own app (e.g. LangChain or CrewAI-style frameworks)
- Users who cannot run Node 20+ or are on musl-based distributions such as Alpine
| - Users without a Hevy PRO subscription (API key required)
- Users who want to use the server without an API key
- Those needing delete workflows (Hevy API does not expose delete endpoints)
|
|---|
| Required permissions | - Read and write a local workspace directory (~/.orkas/ on macOS/Linux, <smallest non-system drive>:\.orkas\ on Windows)
- Store conversations, files, knowledge bases, custom agents, and API keys on your local disk
- Outbound network access to the model provider endpoints you configure (and to cloud embedding providers if you choose them)
- Run external CLI coding agents (Claude Code, Codex, OpenCode, Cline) as local subprocesses
- Download and verify local resources on first launch (embedding model ~95 MB, whisper.cpp runtime and multilingual speech model, FFmpeg, OfficeCLI, and others)
| - Requires HEVY_API_KEY environment variable for Hevy API authentication
- Can create, update, and replace workouts, routines, folders, templates, and body measurements via tools
- Read operations can fetch workouts, routines, folders, templates, history, and user info
|
|---|
| Risks and side effects | - API keys are stored on your machine's disk and can be read by any process or person with access to that account or device, so OS account security and disk encryption matter
- The Commander can drive external CLI coding agents and run them as local subprocesses, so a model may take actions with side effects; scope the working directory and permissions yourself
- Building from source installs a large dependency tree and prepares native runtimes, making first launch long and network-dependent
- On Linux, only glibc 2.34+ x64/arm64 is supported; Alpine and other musl-based distributions are not
- The packaged desktop app asks you to sign in on first launch; avoiding any account layer means using the source build in this repository
- The optional built-in Orkas model is billed by Orkas in credits, so paths other than your own keys incur additional cost
| - API key can be misused if leaked; do not expose in URLs, logs, or screenshots
- Create operations may produce duplicates on retry; update operations replace existing records
- The server sends data to the Hevy API and may send telemetry to external services unless disabled
|
|---|
| Supported clients | | Claude Desktop, Cursor, Codex, Antigravity |
|---|
| Tools | 6 | 26 |
|---|