ralph-orchestrator
Open-source desktop app for Mac, Windows and Linux. Agents run on your computer or on your own server.
Product websitegithub.com Compare with others Missing or wrong data?
- Desktop app
- Mac, Windows and Linux
- Browser
- Yes
- Phone
- Not listed
- Command line
- Yes
- Agents
- Claude Code, Codex, Gemini CLI, OpenCode and Pi
- Your subscription
- Works with your own plan
- Agents run
- On your computer and on your own server
- Laptop closed
- Keeps going
- Isolation
- Worktree
- Parallel agents
- Yes
- Scheduled runs
- Yes
- Coordinator agent
- Yes
- Built-in issues
- Yes
- Pull requests
- No
- Review screen
- Yes
- Team
- Shared sessions
- Self-hosting
- Yes
- Licence
- MIT
- Price from
- Free
- How it charges
- No paid plan and bring your own key
- Paid plans from
- Not listed
Receipts
- Checked
- · oldest answer 2026-11-08
- Findings
- 33 published · 22 cross-checked by a second agent · read them all
- Sources
- 22 public pages on 1 site: github.com
- Screenshot
- github.com, retrieved · first party repository · shows appearance, not capability
- Method
- Same rules for all 103 researched ADEs. How we check · Report wrong data
What it does
Where you use it
Ralph supplies a native CLI/TUI on macOS, Linux and Windows plus an alpha browser dashboard and Telegram integration. It has no product-owned native phone app.
Source and scope for Where you use itAgents it runs
Eleven named CLI backends and custom commands are documented, with different backends selectable per hat.
Source and scope for Agents it runsAccounts and subscriptions
Backend setup supports native Claude login and provider API credentials. Costs and account rights belong to the selected agent.
Source and scope for Accounts and subscriptionsWhere agents run
Ralph normally invokes installed agent CLIs on the current host. Its documented alpha legacy Node web mode also supplies an operator-hosted network server with detached agent processes independent of browser clients.
Source and scope for Where agents runHow work is kept apart
Ralph separates parallel loop checkouts with Git worktrees and runs native host CLI processes; it provides no built-in container or VM isolation.
Source and scope for How work is kept apartParallel work
Additional concurrent loops run in separate Git worktrees.
Source and scope for Parallel workScheduled runs
The alpha legacy Node API can start agent work from externally created unblocked tasks through its owned dispatcher, without a human initiating each execution.
Source and scope for Scheduled runsGit and pull requests
Ralph integrates worktree diff, branch publish/rebase and merge operations; publish-review writes a Markdown handoff and pushes the branch without creating a pull request.
Source and scope for Git and pull requestsPrice
Ralph is free MIT software without a published paid Ralph plan. Its supported backend setup accepts the user provider API keys or native CLI logins, billed separately.
Source and scope for PriceTyped filters
Every value links to its receipt below. Read plan and surface restrictions before using a filter to decide.
| Filter | Value |
|---|---|
| Desktop OS: macOS | Yes |
| Desktop OS: Windows | Yes |
| Desktop OS: Linux | Yes |
| Web client | Yes |
| Phone access: Native iOS | No |
| Phone access: Native Android | No |
| Phone access: Phone browser | Unknown |
| CLI | Yes |
| Coding agents: Claude Code | Yes cross-checked |
| Coding agents: Codex | Yes cross-checked |
| Coding agents: Cursor Agent | Unknown |
| Coding agents: Gemini CLI | Yes cross-checked |
| Coding agents: OpenCode | Yes cross-checked |
| Coding agents: Pi | Yes cross-checked |
| Coding agents: Grok | Unknown |
| Coding agents: Aider | Unknown |
| Coding agents: Antigravity | Unknown |
| Use my subscription | Yes cross-checked |
| Where agents run: On your computer | Yes |
| Where agents run: On your own server | Yes |
| Where agents run: In the vendor's cloud | No |
| Workspace isolation: Git worktree | Yes |
| Workspace isolation: Container | No |
| Workspace isolation: VM or microVM | No |
| Parallel runs | Yes cross-checked |
| Coordinator | Yes |
| Native issue tracking | Yes cross-checked |
| Unattended triggers | Yes |
| Shared prompting | Yes |
| Team roles | No |
| SSO | No |
| Pull request workflow | No |
| Review interface | Yes |
| Product license: Apache-2.0 | No. MIT cross-checked |
| Product license: MIT | Yes. MIT cross-checked |
| Product license: GPL-3.0 | No. MIT cross-checked |
| Product license: GPL-3.0-or-later | No. MIT cross-checked |
| Product license: AGPL-3.0 | No. MIT cross-checked |
| Product license: AGPL-3.0-or-later | No. MIT cross-checked |
| Product license: Elastic License 2.0 | No. MIT cross-checked |
| Product license: Custom terms | No. MIT cross-checked |
| Product license: Proprietary | No. MIT cross-checked |
| Self-hosting | Yes cross-checked |
| Telemetry opt-out | Yes |
| Free access | Yes cross-checked |
| Starting price: Free | Yes. Free cross-checked |
| Starting price: Up to $20/month | No. Free cross-checked |
| Starting price: $21–40/month | No. Free cross-checked |
| Starting price: $41–100/month | No. Free cross-checked |
| Starting price: Over $100/month | No. Free cross-checked |
| Starting price: Contact for pricing | No. Free cross-checked |
| Pricing model: Free, no paid plan | Yes |
| Pricing model: Free plan | No |
| Pricing model: Subscription | No |
| Pricing model: Per seat | No |
| Pricing model: Usage-based | No |
| Pricing model: Per machine or compute | No |
| Pricing model: Bring your own key | Yes |
| Pricing model: One-time purchase | No |
| Paid plans from: No paid plan | Unknown |
| Paid plans from: $10 or less/month | Unknown |
| Paid plans from: $11–20/month | Unknown |
| Paid plans from: $21–40/month | Unknown |
| Paid plans from: $41–100/month | Unknown |
| Paid plans from: Over $100/month | Unknown |
| Paid plans from: Contact sales | Unknown |
| Lifecycle status: Active | Unknown |
| Lifecycle status: Sunsetting | Unknown |
| Keeps going with laptop closed | Yes |
| Open-source license | Yes. MIT cross-checked |
| Any desktop app | Yes |
| Paid plan up to $20/month | Unknown |
| Paid plan up to $40/month | Unknown |
| Any phone client | Unknown |
Filter receipts
Desktop OS: macOS: Yes
Desktop OS: macOS
Typed value: Yes.
Ralph supplies a native CLI/TUI on macOS, Linux and Windows plus an alpha browser dashboard and Telegram integration. It has no product-owned native phone app.
- Desktop os: The first-party installation OS list is macOS, Linux and Windows.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: mobile_browser, editor_extensions, notifications, cross_device_continuity.
-
ralph-orchestrator: docs/installation.md
Finding: The first-party installation guide explicitly supports macOS, Linux and Windows for the native Ralph CLI. These are terminal clients rather than desktop GUI applications.
Desktop OS: Windows: Yes
Desktop OS: Windows
Typed value: Yes.
Ralph supplies a native CLI/TUI on macOS, Linux and Windows plus an alpha browser dashboard and Telegram integration. It has no product-owned native phone app.
- Desktop os: The first-party installation OS list is macOS, Linux and Windows.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: mobile_browser, editor_extensions, notifications, cross_device_continuity.
-
ralph-orchestrator: docs/installation.md
Finding: The first-party installation guide explicitly supports macOS, Linux and Windows for the native Ralph CLI. These are terminal clients rather than desktop GUI applications.
Desktop OS: Linux: Yes
Desktop OS: Linux
Typed value: Yes.
Ralph supplies a native CLI/TUI on macOS, Linux and Windows plus an alpha browser dashboard and Telegram integration. It has no product-owned native phone app.
- Desktop os: The first-party installation OS list is macOS, Linux and Windows.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: mobile_browser, editor_extensions, notifications, cross_device_continuity.
-
ralph-orchestrator: docs/installation.md
Finding: The first-party installation guide explicitly supports macOS, Linux and Windows for the native Ralph CLI. These are terminal clients rather than desktop GUI applications.
Web client: Yes
Web client
Typed value: Yes.
Ralph supplies a native CLI/TUI on macOS, Linux and Windows plus an alpha browser dashboard and Telegram integration. It has no product-owned native phone app.
- Browser: ralph web opens the alpha dashboard.
- Cli: ralph commands run and manage loops.
- Task actions: Telegram supports status, tasks, restart and proactive guidance.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: mobile_browser, editor_extensions, notifications, cross_device_continuity.
-
Finding: Ralph offers CLI/TUI loops, an alpha web dashboard, workspace-scoped MCP server, planning documents, backend selection and Telegram intervention.
Phone access: Native iOS: No
Phone access: Native iOS
Typed value: No.
Ralph supplies a native CLI/TUI on macOS, Linux and Windows plus an alpha browser dashboard and Telegram integration. It has no product-owned native phone app.
- Mobile apps: The product client inventory is CLI/TUI, alpha web and Telegram integration, without a native Ralph iOS/Android client.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: mobile_browser, editor_extensions, notifications, cross_device_continuity.
-
ralph-orchestrator: crates/ralph-cli/src/loops.rs
Finding: Bounded inspection of the native loop and alpha web runtime found installed host CLI processes and Git-worktree separation, without product-managed container/VM provisioning, enterprise human SSO or named human team permissions. Hat roles are agent operational roles. publish-review pushes a branch and writes a Markdown handoff; it does not create or manage a pull request.
Phone access: Native Android: No
Phone access: Native Android
Typed value: No.
Ralph supplies a native CLI/TUI on macOS, Linux and Windows plus an alpha browser dashboard and Telegram integration. It has no product-owned native phone app.
- Mobile apps: The product client inventory is CLI/TUI, alpha web and Telegram integration, without a native Ralph iOS/Android client.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: mobile_browser, editor_extensions, notifications, cross_device_continuity.
-
ralph-orchestrator: crates/ralph-cli/src/loops.rs
Finding: Bounded inspection of the native loop and alpha web runtime found installed host CLI processes and Git-worktree separation, without product-managed container/VM provisioning, enterprise human SSO or named human team permissions. Hat roles are agent operational roles. publish-review pushes a branch and writes a Markdown handoff; it does not create or manage a pull request.
CLI: Yes
CLI
Typed value: Yes.
Ralph supplies a native CLI/TUI on macOS, Linux and Windows plus an alpha browser dashboard and Telegram integration. It has no product-owned native phone app.
- Browser: ralph web opens the alpha dashboard.
- Cli: ralph commands run and manage loops.
- Task actions: Telegram supports status, tasks, restart and proactive guidance.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: mobile_browser, editor_extensions, notifications, cross_device_continuity.
-
Finding: Ralph offers CLI/TUI loops, an alpha web dashboard, workspace-scoped MCP server, planning documents, backend selection and Telegram intervention.
Coding agents: Claude Code: Yes cross-checked
Coding agents: Claude Code
Typed value: Yes.
Eleven named CLI backends and custom commands are documented, with different backends selectable per hat.
- Harnesses: Claude Code, Codex, Gemini CLI, OpenCode, Pi, Kiro, Forge, Amp, Copilot CLI, Roo and OMP.
- Custom adapters: Custom command backend accepts argument or stdin prompts.
- Mixed harness operation: Per-hat backend overrides allow a mixed-backend workflow.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: Names Claude Code, Codex, Gemini CLI, OpenCode and Pi among eleven backends, documents native Claude login and API keys, and per-hat backend overrides.
Coding agents: Codex: Yes cross-checked
Coding agents: Codex
Typed value: Yes.
Eleven named CLI backends and custom commands are documented, with different backends selectable per hat.
- Harnesses: Claude Code, Codex, Gemini CLI, OpenCode, Pi, Kiro, Forge, Amp, Copilot CLI, Roo and OMP.
- Custom adapters: Custom command backend accepts argument or stdin prompts.
- Mixed harness operation: Per-hat backend overrides allow a mixed-backend workflow.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: Names Claude Code, Codex, Gemini CLI, OpenCode and Pi among eleven backends, documents native Claude login and API keys, and per-hat backend overrides.
Coding agents: Gemini CLI: Yes cross-checked
Coding agents: Gemini CLI
Typed value: Yes.
Eleven named CLI backends and custom commands are documented, with different backends selectable per hat.
- Harnesses: Claude Code, Codex, Gemini CLI, OpenCode, Pi, Kiro, Forge, Amp, Copilot CLI, Roo and OMP.
- Custom adapters: Custom command backend accepts argument or stdin prompts.
- Mixed harness operation: Per-hat backend overrides allow a mixed-backend workflow.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: Names Claude Code, Codex, Gemini CLI, OpenCode and Pi among eleven backends, documents native Claude login and API keys, and per-hat backend overrides.
Coding agents: OpenCode: Yes cross-checked
Coding agents: OpenCode
Typed value: Yes.
Eleven named CLI backends and custom commands are documented, with different backends selectable per hat.
- Harnesses: Claude Code, Codex, Gemini CLI, OpenCode, Pi, Kiro, Forge, Amp, Copilot CLI, Roo and OMP.
- Custom adapters: Custom command backend accepts argument or stdin prompts.
- Mixed harness operation: Per-hat backend overrides allow a mixed-backend workflow.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: Names Claude Code, Codex, Gemini CLI, OpenCode and Pi among eleven backends, documents native Claude login and API keys, and per-hat backend overrides.
Coding agents: Pi: Yes cross-checked
Coding agents: Pi
Typed value: Yes.
Eleven named CLI backends and custom commands are documented, with different backends selectable per hat.
- Harnesses: Claude Code, Codex, Gemini CLI, OpenCode, Pi, Kiro, Forge, Amp, Copilot CLI, Roo and OMP.
- Custom adapters: Custom command backend accepts argument or stdin prompts.
- Mixed harness operation: Per-hat backend overrides allow a mixed-backend workflow.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: Names Claude Code, Codex, Gemini CLI, OpenCode and Pi among eleven backends, documents native Claude login and API keys, and per-hat backend overrides.
Use my subscription: Yes cross-checked
Use my subscription
Typed value: Yes.
Backend setup supports native Claude login and provider API credentials. Costs and account rights belong to the selected agent.
- Agent subscriptions: Claude native login is documented; subscription entitlements depend on the underlying account.
- Api accounts: Provider key configuration is documented for supported backends.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: Names Claude Code, Codex, Gemini CLI, OpenCode and Pi among eleven backends, documents native Claude login and API keys, and per-hat backend overrides.
Where agents run: On your computer: Yes
Where agents run: On your computer
Typed value: Yes.
Ralph normally invokes installed agent CLIs on the current host. Its documented alpha legacy Node web mode also supplies an operator-hosted network server with detached agent processes independent of browser clients.
- Local: User-installed ralph invokes local coding backends.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: self_hosted, hybrid, provisioning, payer, resources, region, expiry, other_device_continuation.
-
Finding: Ralph offers CLI/TUI loops, an alpha web dashboard, workspace-scoped MCP server, planning documents, backend selection and Telegram intervention.
Where agents run: On your own server: Yes
Where agents run: On your own server
Typed value: Yes.
Ralph normally invokes installed agent CLIs on the current host. Its documented alpha legacy Node web mode also supplies an operator-hosted network server with detached agent processes independent of browser clients.
- Byo remote: The alpha legacy Node backend binds a network host and runs the installed Ralph process on that operator host.
- Managed cloud: The inspected public runtime modes run installed CLIs on operator machines, without a Ralph-operated compute service.
- Client disconnect: ProcessSupervisor starts detached/unref processes with persisted PID/status/logs; browser disconnect does not own their lifetime.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: self_hosted, hybrid, provisioning, payer, resources, region, expiry, other_device_continuation.
-
ralph-orchestrator: backend/ralph-web-server/src/runner/ProcessSupervisor.ts
Finding: The documented alpha web command can enable the legacy Node backend. That backend binds an operator-selected network host, starts detached native Ralph processes, persists PID/status/logs and can reconnect after server restarts. Agent work is owned by that server process tree rather than a browser connection. This is a self-hosted alpha mode; no managed Ralph cloud is supplied.
Where agents run: In the vendor's cloud: No
Where agents run: In the vendor's cloud
Typed value: No.
Ralph normally invokes installed agent CLIs on the current host. Its documented alpha legacy Node web mode also supplies an operator-hosted network server with detached agent processes independent of browser clients.
- Byo remote: The alpha legacy Node backend binds a network host and runs the installed Ralph process on that operator host.
- Managed cloud: The inspected public runtime modes run installed CLIs on operator machines, without a Ralph-operated compute service.
- Client disconnect: ProcessSupervisor starts detached/unref processes with persisted PID/status/logs; browser disconnect does not own their lifetime.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: self_hosted, hybrid, provisioning, payer, resources, region, expiry, other_device_continuation.
-
ralph-orchestrator: backend/ralph-web-server/src/runner/ProcessSupervisor.ts
Finding: The documented alpha web command can enable the legacy Node backend. That backend binds an operator-selected network host, starts detached native Ralph processes, persists PID/status/logs and can reconnect after server restarts. Agent work is owned by that server process tree rather than a browser connection. This is a self-hosted alpha mode; no managed Ralph cloud is supplied.
-
ralph-orchestrator: crates/ralph-cli/src/loops.rs
Finding: Bounded inspection of the native loop and alpha web runtime found installed host CLI processes and Git-worktree separation, without product-managed container/VM provisioning, enterprise human SSO or named human team permissions. Hat roles are agent operational roles. publish-review pushes a branch and writes a Markdown handoff; it does not create or manage a pull request.
Workspace isolation: Git worktree: Yes
Workspace isolation: Git worktree
Typed value: Yes.
Ralph separates parallel loop checkouts with Git worktrees and runs native host CLI processes; it provides no built-in container or VM isolation.
- Worktree: Additional loops use a separate Git working directory named for the loop ID.
- Code separation: Loop events, tasks and scratchpad are isolated by worktree.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: checkout, branch, os_sandbox, filesystem, process, network, secrets, security_boundary.
-
docs/advanced/parallel-loops.md
Finding: Concurrent loops have worktrees, separate events/tasks and shared memories. Completed work can enter a merge queue or publish remote review branches; failed merges need review.
Workspace isolation: Container: No
Workspace isolation: Container
Typed value: No.
Ralph separates parallel loop checkouts with Git worktrees and runs native host CLI processes; it provides no built-in container or VM isolation.
- Container: No product-managed container provisioning is present in the inspected runtime paths.
- Vm: No product-managed VM provisioning is present in the inspected runtime paths.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: checkout, branch, os_sandbox, filesystem, process, network, secrets, security_boundary.
-
ralph-orchestrator: crates/ralph-cli/src/loops.rs
Finding: Bounded inspection of the native loop and alpha web runtime found installed host CLI processes and Git-worktree separation, without product-managed container/VM provisioning, enterprise human SSO or named human team permissions. Hat roles are agent operational roles. publish-review pushes a branch and writes a Markdown handoff; it does not create or manage a pull request.
Workspace isolation: VM or microVM: No
Workspace isolation: VM or microVM
Typed value: No.
Ralph separates parallel loop checkouts with Git worktrees and runs native host CLI processes; it provides no built-in container or VM isolation.
- Container: No product-managed container provisioning is present in the inspected runtime paths.
- Vm: No product-managed VM provisioning is present in the inspected runtime paths.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: checkout, branch, os_sandbox, filesystem, process, network, secrets, security_boundary.
-
ralph-orchestrator: crates/ralph-cli/src/loops.rs
Finding: Bounded inspection of the native loop and alpha web runtime found installed host CLI processes and Git-worktree separation, without product-managed container/VM provisioning, enterprise human SSO or named human team permissions. Hat roles are agent operational roles. publish-review pushes a branch and writes a Markdown handoff; it does not create or manage a pull request.
Parallel runs: Yes cross-checked
Parallel runs
Typed value: Yes.
Additional concurrent loops run in separate Git worktrees.
- Concurrent sessions: Multiple loops run simultaneously.
- Concurrent tasks: Separate prompts execute in separate loops.
- Status visibility: ralph loops lists running, queued, merged, crashed and needs-review states.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
docs/advanced/parallel-loops.md
Finding: Concurrent loops have worktrees, separate events/tasks and shared memories. Completed work can enter a merge queue or publish remote review branches; failed merges need review.
Coordinator: Yes
Coordinator
Typed value: Yes.
The shipped Hatless Ralph coordinator delegates work through named hat events, receives their event results and can route hats to different coding-agent backends with fresh iteration context.
- Roles: The product supplies a constant Ralph coordinator and named specialized hat-agent roles.
- Messages: ralph emit routes delegation and result events between the coordinator and named hats.
- Cross harness: Per-hat backend selection can route specialized work to different supported coding-agent CLIs.
- Orchestration owner: The coordinator prompt, event tools and hat dispatch belong to Ralph; provider-native subagents are separate.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: results_return, activation, authentication, live_progress, retained_results, followup, invocation.
-
ralph-orchestrator: crates/ralph-core/src/hatless_ralph.rs
Finding: The product always supplies a Hatless Ralph coordinator role. Its shipped prompt instructs that coordinator to delegate through ralph emit events to named specialized hats, and event publishing starts a fresh iteration with clear context. Hats can select distinct coding-agent backends, publish results/events back into the product event loop and retain task/event state. This is product-supplied coordination, not merely display of provider-native subagents.
Native issue tracking: Yes cross-checked
Native issue tracking
Typed value: Yes.
Ralph owns persistent runtime task records with ready, close and fail operations; a full issue backlog workflow is not established.
- Create: ralph tools task add.
- Filter: ready lists unblocked tasks.
- Durable states: Task records can be closed or failed.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: CLI documents bounded iterations, headless execution, recording, continuation, loop logs/diff/rebase/resume, and memory/task operations.
Unattended triggers: Yes
Unattended triggers
Typed value: Yes.
The alpha legacy Node API can start agent work from externally created unblocked tasks through its owned dispatcher, without a human initiating each execution.
- Events: POST /api/v1/tasks auto-enqueues unblocked work unless autoExecute is false; the owned dispatcher starts Ralph.
- Scheduler location: The dispatcher runs in the self-hosted alpha legacy Node web backend.
- Client independence: Dispatch is backend-owned rather than driven by a connected browser.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: schedules, recurring_tasks, completion_conditions, overlaps, retries.
-
ralph-orchestrator: backend/ralph-web-server/src/api/rest.ts
Finding: The alpha legacy Node REST API is explicitly for external consumers. Creating an unblocked task auto-enqueues it unless autoExecute is false, and the product-owned Dispatcher executes it through RalphTaskHandler without a human click for each run. The backend service must remain running; no cron-schedule claim is established.
Shared prompting: Yes
Shared prompting
Typed value: Yes.
The Telegram integration can route instructions from multiple humans reaching the bot into the same loop as human.guidance or human.response events.
- Coprompting: The public Telegram polling/handler path accepts messages into the same loop without a single-sender identity restriction.
- Attribution: Events retain guidance/response content and loop routing; distinct human attribution is not established.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: visibility, discussion, comments, presence, ordering, conflicts, permissions, plan_restrictions, owner_online.
-
ralph-orchestrator: crates/ralph-telegram/src/service.rs
Finding: The Telegram integration routes incoming human messages to the selected loop. The polling service passes message text and chat ID to the handler, which appends human.guidance or human.response events to that loop; messages are not restricted to one sender identity in the inspected handler path. Distinct humans can send messages from their separate Telegram accounts (including a shared group chat) to steer the same loop; they do not share an ADE owner bearer credential. Per-human attribution and team permissions are not supplied by this path.
Team roles: No
Team roles
Typed value: No.
The inspected Ralph runtime has agent hat roles and local/API control, without named human workspace roles or enterprise SSO.
- Organization roles: Agent hats are operational roles; no named human organization-role permission layer is implemented in the inspected runtime.
- Sso: No enterprise SAML/OIDC SSO path exists in the inspected runtime; provider and Telegram authentication are separate.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: project_roles, task_roles, membership, provisioning, unauthorized_access, revocation, plan_scope.
-
ralph-orchestrator: crates/ralph-cli/src/loops.rs
Finding: Bounded inspection of the native loop and alpha web runtime found installed host CLI processes and Git-worktree separation, without product-managed container/VM provisioning, enterprise human SSO or named human team permissions. Hat roles are agent operational roles. publish-review pushes a branch and writes a Markdown handoff; it does not create or manage a pull request.
SSO: No
SSO
Typed value: No.
The inspected Ralph runtime has agent hat roles and local/API control, without named human workspace roles or enterprise SSO.
- Organization roles: Agent hats are operational roles; no named human organization-role permission layer is implemented in the inspected runtime.
- Sso: No enterprise SAML/OIDC SSO path exists in the inspected runtime; provider and Telegram authentication are separate.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: project_roles, task_roles, membership, provisioning, unauthorized_access, revocation, plan_scope.
-
ralph-orchestrator: crates/ralph-cli/src/loops.rs
Finding: Bounded inspection of the native loop and alpha web runtime found installed host CLI processes and Git-worktree separation, without product-managed container/VM provisioning, enterprise human SSO or named human team permissions. Hat roles are agent operational roles. publish-review pushes a branch and writes a Markdown handoff; it does not create or manage a pull request.
Pull request workflow: No
Pull request workflow
Typed value: No.
Ralph integrates worktree diff, branch publish/rebase and merge operations; publish-review writes a Markdown handoff and pushes the branch without creating a pull request.
- Pull requests: The native publish-review implementation uses Git branch publication and a handoff file without a PR creation/management operation.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: branches, commits, comments, ci_response, product_state.
-
ralph-orchestrator: crates/ralph-cli/src/loops.rs
Finding: Bounded inspection of the native loop and alpha web runtime found installed host CLI processes and Git-worktree separation, without product-managed container/VM provisioning, enterprise human SSO or named human team permissions. Hat roles are agent operational roles. publish-review pushes a branch and writes a Markdown handoff; it does not create or manage a pull request.
Review interface: Yes
Review interface
Typed value: Yes.
Planning documents and branch diffs can be retained, and publish-review writes a Markdown handoff.
- Diffs: loops diff compares to merge base.
- Documents: Generated requirements/design/implementation plan.
- Persistence: publish-review writes .ralph/reviews/<id>.md.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
docs/advanced/parallel-loops.md
Finding: Concurrent loops have worktrees, separate events/tasks and shared memories. Completed work can enter a merge queue or publish remote review branches; failed merges need review.
Product license: Apache-2.0: No. MIT cross-checked
Product license: Apache-2.0
Typed value: No. MIT.
Ralph application source is MIT licensed.
- Client license: MIT.
- Source visibility: Public application repository.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: The repository grants the application source under MIT.
Product license: MIT: Yes. MIT cross-checked
Product license: MIT
Typed value: Yes. MIT.
Ralph application source is MIT licensed.
- Client license: MIT.
- Source visibility: Public application repository.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: The repository grants the application source under MIT.
Product license: GPL-3.0: No. MIT cross-checked
Product license: GPL-3.0
Typed value: No. MIT.
Ralph application source is MIT licensed.
- Client license: MIT.
- Source visibility: Public application repository.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: The repository grants the application source under MIT.
Product license: GPL-3.0-or-later: No. MIT cross-checked
Product license: GPL-3.0-or-later
Typed value: No. MIT.
Ralph application source is MIT licensed.
- Client license: MIT.
- Source visibility: Public application repository.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: The repository grants the application source under MIT.
Product license: AGPL-3.0: No. MIT cross-checked
Product license: AGPL-3.0
Typed value: No. MIT.
Ralph application source is MIT licensed.
- Client license: MIT.
- Source visibility: Public application repository.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: The repository grants the application source under MIT.
Product license: AGPL-3.0-or-later: No. MIT cross-checked
Product license: AGPL-3.0-or-later
Typed value: No. MIT.
Ralph application source is MIT licensed.
- Client license: MIT.
- Source visibility: Public application repository.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: The repository grants the application source under MIT.
Product license: Elastic License 2.0: No. MIT cross-checked
Product license: Elastic License 2.0
Typed value: No. MIT.
Ralph application source is MIT licensed.
- Client license: MIT.
- Source visibility: Public application repository.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: The repository grants the application source under MIT.
Product license: Custom terms: No. MIT cross-checked
Product license: Custom terms
Typed value: No. MIT.
Ralph application source is MIT licensed.
- Client license: MIT.
- Source visibility: Public application repository.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: The repository grants the application source under MIT.
Product license: Proprietary: No. MIT cross-checked
Product license: Proprietary
Typed value: No. MIT.
Ralph application source is MIT licensed.
- Client license: MIT.
- Source visibility: Public application repository.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: The repository grants the application source under MIT.
Self-hosting: Yes cross-checked
Self-hosting
Typed value: Yes.
The core Ralph CLI and local web stack can run on user-controlled hardware.
- Self hosting: Install local Ralph with an installed coding CLI and optionally run ralph web.
- Formats: Planning Markdown and JSONL session/event output.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: Ralph offers CLI/TUI loops, an alpha web dashboard, workspace-scoped MCP server, planning documents, backend selection and Telegram intervention.
Telemetry opt-out: Yes
Telemetry opt-out
Typed value: Yes.
Ralph provides opt-in local diagnostic output controlled by RALPH_DIAGNOSTICS; leaving it unset disables those collectors. Coding-agent/provider telemetry is separate.
- Telemetry disclosure: Diagnostics include local JSONL output, trace, hook-run telemetry and performance records.
- Telemetry defaults: The collector is disabled unless RALPH_DIAGNOSTICS is exactly 1.
- Telemetry controls: Unset RALPH_DIAGNOSTICS or set it to 0 to disable the local diagnostic collectors.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: code_data, prompts, credentials, logs, artifacts, retention, deletion, training, residency, subprocessors, consent_prompt, provider_separation.
-
ralph-orchestrator: crates/ralph-core/src/diagnostics/mod.rs
Finding: Ralph diagnostic collection is opt-in through RALPH_DIAGNOSTICS=1. When unset or another value, the collector creates no diagnostic directory or loggers. It controls local agent output, traces, hook-run telemetry and performance JSONL files; provider telemetry is separate.
Free access: Yes cross-checked
Free access
Typed value: Yes.
Ralph Orchestrator is a free MIT download from npm, Cargo or the GitHub Releases installer, with no paid plan shown; optional sponsorship is a donation. Agent and model costs are paid to their providers.
- Ongoing free: The ralph CLI is a free MIT download from npm, Cargo or the release installer.
- Self host cost: Runs on the user's machine with no Ralph fee shown; agent provider charges remain separate.
- Paid only: Not paid-only: the application installs free of charge from public channels.
- Free scenarios, usage caps and card requirements for the underlying agents were not checked. No installed-product test was run.
-
Finding: The repository is MIT licensed, copyright Ralph Orchestrator Contributors.
-
Ralph Orchestrator README: Installation
Finding: Ralph installs free from npm (@ralph-orchestrator/ralph-cli), a GitHub Releases installer script or cargo install ralph-cli; the README names no price, account or paid plan. FUNDING.md asks only for optional GitHub Sponsors donations.
Starting price: Free: Yes. Free cross-checked
Starting price: Free
Typed value: Yes. Free.
Ralph Orchestrator is a free MIT download from npm, Cargo or the GitHub Releases installer, with no paid plan shown; optional sponsorship is a donation. Agent and model costs are paid to their providers.
- Ongoing free: The ralph CLI is a free MIT download from npm, Cargo or the release installer.
- Self host cost: Runs on the user's machine with no Ralph fee shown; agent provider charges remain separate.
- Paid only: Not paid-only: the application installs free of charge from public channels.
- Free scenarios, usage caps and card requirements for the underlying agents were not checked. No installed-product test was run.
-
Finding: The repository is MIT licensed, copyright Ralph Orchestrator Contributors.
-
Ralph Orchestrator README: Installation
Finding: Ralph installs free from npm (@ralph-orchestrator/ralph-cli), a GitHub Releases installer script or cargo install ralph-cli; the README names no price, account or paid plan. FUNDING.md asks only for optional GitHub Sponsors donations.
Starting price: Up to $20/month: No. Free cross-checked
Starting price: Up to $20/month
Typed value: No. Free.
Ralph Orchestrator is a free MIT download from npm, Cargo or the GitHub Releases installer, with no paid plan shown; optional sponsorship is a donation. Agent and model costs are paid to their providers.
- Ongoing free: The ralph CLI is a free MIT download from npm, Cargo or the release installer.
- Self host cost: Runs on the user's machine with no Ralph fee shown; agent provider charges remain separate.
- Paid only: Not paid-only: the application installs free of charge from public channels.
- Free scenarios, usage caps and card requirements for the underlying agents were not checked. No installed-product test was run.
-
Finding: The repository is MIT licensed, copyright Ralph Orchestrator Contributors.
-
Ralph Orchestrator README: Installation
Finding: Ralph installs free from npm (@ralph-orchestrator/ralph-cli), a GitHub Releases installer script or cargo install ralph-cli; the README names no price, account or paid plan. FUNDING.md asks only for optional GitHub Sponsors donations.
Starting price: $21–40/month: No. Free cross-checked
Starting price: $21–40/month
Typed value: No. Free.
Ralph Orchestrator is a free MIT download from npm, Cargo or the GitHub Releases installer, with no paid plan shown; optional sponsorship is a donation. Agent and model costs are paid to their providers.
- Ongoing free: The ralph CLI is a free MIT download from npm, Cargo or the release installer.
- Self host cost: Runs on the user's machine with no Ralph fee shown; agent provider charges remain separate.
- Paid only: Not paid-only: the application installs free of charge from public channels.
- Free scenarios, usage caps and card requirements for the underlying agents were not checked. No installed-product test was run.
-
Finding: The repository is MIT licensed, copyright Ralph Orchestrator Contributors.
-
Ralph Orchestrator README: Installation
Finding: Ralph installs free from npm (@ralph-orchestrator/ralph-cli), a GitHub Releases installer script or cargo install ralph-cli; the README names no price, account or paid plan. FUNDING.md asks only for optional GitHub Sponsors donations.
Starting price: $41–100/month: No. Free cross-checked
Starting price: $41–100/month
Typed value: No. Free.
Ralph Orchestrator is a free MIT download from npm, Cargo or the GitHub Releases installer, with no paid plan shown; optional sponsorship is a donation. Agent and model costs are paid to their providers.
- Ongoing free: The ralph CLI is a free MIT download from npm, Cargo or the release installer.
- Self host cost: Runs on the user's machine with no Ralph fee shown; agent provider charges remain separate.
- Paid only: Not paid-only: the application installs free of charge from public channels.
- Free scenarios, usage caps and card requirements for the underlying agents were not checked. No installed-product test was run.
-
Finding: The repository is MIT licensed, copyright Ralph Orchestrator Contributors.
-
Ralph Orchestrator README: Installation
Finding: Ralph installs free from npm (@ralph-orchestrator/ralph-cli), a GitHub Releases installer script or cargo install ralph-cli; the README names no price, account or paid plan. FUNDING.md asks only for optional GitHub Sponsors donations.
Starting price: Over $100/month: No. Free cross-checked
Starting price: Over $100/month
Typed value: No. Free.
Ralph Orchestrator is a free MIT download from npm, Cargo or the GitHub Releases installer, with no paid plan shown; optional sponsorship is a donation. Agent and model costs are paid to their providers.
- Ongoing free: The ralph CLI is a free MIT download from npm, Cargo or the release installer.
- Self host cost: Runs on the user's machine with no Ralph fee shown; agent provider charges remain separate.
- Paid only: Not paid-only: the application installs free of charge from public channels.
- Free scenarios, usage caps and card requirements for the underlying agents were not checked. No installed-product test was run.
-
Finding: The repository is MIT licensed, copyright Ralph Orchestrator Contributors.
-
Ralph Orchestrator README: Installation
Finding: Ralph installs free from npm (@ralph-orchestrator/ralph-cli), a GitHub Releases installer script or cargo install ralph-cli; the README names no price, account or paid plan. FUNDING.md asks only for optional GitHub Sponsors donations.
Starting price: Contact for pricing: No. Free cross-checked
Starting price: Contact for pricing
Typed value: No. Free.
Ralph Orchestrator is a free MIT download from npm, Cargo or the GitHub Releases installer, with no paid plan shown; optional sponsorship is a donation. Agent and model costs are paid to their providers.
- Ongoing free: The ralph CLI is a free MIT download from npm, Cargo or the release installer.
- Self host cost: Runs on the user's machine with no Ralph fee shown; agent provider charges remain separate.
- Paid only: Not paid-only: the application installs free of charge from public channels.
- Free scenarios, usage caps and card requirements for the underlying agents were not checked. No installed-product test was run.
-
Finding: The repository is MIT licensed, copyright Ralph Orchestrator Contributors.
-
Ralph Orchestrator README: Installation
Finding: Ralph installs free from npm (@ralph-orchestrator/ralph-cli), a GitHub Releases installer script or cargo install ralph-cli; the README names no price, account or paid plan. FUNDING.md asks only for optional GitHub Sponsors donations.
Pricing model: Free, no paid plan: Yes
Pricing model: Free, no paid plan
Typed value: Yes.
Ralph is free MIT software without a published paid Ralph plan. Its supported backend setup accepts the user provider API keys or native CLI logins, billed separately.
- Model cost: Backend setup documents user provider API keys and native CLI authentication; these provider bills are separate from Ralph.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: currency, interval, seats, seat_minimum, workspace_fees, included_usage, credits, trial, overages, taxes, compute_cost.
-
Finding: Says the tool is MIT licensed and runs on a backend agent you choose, such as Claude. It mentions no paid plan or price.
-
mikeyobrien/ralph-orchestrator LICENSE (MIT)
Finding: The MIT License lets anyone obtain, use, copy and modify the software free of charge.
Pricing model: Free plan: No
Pricing model: Free plan
Typed value: No.
Ralph is free MIT software without a published paid Ralph plan. Its supported backend setup accepts the user provider API keys or native CLI logins, billed separately.
- Model cost: Backend setup documents user provider API keys and native CLI authentication; these provider bills are separate from Ralph.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: currency, interval, seats, seat_minimum, workspace_fees, included_usage, credits, trial, overages, taxes, compute_cost.
-
Finding: Says the tool is MIT licensed and runs on a backend agent you choose, such as Claude. It mentions no paid plan or price.
-
mikeyobrien/ralph-orchestrator LICENSE (MIT)
Finding: The MIT License lets anyone obtain, use, copy and modify the software free of charge.
Pricing model: Subscription: No
Pricing model: Subscription
Typed value: No.
Ralph is free MIT software without a published paid Ralph plan. Its supported backend setup accepts the user provider API keys or native CLI logins, billed separately.
- Model cost: Backend setup documents user provider API keys and native CLI authentication; these provider bills are separate from Ralph.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: currency, interval, seats, seat_minimum, workspace_fees, included_usage, credits, trial, overages, taxes, compute_cost.
-
Finding: Says the tool is MIT licensed and runs on a backend agent you choose, such as Claude. It mentions no paid plan or price.
-
mikeyobrien/ralph-orchestrator LICENSE (MIT)
Finding: The MIT License lets anyone obtain, use, copy and modify the software free of charge.
Pricing model: Per seat: No
Pricing model: Per seat
Typed value: No.
Ralph is free MIT software without a published paid Ralph plan. Its supported backend setup accepts the user provider API keys or native CLI logins, billed separately.
- Model cost: Backend setup documents user provider API keys and native CLI authentication; these provider bills are separate from Ralph.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: currency, interval, seats, seat_minimum, workspace_fees, included_usage, credits, trial, overages, taxes, compute_cost.
-
Finding: Says the tool is MIT licensed and runs on a backend agent you choose, such as Claude. It mentions no paid plan or price.
-
mikeyobrien/ralph-orchestrator LICENSE (MIT)
Finding: The MIT License lets anyone obtain, use, copy and modify the software free of charge.
Pricing model: Usage-based: No
Pricing model: Usage-based
Typed value: No.
Ralph is free MIT software without a published paid Ralph plan. Its supported backend setup accepts the user provider API keys or native CLI logins, billed separately.
- Model cost: Backend setup documents user provider API keys and native CLI authentication; these provider bills are separate from Ralph.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: currency, interval, seats, seat_minimum, workspace_fees, included_usage, credits, trial, overages, taxes, compute_cost.
-
Finding: Says the tool is MIT licensed and runs on a backend agent you choose, such as Claude. It mentions no paid plan or price.
-
mikeyobrien/ralph-orchestrator LICENSE (MIT)
Finding: The MIT License lets anyone obtain, use, copy and modify the software free of charge.
Pricing model: Per machine or compute: No
Pricing model: Per machine or compute
Typed value: No.
Ralph is free MIT software without a published paid Ralph plan. Its supported backend setup accepts the user provider API keys or native CLI logins, billed separately.
- Model cost: Backend setup documents user provider API keys and native CLI authentication; these provider bills are separate from Ralph.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: currency, interval, seats, seat_minimum, workspace_fees, included_usage, credits, trial, overages, taxes, compute_cost.
-
Finding: Says the tool is MIT licensed and runs on a backend agent you choose, such as Claude. It mentions no paid plan or price.
-
mikeyobrien/ralph-orchestrator LICENSE (MIT)
Finding: The MIT License lets anyone obtain, use, copy and modify the software free of charge.
Pricing model: Bring your own key: Yes
Pricing model: Bring your own key
Typed value: Yes.
Ralph is free MIT software without a published paid Ralph plan. Its supported backend setup accepts the user provider API keys or native CLI logins, billed separately.
- Model cost: Backend setup documents user provider API keys and native CLI authentication; these provider bills are separate from Ralph.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: currency, interval, seats, seat_minimum, workspace_fees, included_usage, credits, trial, overages, taxes, compute_cost.
-
ralph-orchestrator: docs/guide/backends.md
Finding: The first-party backend setup explicitly accepts user provider API credentials, including ANTHROPIC_API_KEY and GEMINI_API_KEY, as well as native CLI logins. Model usage is billed by the selected provider, separately from the free Ralph software.
Pricing model: One-time purchase: No
Pricing model: One-time purchase
Typed value: No.
Ralph is free MIT software without a published paid Ralph plan. Its supported backend setup accepts the user provider API keys or native CLI logins, billed separately.
- Model cost: Backend setup documents user provider API keys and native CLI authentication; these provider bills are separate from Ralph.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: currency, interval, seats, seat_minimum, workspace_fees, included_usage, credits, trial, overages, taxes, compute_cost.
-
Finding: Says the tool is MIT licensed and runs on a backend agent you choose, such as Claude. It mentions no paid plan or price.
-
mikeyobrien/ralph-orchestrator LICENSE (MIT)
Finding: The MIT License lets anyone obtain, use, copy and modify the software free of charge.
Keeps going with laptop closed: Yes
Keeps going with laptop closed
Typed value: Yes.
Ralph normally invokes installed agent CLIs on the current host. Its documented alpha legacy Node web mode also supplies an operator-hosted network server with detached agent processes independent of browser clients.
- Byo remote: The alpha legacy Node backend binds a network host and runs the installed Ralph process on that operator host.
- Managed cloud: The inspected public runtime modes run installed CLIs on operator machines, without a Ralph-operated compute service.
- Client disconnect: ProcessSupervisor starts detached/unref processes with persisted PID/status/logs; browser disconnect does not own their lifetime.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: self_hosted, hybrid, provisioning, payer, resources, region, expiry, other_device_continuation.
-
ralph-orchestrator: backend/ralph-web-server/src/runner/ProcessSupervisor.ts
Finding: The documented alpha web command can enable the legacy Node backend. That backend binds an operator-selected network host, starts detached native Ralph processes, persists PID/status/logs and can reconnect after server restarts. Agent work is owned by that server process tree rather than a browser connection. This is a self-hosted alpha mode; no managed Ralph cloud is supplied.
Open-source license: Yes. MIT cross-checked
Open-source license
Typed value: Yes. MIT.
Ralph application source is MIT licensed.
- Client license: MIT.
- Source visibility: Public application repository.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: The repository grants the application source under MIT.
Any desktop app: Yes
Any desktop app
Typed value: Yes.
Ralph supplies a native CLI/TUI on macOS, Linux and Windows plus an alpha browser dashboard and Telegram integration. It has no product-owned native phone app.
- Desktop os: The first-party installation OS list is macOS, Linux and Windows.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: mobile_browser, editor_extensions, notifications, cross_device_continuity.
-
ralph-orchestrator: docs/installation.md
Finding: The first-party installation guide explicitly supports macOS, Linux and Windows for the native Ralph CLI. These are terminal clients rather than desktop GUI applications.
All public findings
Findings may summarize a source. They are not presented as verbatim statements.
ralph-orchestrator:ACC-01: Ralph supplies a native CLI/TUI on macOS, Linux and Windows plus an alpha browser dashboard and Telegram integration. It has no product-owned native phone app.
ralph-orchestrator:ACC-01
Ralph supplies a native CLI/TUI on macOS, Linux and Windows plus an alpha browser dashboard and Telegram integration. It has no product-owned native phone app.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: mobile_browser, editor_extensions, notifications, cross_device_continuity.
-
Finding: Ralph offers CLI/TUI loops, an alpha web dashboard, workspace-scoped MCP server, planning documents, backend selection and Telegram intervention.
-
ralph-orchestrator: docs/installation.md
Finding: The first-party installation guide explicitly supports macOS, Linux and Windows for the native Ralph CLI. These are terminal clients rather than desktop GUI applications.
-
ralph-orchestrator: crates/ralph-cli/src/loops.rs
Finding: Bounded inspection of the native loop and alpha web runtime found installed host CLI processes and Git-worktree separation, without product-managed container/VM provisioning, enterprise human SSO or named human team permissions. Hat roles are agent operational roles. publish-review pushes a branch and writes a Markdown handoff; it does not create or manage a pull request.
ralph-orchestrator:ACC-02: Eleven named CLI backends and custom commands are documented, with different backends selectable per hat. cross-checked
ralph-orchestrator:ACC-02
Eleven named CLI backends and custom commands are documented, with different backends selectable per hat.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: Names Claude Code, Codex, Gemini CLI, OpenCode and Pi among eleven backends, documents native Claude login and API keys, and per-hat backend overrides.
ralph-orchestrator:ACC-03: Backend setup supports native Claude login and provider API credentials. Costs and account rights belong to the selected agent. cross-checked
ralph-orchestrator:ACC-03
Backend setup supports native Claude login and provider API credentials. Costs and account rights belong to the selected agent.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: Names Claude Code, Codex, Gemini CLI, OpenCode and Pi among eleven backends, documents native Claude login and API keys, and per-hat backend overrides.
ralph-orchestrator:ACC-04: Install Ralph and a supported agent CLI, initialize a backend, then plan or run. Dashboard setup additionally needs Rust and Node. cross-checked
ralph-orchestrator:ACC-04
Install Ralph and a supported agent CLI, initialize a backend, then plan or run. Dashboard setup additionally needs Rust and Node.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: Ralph offers CLI/TUI loops, an alpha web dashboard, workspace-scoped MCP server, planning documents, backend selection and Telegram intervention.
ralph-orchestrator:ACC-05: Ralph provides its CLI and a stdio MCP server scoped to one workspace. cross-checked
ralph-orchestrator:ACC-05
Ralph provides its CLI and a stdio MCP server scoped to one workspace.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: Ralph offers CLI/TUI loops, an alpha web dashboard, workspace-scoped MCP server, planning documents, backend selection and Telegram intervention.
-
Finding: CLI documents bounded iterations, headless execution, recording, continuation, loop logs/diff/rebase/resume, and memory/task operations.
ralph-orchestrator:PLAN-01: Runtime tasks can be added, listed and inspected through product commands. cross-checked
ralph-orchestrator:PLAN-01
Runtime tasks can be added, listed and inspected through product commands.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: CLI documents bounded iterations, headless execution, recording, continuation, loop logs/diff/rebase/resume, and memory/task operations.
ralph-orchestrator:PLAN-02: Interactive planning writes requirements, design and implementation-plan Markdown under .ralph/specs. cross-checked
ralph-orchestrator:PLAN-02
Interactive planning writes requirements, design and implementation-plan Markdown under .ralph/specs.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: Ralph offers CLI/TUI loops, an alpha web dashboard, workspace-scoped MCP server, planning documents, backend selection and Telegram intervention.
ralph-orchestrator:PLAN-04: Persistent Markdown memory is shared across parallel loops; tools can search, add and delete entries. cross-checked
ralph-orchestrator:PLAN-04
Persistent Markdown memory is shared across parallel loops; tools can search, add and delete entries.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: CLI documents bounded iterations, headless execution, recording, continuation, loop logs/diff/rebase/resume, and memory/task operations.
-
docs/advanced/parallel-loops.md
Finding: Concurrent loops have worktrees, separate events/tasks and shared memories. Completed work can enter a merge queue or publish remote review branches; failed merges need review.
-
docs/advanced/memory-system.md
Finding: Memories persist across sessions in .agent/memories.md and include codebase patterns, decisions and recurring solutions.
ralph-orchestrator:PLAN-06: Ralph owns persistent runtime task records with ready, close and fail operations; a full issue backlog workflow is not established. cross-checked
ralph-orchestrator:PLAN-06
Ralph owns persistent runtime task records with ready, close and fail operations; a full issue backlog workflow is not established.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: CLI documents bounded iterations, headless execution, recording, continuation, loop logs/diff/rebase/resume, and memory/task operations.
ralph-orchestrator:PLAN-07: Runtime task commands are exposed to agents as tools. cross-checked
ralph-orchestrator:PLAN-07
Runtime task commands are exposed to agents as tools.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: CLI documents bounded iterations, headless execution, recording, continuation, loop logs/diff/rebase/resume, and memory/task operations.
ralph-orchestrator:PLAN-08: Planning creates persistent requirements and design files; approval and drift gates remain unestablished. cross-checked
ralph-orchestrator:PLAN-08
Planning creates persistent requirements and design files; approval and drift gates remain unestablished.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: Ralph offers CLI/TUI loops, an alpha web dashboard, workspace-scoped MCP server, planning documents, backend selection and Telegram intervention.
ralph-orchestrator:COORD-01: Additional concurrent loops run in separate Git worktrees. cross-checked
ralph-orchestrator:COORD-01
Additional concurrent loops run in separate Git worktrees.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
docs/advanced/parallel-loops.md
Finding: Concurrent loops have worktrees, separate events/tasks and shared memories. Completed work can enter a merge queue or publish remote review branches; failed merges need review.
ralph-orchestrator:COORD-03: The shipped Hatless Ralph coordinator delegates work through named hat events, receives their event results and can route hats to different coding-agent backends with fresh iteration context.
ralph-orchestrator:COORD-03
The shipped Hatless Ralph coordinator delegates work through named hat events, receives their event results and can route hats to different coding-agent backends with fresh iteration context.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: results_return, activation, authentication, live_progress, retained_results, followup, invocation.
-
Finding: Ralph offers CLI/TUI loops, an alpha web dashboard, workspace-scoped MCP server, planning documents, backend selection and Telegram intervention.
-
Finding: Names Claude Code, Codex, Gemini CLI, OpenCode and Pi among eleven backends, documents native Claude login and API keys, and per-hat backend overrides.
-
ralph-orchestrator: crates/ralph-core/src/hatless_ralph.rs
Finding: The product always supplies a Hatless Ralph coordinator role. Its shipped prompt instructs that coordinator to delegate through ralph emit events to named specialized hats, and event publishing starts a fresh iteration with clear context. Hats can select distinct coding-agent backends, publish results/events back into the product event loop and retain task/event state. This is product-supplied coordination, not merely display of provider-native subagents.
ralph-orchestrator:COORD-04: The alpha legacy Node API can start agent work from externally created unblocked tasks through its owned dispatcher, without a human initiating each execution.
ralph-orchestrator:COORD-04
The alpha legacy Node API can start agent work from externally created unblocked tasks through its owned dispatcher, without a human initiating each execution.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: schedules, recurring_tasks, completion_conditions, overlaps, retries.
-
ralph-orchestrator: backend/ralph-web-server/src/api/rest.ts
Finding: The alpha legacy Node REST API is explicitly for external consumers. Creating an unblocked task auto-enqueues it unless autoExecute is false, and the product-owned Dispatcher executes it through RalphTaskHandler without a human click for each run. The backend service must remain running; no cron-schedule claim is established.
-
ralph-orchestrator: public preview availability
Finding: The first-party README explicitly labels the web dashboard Alpha, warns of breaking changes, and documents ralph web --legacy-node-api as the opt-in deprecated Node backend. The unattended task-dispatch path and operator-server mode inspected in that backend are publicly enableable experimental paths.
ralph-orchestrator:COORD-05: Loops can be stopped/resumed; Telegram questions block until answered and proactive messages steer a run. cross-checked
ralph-orchestrator:COORD-05
Loops can be stopped/resumed; Telegram questions block until answered and proactive messages steer a run.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: Ralph offers CLI/TUI loops, an alpha web dashboard, workspace-scoped MCP server, planning documents, backend selection and Telegram intervention.
-
Finding: CLI documents bounded iterations, headless execution, recording, continuation, loop logs/diff/rebase/resume, and memory/task operations.
ralph-orchestrator:COORD-07: Five built-in workflows and direct prompts are documented.
ralph-orchestrator:COORD-07
Five built-in workflows and direct prompts are documented.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: Ralph offers CLI/TUI loops, an alpha web dashboard, workspace-scoped MCP server, planning documents, backend selection and Telegram intervention.
-
Finding: Names Claude Code, Codex, Gemini CLI, OpenCode and Pi among eleven backends, documents native Claude login and API keys, and per-hat backend overrides.
ralph-orchestrator:RUN-01: Ralph normally invokes installed agent CLIs on the current host. Its documented alpha legacy Node web mode also supplies an operator-hosted network server with detached agent processes independent of browser clients.
ralph-orchestrator:RUN-01
Ralph normally invokes installed agent CLIs on the current host. Its documented alpha legacy Node web mode also supplies an operator-hosted network server with detached agent processes independent of browser clients.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: self_hosted, hybrid, provisioning, payer, resources, region, expiry, other_device_continuation.
-
Finding: Ralph offers CLI/TUI loops, an alpha web dashboard, workspace-scoped MCP server, planning documents, backend selection and Telegram intervention.
-
ralph-orchestrator: backend/ralph-web-server/src/runner/ProcessSupervisor.ts
Finding: The documented alpha web command can enable the legacy Node backend. That backend binds an operator-selected network host, starts detached native Ralph processes, persists PID/status/logs and can reconnect after server restarts. Agent work is owned by that server process tree rather than a browser connection. This is a self-hosted alpha mode; no managed Ralph cloud is supplied.
-
ralph-orchestrator: crates/ralph-cli/src/loops.rs
Finding: Bounded inspection of the native loop and alpha web runtime found installed host CLI processes and Git-worktree separation, without product-managed container/VM provisioning, enterprise human SSO or named human team permissions. Hat roles are agent operational roles. publish-review pushes a branch and writes a Markdown handoff; it does not create or manage a pull request.
-
ralph-orchestrator: public preview availability
Finding: The first-party README explicitly labels the web dashboard Alpha, warns of breaking changes, and documents ralph web --legacy-node-api as the opt-in deprecated Node backend. The unattended task-dispatch path and operator-server mode inspected in that backend are publicly enableable experimental paths.
ralph-orchestrator:RUN-02: Ralph separates parallel loop checkouts with Git worktrees and runs native host CLI processes; it provides no built-in container or VM isolation.
ralph-orchestrator:RUN-02
Ralph separates parallel loop checkouts with Git worktrees and runs native host CLI processes; it provides no built-in container or VM isolation.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: checkout, branch, os_sandbox, filesystem, process, network, secrets, security_boundary.
-
docs/advanced/parallel-loops.md
Finding: Concurrent loops have worktrees, separate events/tasks and shared memories. Completed work can enter a merge queue or publish remote review branches; failed merges need review.
-
ralph-orchestrator: crates/ralph-cli/src/loops.rs
Finding: Bounded inspection of the native loop and alpha web runtime found installed host CLI processes and Git-worktree separation, without product-managed container/VM provisioning, enterprise human SSO or named human team permissions. Hat roles are agent operational roles. publish-review pushes a branch and writes a Markdown handoff; it does not create or manage a pull request.
ralph-orchestrator:RUN-03: Existing loop state can be continued and suspended loops resumed; no crash recovery experiment was run. cross-checked
ralph-orchestrator:RUN-03
Existing loop state can be continued and suspended loops resumed; no crash recovery experiment was run.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: CLI documents bounded iterations, headless execution, recording, continuation, loop logs/diff/rebase/resume, and memory/task operations.
-
docs/advanced/parallel-loops.md
Finding: Concurrent loops have worktrees, separate events/tasks and shared memories. Completed work can enter a merge queue or publish remote review branches; failed merges need review.
ralph-orchestrator:RUN-05: Current configuration bounds iterations and total runtime, with adapter inactivity timeouts and per-hat activation caps. cross-checked
ralph-orchestrator:RUN-05
Current configuration bounds iterations and total runtime, with adapter inactivity timeouts and per-hat activation caps.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: Configuration defines iteration/runtime limits, inactivity timeouts, hook timeouts and per-hat activation limits.
ralph-orchestrator:RUN-06: Loop logs and event history expose operational state and JSONL export. cross-checked
ralph-orchestrator:RUN-06
Loop logs and event history expose operational state and JSONL export.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: CLI documents bounded iterations, headless execution, recording, continuation, loop logs/diff/rebase/resume, and memory/task operations.
-
docs/advanced/parallel-loops.md
Finding: Concurrent loops have worktrees, separate events/tasks and shared memories. Completed work can enter a merge queue or publish remote review branches; failed merges need review.
ralph-orchestrator:TEAM-01: The Telegram integration can route instructions from multiple humans reaching the bot into the same loop as human.guidance or human.response events.
ralph-orchestrator:TEAM-01
The Telegram integration can route instructions from multiple humans reaching the bot into the same loop as human.guidance or human.response events.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: visibility, discussion, comments, presence, ordering, conflicts, permissions, plan_restrictions, owner_online.
-
ralph-orchestrator: crates/ralph-telegram/src/service.rs
Finding: The Telegram integration routes incoming human messages to the selected loop. The polling service passes message text and chat ID to the handler, which appends human.guidance or human.response events to that loop; messages are not restricted to one sender identity in the inspected handler path. Distinct humans can send messages from their separate Telegram accounts (including a shared group chat) to steer the same loop; they do not share an ADE owner bearer credential. Per-human attribution and team permissions are not supplied by this path.
ralph-orchestrator:TEAM-02: The inspected Ralph runtime has agent hat roles and local/API control, without named human workspace roles or enterprise SSO.
ralph-orchestrator:TEAM-02
The inspected Ralph runtime has agent hat roles and local/API control, without named human workspace roles or enterprise SSO.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: project_roles, task_roles, membership, provisioning, unauthorized_access, revocation, plan_scope.
-
ralph-orchestrator: crates/ralph-cli/src/loops.rs
Finding: Bounded inspection of the native loop and alpha web runtime found installed host CLI processes and Git-worktree separation, without product-managed container/VM provisioning, enterprise human SSO or named human team permissions. Hat roles are agent operational roles. publish-review pushes a branch and writes a Markdown handoff; it does not create or manage a pull request.
ralph-orchestrator:SHIP-01: Planning documents and branch diffs can be retained, and publish-review writes a Markdown handoff. cross-checked
ralph-orchestrator:SHIP-01
Planning documents and branch diffs can be retained, and publish-review writes a Markdown handoff.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: Ralph offers CLI/TUI loops, an alpha web dashboard, workspace-scoped MCP server, planning documents, backend selection and Telegram intervention.
-
docs/advanced/parallel-loops.md
Finding: Concurrent loops have worktrees, separate events/tasks and shared memories. Completed work can enter a merge queue or publish remote review branches; failed merges need review.
ralph-orchestrator:SHIP-02: Backpressure workflows request test, lint and typecheck evidence; instruction examples do not prove that an external verifier enforced it. cross-checked
ralph-orchestrator:SHIP-02
Backpressure workflows request test, lint and typecheck evidence; instruction examples do not prove that an external verifier enforced it.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: Documents test/lint/typecheck evidence and reviewer hats, but warns that emitted evidence can be fake. Instructional examples are not proof of enforcement.
ralph-orchestrator:SHIP-03: Ralph integrates worktree diff, branch publish/rebase and merge operations; publish-review writes a Markdown handoff and pushes the branch without creating a pull request.
ralph-orchestrator:SHIP-03
Ralph integrates worktree diff, branch publish/rebase and merge operations; publish-review writes a Markdown handoff and pushes the branch without creating a pull request.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: branches, commits, comments, ci_response, product_state.
-
docs/advanced/parallel-loops.md
Finding: Concurrent loops have worktrees, separate events/tasks and shared memories. Completed work can enter a merge queue or publish remote review branches; failed merges need review.
-
ralph-orchestrator: crates/ralph-cli/src/loops.rs
Finding: Bounded inspection of the native loop and alpha web runtime found installed host CLI processes and Git-worktree separation, without product-managed container/VM provisioning, enterprise human SSO or named human team permissions. Hat roles are agent operational roles. publish-review pushes a branch and writes a Markdown handoff; it does not create or manage a pull request.
ralph-orchestrator:SHIP-04: Optional auto-merge uses merger, resolver and tester hats. Exact-revision authorization is unestablished. cross-checked
ralph-orchestrator:SHIP-04
Optional auto-merge uses merger, resolver and tester hats. Exact-revision authorization is unestablished.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
docs/advanced/parallel-loops.md
Finding: Concurrent loops have worktrees, separate events/tasks and shared memories. Completed work can enter a merge queue or publish remote review branches; failed merges need review.
ralph-orchestrator:OWN-01: Ralph application source is MIT licensed. cross-checked
ralph-orchestrator:OWN-01
Ralph application source is MIT licensed.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: The repository grants the application source under MIT.
ralph-orchestrator:OWN-02: The core Ralph CLI and local web stack can run on user-controlled hardware. cross-checked
ralph-orchestrator:OWN-02
The core Ralph CLI and local web stack can run on user-controlled hardware.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: Ralph offers CLI/TUI loops, an alpha web dashboard, workspace-scoped MCP server, planning documents, backend selection and Telegram intervention.
-
Finding: CLI documents bounded iterations, headless execution, recording, continuation, loop logs/diff/rebase/resume, and memory/task operations.
ralph-orchestrator:OWN-03: Ralph provides opt-in local diagnostic output controlled by RALPH_DIAGNOSTICS; leaving it unset disables those collectors. Coding-agent/provider telemetry is separate.
ralph-orchestrator:OWN-03
Ralph provides opt-in local diagnostic output controlled by RALPH_DIAGNOSTICS; leaving it unset disables those collectors. Coding-agent/provider telemetry is separate.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: code_data, prompts, credentials, logs, artifacts, retention, deletion, training, residency, subprocessors, consent_prompt, provider_separation.
-
ralph-orchestrator: crates/ralph-core/src/diagnostics/mod.rs
Finding: Ralph diagnostic collection is opt-in through RALPH_DIAGNOSTICS=1. When unset or another value, the collector creates no diagnostic directory or loggers. It controls local agent output, traces, hook-run telemetry and performance JSONL files; provider telemetry is separate.
ralph-orchestrator:OWN-04: Ralph is free MIT software without a published paid Ralph plan. Its supported backend setup accepts the user provider API keys or native CLI logins, billed separately.
ralph-orchestrator:OWN-04
Ralph is free MIT software without a published paid Ralph plan. Its supported backend setup accepts the user provider API keys or native CLI logins, billed separately.
- Documentation and pinned source inspection only; no hands-on scenario was run.
- Other atomic questions remain unestablished: currency, interval, seats, seat_minimum, workspace_fees, included_usage, credits, trial, overages, taxes, compute_cost.
-
Finding: Says the tool is MIT licensed and runs on a backend agent you choose, such as Claude. It mentions no paid plan or price.
-
mikeyobrien/ralph-orchestrator LICENSE (MIT)
Finding: The MIT License lets anyone obtain, use, copy and modify the software free of charge.
-
ralph-orchestrator: docs/guide/backends.md
Finding: The first-party backend setup explicitly accepts user provider API credentials, including ANTHROPIC_API_KEY and GEMINI_API_KEY, as well as native CLI logins. Model usage is billed by the selected provider, separately from the free Ralph software.
ralph-orchestrator:OWN-06: The latest listed release is 2.10.1, published June 23; current README labels the browser dashboard alpha. cross-checked
ralph-orchestrator:OWN-06
The latest listed release is 2.10.1, published June 23; current README labels the browser dashboard alpha.
- Only the named facts are documented. Unanswered atomic questions remain unknown; no execution test was performed.
-
Finding: Ralph offers CLI/TUI loops, an alpha web dashboard, workspace-scoped MCP server, planning documents, backend selection and Telegram intervention.
-
Finding: 2.10.1 - 2026-06-22 was published 2026-06-23. Release notes describe the scoped changes; this is not a hands-on check.
ralph-orchestrator:OWN-08: Ralph Orchestrator is a free MIT download from npm, Cargo or the GitHub Releases installer, with no paid plan shown; optional sponsorship is a donation. Agent and model costs are paid to their providers. cross-checked
ralph-orchestrator:OWN-08
Ralph Orchestrator is a free MIT download from npm, Cargo or the GitHub Releases installer, with no paid plan shown; optional sponsorship is a donation. Agent and model costs are paid to their providers.
- Free scenarios, usage caps and card requirements for the underlying agents were not checked. No installed-product test was run.
-
Finding: The repository is MIT licensed, copyright Ralph Orchestrator Contributors.
-
Ralph Orchestrator README: Installation
Finding: Ralph installs free from npm (@ralph-orchestrator/ralph-cli), a GitHub Releases installer script or cargo install ralph-cli; the README names no price, account or paid plan. FUNDING.md asks only for optional GitHub Sponsors donations.