Happy

Desktop OS: macOS

Typed value: Yes.

Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams. Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop. The first-party repository describes the mobile app as available on iOS, Android and web. This establishes the phone web client, not desktop parity.

• Desktop os: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Mobile apps: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Browser: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Mobile browser: The first-party repository describes the mobile app as available on iOS, Android and web. This establishes the phone web client, not desktop parity.
• Cli: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Task actions: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.
• Cross device continuity: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.

Checked

2026-11-08 · checked 1 week ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Happy Agent v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2), Desktop v0.0.103 (a369b7b0a86a344904a2e171a78e2b0daf0b4be8); targeted first-party pass 2026-11-13; no installed-product test

• The scoped first-party source pass does not establish editor_extensions, notifications. No hands-on scenario was run.

1. Happy: How Happy fits together; Original Happy CLI

   Finding: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.

   Locator

   How Happy fits together; Original Happy CLI

   Retrieved

   2026-11-08

2. Happy: Mobile access

   Finding: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.

   Locator

   Mobile access

   Retrieved

   2026-11-08

Desktop OS: Windows

Typed value: Yes.

Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams. Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop. The first-party repository describes the mobile app as available on iOS, Android and web. This establishes the phone web client, not desktop parity.

• Desktop os: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Mobile apps: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Browser: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Mobile browser: The first-party repository describes the mobile app as available on iOS, Android and web. This establishes the phone web client, not desktop parity.
• Cli: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Task actions: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.
• Cross device continuity: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.

Checked

2026-11-08 · checked 1 week ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Happy Agent v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2), Desktop v0.0.103 (a369b7b0a86a344904a2e171a78e2b0daf0b4be8); targeted first-party pass 2026-11-13; no installed-product test

• The scoped first-party source pass does not establish editor_extensions, notifications. No hands-on scenario was run.

1. Happy: How Happy fits together; Original Happy CLI

   Finding: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.

   Locator

   How Happy fits together; Original Happy CLI

   Retrieved

   2026-11-08

2. Happy: Mobile access

   Finding: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.

   Locator

   Mobile access

   Retrieved

   2026-11-08

Desktop OS: Linux

Typed value: Yes.

Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams. Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop. The first-party repository describes the mobile app as available on iOS, Android and web. This establishes the phone web client, not desktop parity.

• Desktop os: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Mobile apps: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Browser: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Mobile browser: The first-party repository describes the mobile app as available on iOS, Android and web. This establishes the phone web client, not desktop parity.
• Cli: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Task actions: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.
• Cross device continuity: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.

Checked

2026-11-08 · checked 1 week ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Happy Agent v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2), Desktop v0.0.103 (a369b7b0a86a344904a2e171a78e2b0daf0b4be8); targeted first-party pass 2026-11-13; no installed-product test

• The scoped first-party source pass does not establish editor_extensions, notifications. No hands-on scenario was run.

1. Happy: How Happy fits together; Original Happy CLI

   Finding: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.

   Locator

   How Happy fits together; Original Happy CLI

   Retrieved

   2026-11-08

2. Happy: Mobile access

   Finding: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.

   Locator

   Mobile access

   Retrieved

   2026-11-08

Web client

Typed value: Yes.

Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams. Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop. The first-party repository describes the mobile app as available on iOS, Android and web. This establishes the phone web client, not desktop parity.

• Desktop os: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Mobile apps: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Browser: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Mobile browser: The first-party repository describes the mobile app as available on iOS, Android and web. This establishes the phone web client, not desktop parity.
• Cli: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Task actions: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.
• Cross device continuity: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.

Checked

2026-11-08 · checked 1 week ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Happy Agent v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2), Desktop v0.0.103 (a369b7b0a86a344904a2e171a78e2b0daf0b4be8); targeted first-party pass 2026-11-13; no installed-product test

• The scoped first-party source pass does not establish editor_extensions, notifications. No hands-on scenario was run.

1. Happy: How Happy fits together; Original Happy CLI

   Finding: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.

   Locator

   How Happy fits together; Original Happy CLI

   Retrieved

   2026-11-08

2. Happy: Mobile access

   Finding: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.

   Locator

   Mobile access

   Retrieved

   2026-11-08

Phone access: Native iOS

Typed value: Yes.

Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams. Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop. The first-party repository describes the mobile app as available on iOS, Android and web. This establishes the phone web client, not desktop parity.

• Desktop os: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Mobile apps: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Browser: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Mobile browser: The first-party repository describes the mobile app as available on iOS, Android and web. This establishes the phone web client, not desktop parity.
• Cli: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Task actions: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.
• Cross device continuity: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.

Checked

2026-11-08 · checked 1 week ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Happy Agent v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2), Desktop v0.0.103 (a369b7b0a86a344904a2e171a78e2b0daf0b4be8); targeted first-party pass 2026-11-13; no installed-product test

• The scoped first-party source pass does not establish editor_extensions, notifications. No hands-on scenario was run.

1. Happy: How Happy fits together; Original Happy CLI

   Finding: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.

   Locator

   How Happy fits together; Original Happy CLI

   Retrieved

   2026-11-08

2. Happy: Mobile access

   Finding: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.

   Locator

   Mobile access

   Retrieved

   2026-11-08

Phone access: Native Android

Typed value: Yes.

Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams. Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop. The first-party repository describes the mobile app as available on iOS, Android and web. This establishes the phone web client, not desktop parity.

• Desktop os: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Mobile apps: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Browser: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Mobile browser: The first-party repository describes the mobile app as available on iOS, Android and web. This establishes the phone web client, not desktop parity.
• Cli: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Task actions: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.
• Cross device continuity: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.

Checked

2026-11-08 · checked 1 week ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Happy Agent v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2), Desktop v0.0.103 (a369b7b0a86a344904a2e171a78e2b0daf0b4be8); targeted first-party pass 2026-11-13; no installed-product test

• The scoped first-party source pass does not establish editor_extensions, notifications. No hands-on scenario was run.

1. Happy: How Happy fits together; Original Happy CLI

   Finding: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.

   Locator

   How Happy fits together; Original Happy CLI

   Retrieved

   2026-11-08

2. Happy: Mobile access

   Finding: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.

   Locator

   Mobile access

   Retrieved

   2026-11-08

Phone access: Phone browser

Typed value: Yes.

Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams. Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop. The first-party repository describes the mobile app as available on iOS, Android and web. This establishes the phone web client, not desktop parity.

• Desktop os: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Mobile apps: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Browser: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Mobile browser: The first-party repository describes the mobile app as available on iOS, Android and web. This establishes the phone web client, not desktop parity.
• Cli: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Happy Agent v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2), Desktop v0.0.103 (a369b7b0a86a344904a2e171a78e2b0daf0b4be8); targeted first-party pass 2026-11-13; no installed-product test

• The scoped first-party source pass does not establish editor_extensions, notifications. No hands-on scenario was run.

1. Happy: How Happy fits together; Original Happy CLI

   Finding: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.

   Locator

   How Happy fits together; Original Happy CLI

   Retrieved

   2026-11-08

CLI

Typed value: Yes.

Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams. Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop. The first-party repository describes the mobile app as available on iOS, Android and web. This establishes the phone web client, not desktop parity.

• Desktop os: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Mobile apps: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Browser: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Mobile browser: The first-party repository describes the mobile app as available on iOS, Android and web. This establishes the phone web client, not desktop parity.
• Cli: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Task actions: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.
• Cross device continuity: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.

Checked

2026-11-08 · checked 1 week ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Happy Agent v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2), Desktop v0.0.103 (a369b7b0a86a344904a2e171a78e2b0daf0b4be8); targeted first-party pass 2026-11-13; no installed-product test

• The scoped first-party source pass does not establish editor_extensions, notifications. No hands-on scenario was run.

1. Happy: How Happy fits together; Original Happy CLI

   Finding: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.

   Locator

   How Happy fits together; Original Happy CLI

   Retrieved

   2026-11-08

2. Happy: Mobile access

   Finding: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.

   Locator

   Mobile access

   Retrieved

   2026-11-08

Coding agents: Claude Code

Typed value: Yes.

Happy Agent runs its own loop by default and calls Claude, Codex and Grok models on existing CLI sign-ins. Optional harnesses run Claude Code itself (claude_code) and Codex CLI itself (codex_cli); Gemini runs through Antigravity and OpenCode or other ACP agents through ACP (beta). Grok is a model choice, not a separate harness. Model and effort can change mid-session without discarding the transcript. The original happy CLI wraps Claude Code and Codex directly. Happy Agent v2026.11.4 runs the Antigravity whole-agent harness through antigravity-acp@1.2.0, a community ACP adapter driving the signed-in agy CLI.

• Harnesses: Happy's own harness by default; claude_code and codex_cli harness options run Claude Code and Codex CLI themselves; Antigravity and OpenCode or other ACP agents (beta). The original CLI wraps Claude Code and Codex. Happy Agent v2026.11.4 runs the Antigravity whole-agent harness through antigravity-acp@1.2.0, a community ACP adapter driving the signed-in agy CLI.
• Custom adapters: Any Agent Client Protocol agent can be added on its own login (beta).
• Session integration: The claude_code and codex_cli harnesses run those agents' own loops on their accounts inside Happy sessions.
• Mixed harness operation: Subagents pick their own model, and harness options sit alongside Happy's own loop; no mixed-harness run was observed.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08 Antigravity source pass: v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2). Antigravity integration is beta.

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
• Antigravity is a beta foreign-harness integration using a community ACP adapter and its own login; new sessions are serialized to avoid conversation binding collisions.

1. Happy: How Happy fits together; Original Happy CLI

   Finding: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.

   Locator

   How Happy fits together; Original Happy CLI

   Retrieved

   2026-11-08

2. Happy: Harnesses: Claude Code, Codex CLI, Antigravity, OpenCode, and ACP agents

   Finding: Happy's own harness runs the loop by default; the claude_code harness runs Claude Code itself on a claude account and codex_cli does the same for Codex, while Antigravity, OpenCode and other ACP agents sign in themselves. Grok is not listed as a harness.

   Locator

   Harnesses

   Retrieved

   2026-11-08

Coding agents: Codex

Typed value: Yes.

Happy Agent runs its own loop by default and calls Claude, Codex and Grok models on existing CLI sign-ins. Optional harnesses run Claude Code itself (claude_code) and Codex CLI itself (codex_cli); Gemini runs through Antigravity and OpenCode or other ACP agents through ACP (beta). Grok is a model choice, not a separate harness. Model and effort can change mid-session without discarding the transcript. The original happy CLI wraps Claude Code and Codex directly. Happy Agent v2026.11.4 runs the Antigravity whole-agent harness through antigravity-acp@1.2.0, a community ACP adapter driving the signed-in agy CLI.

• Harnesses: Happy's own harness by default; claude_code and codex_cli harness options run Claude Code and Codex CLI themselves; Antigravity and OpenCode or other ACP agents (beta). The original CLI wraps Claude Code and Codex. Happy Agent v2026.11.4 runs the Antigravity whole-agent harness through antigravity-acp@1.2.0, a community ACP adapter driving the signed-in agy CLI.
• Custom adapters: Any Agent Client Protocol agent can be added on its own login (beta).
• Session integration: The claude_code and codex_cli harnesses run those agents' own loops on their accounts inside Happy sessions.
• Mixed harness operation: Subagents pick their own model, and harness options sit alongside Happy's own loop; no mixed-harness run was observed.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08 Antigravity source pass: v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2). Antigravity integration is beta.

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
• Antigravity is a beta foreign-harness integration using a community ACP adapter and its own login; new sessions are serialized to avoid conversation binding collisions.

1. Happy: How Happy fits together; Original Happy CLI

   Finding: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.

   Locator

   How Happy fits together; Original Happy CLI

   Retrieved

   2026-11-08

2. Happy: Harnesses: Claude Code, Codex CLI, Antigravity, OpenCode, and ACP agents

   Finding: Happy's own harness runs the loop by default; the claude_code harness runs Claude Code itself on a claude account and codex_cli does the same for Codex, while Antigravity, OpenCode and other ACP agents sign in themselves. Grok is not listed as a harness.

   Locator

   Harnesses

   Retrieved

   2026-11-08

Coding agents: OpenCode

Typed value: Yes.

Happy Agent runs its own loop by default and calls Claude, Codex and Grok models on existing CLI sign-ins. Optional harnesses run Claude Code itself (claude_code) and Codex CLI itself (codex_cli); Gemini runs through Antigravity and OpenCode or other ACP agents through ACP (beta). Grok is a model choice, not a separate harness. Model and effort can change mid-session without discarding the transcript. The original happy CLI wraps Claude Code and Codex directly. Happy Agent v2026.11.4 runs the Antigravity whole-agent harness through antigravity-acp@1.2.0, a community ACP adapter driving the signed-in agy CLI.

• Harnesses: Happy's own harness by default; claude_code and codex_cli harness options run Claude Code and Codex CLI themselves; Antigravity and OpenCode or other ACP agents (beta). The original CLI wraps Claude Code and Codex. Happy Agent v2026.11.4 runs the Antigravity whole-agent harness through antigravity-acp@1.2.0, a community ACP adapter driving the signed-in agy CLI.
• Model providers: Claude, Codex and Grok models on existing CLI sign-ins, Gemini through Antigravity, and Bedrock.
• Custom adapters: Any Agent Client Protocol agent can be added on its own login (beta).
• Session integration: The claude_code and codex_cli harnesses run those agents' own loops on their accounts inside Happy sessions.
• Mixed harness operation: Subagents pick their own model, and harness options sit alongside Happy's own loop; no mixed-harness run was observed.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08 Antigravity source pass: v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2). Antigravity integration is beta.

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
• Antigravity is a beta foreign-harness integration using a community ACP adapter and its own login; new sessions are serialized to avoid conversation binding collisions.

1. Happy: Supported providers; Switch models

   Finding: Happy runs Claude, Codex and Grok on the user's existing Claude Code, Codex or Grok CLI sign-ins, Gemini through Antigravity, and OpenCode or other ACP agents on their own login (beta). Model or effort can change mid-session without discarding the transcript.

   Locator

   Supported providers; Switch models

   Retrieved

   2026-11-08

2. Happy: Harnesses: Claude Code, Codex CLI, Antigravity, OpenCode, and ACP agents

   Finding: Happy's own harness runs the loop by default; the claude_code harness runs Claude Code itself on a claude account and codex_cli does the same for Codex, while Antigravity, OpenCode and other ACP agents sign in themselves. Grok is not listed as a harness.

   Locator

   Harnesses

   Retrieved

   2026-11-08

Coding agents: Antigravity

Typed value: Yes.

Happy Agent runs its own loop by default and calls Claude, Codex and Grok models on existing CLI sign-ins. Optional harnesses run Claude Code itself (claude_code) and Codex CLI itself (codex_cli); Gemini runs through Antigravity and OpenCode or other ACP agents through ACP (beta). Grok is a model choice, not a separate harness. Model and effort can change mid-session without discarding the transcript. The original happy CLI wraps Claude Code and Codex directly. Happy Agent v2026.11.4 runs the Antigravity whole-agent harness through antigravity-acp@1.2.0, a community ACP adapter driving the signed-in agy CLI.

• Harnesses: Happy's own harness by default; claude_code and codex_cli harness options run Claude Code and Codex CLI themselves; Antigravity and OpenCode or other ACP agents (beta). The original CLI wraps Claude Code and Codex. Happy Agent v2026.11.4 runs the Antigravity whole-agent harness through antigravity-acp@1.2.0, a community ACP adapter driving the signed-in agy CLI.

Checked

2026-11-10 · checked 5 days ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08 Antigravity source pass: v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2). Antigravity integration is beta.

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
• Antigravity is a beta foreign-harness integration using a community ACP adapter and its own login; new sessions are serialized to avoid conversation binding collisions.

1. Happy Antigravity support at v2026.11.4

   Finding: Happy Agent v2026.11.4 runs the Antigravity whole-agent harness through antigravity-acp@1.2.0, a community ACP adapter driving the signed-in agy CLI.

   Locator

   packages/happy-providers/sources/vendors/foreignAgents/antigravityAgent.ts lines 30-63, v2026.11.4, commit db813011c038b2288fbc1efd0e10ef2149c838d2

   Retrieved

   2026-11-10

   Source date

   2026-11-10

Use my subscription

Typed value: Yes.

Happy reuses existing Claude Code, Codex and Grok CLI sign-ins and their subscriptions; Antigravity and ACP agents use their own login. Bedrock API keys or the AWS credential chain are supported.

• Agent subscriptions: Happy reuses Claude Code, Codex and Grok CLI sign-ins and their subscriptions; Antigravity and ACP use their own login. Bedrock API keys or the AWS credential chain are supported. Happy does not proxy these provider requests.
• Api accounts: Happy reuses Claude Code, Codex and Grok CLI sign-ins and their subscriptions; Antigravity and ACP use their own login. Bedrock API keys or the AWS credential chain are supported. Happy does not proxy these provider requests.
• Account switching: Happy reuses Claude Code, Codex and Grok CLI sign-ins and their subscriptions; Antigravity and ACP use their own login. Bedrock API keys or the AWS credential chain are supported. Happy does not proxy these provider requests.
• Provider restrictions: Happy reuses Claude Code, Codex and Grok CLI sign-ins and their subscriptions; Antigravity and ACP use their own login. Bedrock API keys or the AWS credential chain are supported. Happy does not proxy these provider requests.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Models and Subscriptions

   Finding: Happy uses existing Claude Code, Codex and Grok CLI sign-ins, so no Happy plan or pasted key is needed for model access; Antigravity and ACP agents use their own login. Bedrock works with an API key or the AWS credential chain.

   Locator

   Models and Subscriptions

   Retrieved

   2026-11-08

Where agents run: On your computer

Typed value: Yes.

Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.

• Local: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Byo remote: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Self hosted: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Hybrid: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Payer: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Client disconnect: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Other device continuation: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Remote server

   Finding: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.

   Locator

   Remote server

   Retrieved

   2026-11-08

Where agents run: On your own server

Typed value: Yes.

Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.

• Local: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Byo remote: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Self hosted: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Hybrid: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Payer: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Client disconnect: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Other device continuation: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Remote server

   Finding: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.

   Locator

   Remote server

   Retrieved

   2026-11-08

Where agents run: In the vendor's cloud

Typed value: No.

Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.

• Local: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Byo remote: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Self hosted: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Hybrid: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Payer: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Client disconnect: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Other device continuation: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Remote server

   Finding: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.

   Locator

   Remote server

   Retrieved

   2026-11-08

Workspace isolation: Git worktree

Typed value: Yes.

Parallel workspaces use Git worktrees on branches cut from the remote trunk. File sync and setup commands run per workspace; nongit projects use a plain copy. The documented OS sandbox uses macOS Seatbelt or Linux namespaces and seccomp. Shell writes, network and host sockets are restricted; file tools can still read credential folders, and MCP servers run outside the sandbox. Docker-backed sessions nest that sandbox inside the container. No VM or microVM isolation backend exists in the inspected runtime; local OS sandboxing and Docker are separate options.

• Branch: Parallel workspaces use Git worktrees on branches cut from the remote trunk. File sync and setup commands run per workspace; nongit projects use a plain copy.
• Worktree: Parallel workspaces use Git worktrees on branches cut from the remote trunk. File sync and setup commands run per workspace; nongit projects use a plain copy.
• Container: The documented OS sandbox uses macOS Seatbelt or Linux namespaces and seccomp. Shell writes, network and host sockets are restricted; file tools can still read credential folders, and MCP servers run outside the sandbox. Docker-backed sessions nest that sandbox inside the container.
• Os sandbox: The documented OS sandbox uses macOS Seatbelt or Linux namespaces and seccomp. Shell writes, network and host sockets are restricted; file tools can still read credential folders, and MCP servers run outside the sandbox. Docker-backed sessions nest that sandbox inside the container.
• Filesystem: The documented OS sandbox uses macOS Seatbelt or Linux namespaces and seccomp. Shell writes, network and host sockets are restricted; file tools can still read credential folders, and MCP servers run outside the sandbox. Docker-backed sessions nest that sandbox inside the container.
• Network: The documented OS sandbox uses macOS Seatbelt or Linux namespaces and seccomp. Shell writes, network and host sockets are restricted; file tools can still read credential folders, and MCP servers run outside the sandbox. Docker-backed sessions nest that sandbox inside the container.
• Secrets: The documented OS sandbox uses macOS Seatbelt or Linux namespaces and seccomp. Shell writes, network and host sockets are restricted; file tools can still read credential folders, and MCP servers run outside the sandbox. Docker-backed sessions nest that sandbox inside the container.
• Code separation: Parallel workspaces use Git worktrees on branches cut from the remote trunk. File sync and setup commands run per workspace; nongit projects use a plain copy.
• Security boundary: The documented OS sandbox uses macOS Seatbelt or Linux namespaces and seccomp. Shell writes, network and host sockets are restricted; file tools can still read credential folders, and MCP servers run outside the sandbox. Docker-backed sessions nest that sandbox inside the container.

Checked

2026-11-08 · checked 1 week ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Happy Agent v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2), Desktop v0.0.103 (a369b7b0a86a344904a2e171a78e2b0daf0b4be8); targeted first-party pass 2026-11-13; no installed-product test

• The scoped first-party source pass does not establish checkout, process. No hands-on scenario was run.

1. Happy: How Happy creates a workspace

   Finding: Parallel workspaces use Git worktrees on branches cut from the remote trunk. File sync and setup commands run per workspace; nongit projects use a plain copy.

   Locator

   How Happy creates a workspace

   Retrieved

   2026-11-08

2. Happy: What the OS sandbox enforces

   Finding: The documented OS sandbox uses macOS Seatbelt or Linux namespaces and seccomp. Shell writes, network and host sockets are restricted; file tools can still read credential folders, and MCP servers run outside the sandbox. Docker-backed sessions nest that sandbox inside the container.

   Locator

   What the OS sandbox enforces

   Retrieved

   2026-11-08

Workspace isolation: Container

Typed value: Yes.

Parallel workspaces use Git worktrees on branches cut from the remote trunk. File sync and setup commands run per workspace; nongit projects use a plain copy. The documented OS sandbox uses macOS Seatbelt or Linux namespaces and seccomp. Shell writes, network and host sockets are restricted; file tools can still read credential folders, and MCP servers run outside the sandbox. Docker-backed sessions nest that sandbox inside the container. No VM or microVM isolation backend exists in the inspected runtime; local OS sandboxing and Docker are separate options.

• Branch: Parallel workspaces use Git worktrees on branches cut from the remote trunk. File sync and setup commands run per workspace; nongit projects use a plain copy.
• Worktree: Parallel workspaces use Git worktrees on branches cut from the remote trunk. File sync and setup commands run per workspace; nongit projects use a plain copy.
• Container: The documented OS sandbox uses macOS Seatbelt or Linux namespaces and seccomp. Shell writes, network and host sockets are restricted; file tools can still read credential folders, and MCP servers run outside the sandbox. Docker-backed sessions nest that sandbox inside the container.
• Os sandbox: The documented OS sandbox uses macOS Seatbelt or Linux namespaces and seccomp. Shell writes, network and host sockets are restricted; file tools can still read credential folders, and MCP servers run outside the sandbox. Docker-backed sessions nest that sandbox inside the container.
• Filesystem: The documented OS sandbox uses macOS Seatbelt or Linux namespaces and seccomp. Shell writes, network and host sockets are restricted; file tools can still read credential folders, and MCP servers run outside the sandbox. Docker-backed sessions nest that sandbox inside the container.
• Network: The documented OS sandbox uses macOS Seatbelt or Linux namespaces and seccomp. Shell writes, network and host sockets are restricted; file tools can still read credential folders, and MCP servers run outside the sandbox. Docker-backed sessions nest that sandbox inside the container.
• Secrets: The documented OS sandbox uses macOS Seatbelt or Linux namespaces and seccomp. Shell writes, network and host sockets are restricted; file tools can still read credential folders, and MCP servers run outside the sandbox. Docker-backed sessions nest that sandbox inside the container.
• Code separation: Parallel workspaces use Git worktrees on branches cut from the remote trunk. File sync and setup commands run per workspace; nongit projects use a plain copy.
• Security boundary: The documented OS sandbox uses macOS Seatbelt or Linux namespaces and seccomp. Shell writes, network and host sockets are restricted; file tools can still read credential folders, and MCP servers run outside the sandbox. Docker-backed sessions nest that sandbox inside the container.

Checked

2026-11-08 · checked 1 week ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Happy Agent v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2), Desktop v0.0.103 (a369b7b0a86a344904a2e171a78e2b0daf0b4be8); targeted first-party pass 2026-11-13; no installed-product test

• The scoped first-party source pass does not establish checkout, process. No hands-on scenario was run.

1. Happy: How Happy creates a workspace

   Finding: Parallel workspaces use Git worktrees on branches cut from the remote trunk. File sync and setup commands run per workspace; nongit projects use a plain copy.

   Locator

   How Happy creates a workspace

   Retrieved

   2026-11-08

2. Happy: What the OS sandbox enforces

   Finding: The documented OS sandbox uses macOS Seatbelt or Linux namespaces and seccomp. Shell writes, network and host sockets are restricted; file tools can still read credential folders, and MCP servers run outside the sandbox. Docker-backed sessions nest that sandbox inside the container.

   Locator

   What the OS sandbox enforces

   Retrieved

   2026-11-08

Workspace isolation: VM or microVM

Typed value: No.

Parallel workspaces use Git worktrees on branches cut from the remote trunk. File sync and setup commands run per workspace; nongit projects use a plain copy. The documented OS sandbox uses macOS Seatbelt or Linux namespaces and seccomp. Shell writes, network and host sockets are restricted; file tools can still read credential folders, and MCP servers run outside the sandbox. Docker-backed sessions nest that sandbox inside the container. No VM or microVM isolation backend exists in the inspected runtime; local OS sandboxing and Docker are separate options.

• Vm: No VM or microVM isolation backend exists in the inspected runtime; local OS sandboxing and Docker are separate options.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Happy Agent v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2), Desktop v0.0.103 (a369b7b0a86a344904a2e171a78e2b0daf0b4be8); targeted first-party pass 2026-11-13; no installed-product test

• The scoped first-party source pass does not establish checkout, process. No hands-on scenario was run.

1. Happy execution configuration at v2026.11.4

   Finding: The scoped runtime config and runner implementation provide host process execution and optional Docker image/container execution, with OS sandbox restrictions. No VM or microVM isolation backend is implemented in the inspected release. A user provisioning a host VM is separate.

   Locator

   Docker configuration lines 261-272; sources/runners and runtime inspection; search terms docker, virtual machine, microvm

   Retrieved

   2026-11-13

Parallel runs

Typed value: Yes.

Subagents run in the background by default and return completion to the parent. Desktop displays subagents and running tools; tree size is bounded.

• Concurrent sessions: Subagents run in the background by default and return completion to the parent. Desktop displays subagents and running tools; tree size is bounded.
• Concurrent tasks: Subagents run in the background by default and return completion to the parent. Desktop displays subagents and running tools; tree size is bounded.
• Quotas: Subagents run in the background by default and return completion to the parent. Desktop displays subagents and running tools; tree size is bounded.
• Status visibility: Subagents run in the background by default and return completion to the parent. Desktop displays subagents and running tools; tree size is bounded.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Subagents; What Happy Desktop shows

   Finding: Subagents run in the background by default and return completion to the parent. Desktop displays subagents and running tools; tree size is bounded.

   Locator

   Subagents; What Happy Desktop shows

   Retrieved

   2026-11-08

Coordinator

Typed value: Yes.

Agents delegate bounded work, choose each child model and effort, receive background completion notices and send follow-ups to finished children with retained context. Exact IDs route messages across projects or machines.

• Roles: Agents delegate bounded work, choose each child model and effort, receive background completion notices and send follow-ups to finished children with retained context. Exact IDs route messages across projects or machines.
• Model harness effort: Agents delegate bounded work, choose each child model and effort, receive background completion notices and send follow-ups to finished children with retained context. Exact IDs route messages across projects or machines.
• Messages: Agents delegate bounded work, choose each child model and effort, receive background completion notices and send follow-ups to finished children with retained context. Exact IDs route messages across projects or machines.
• Results return: Agents delegate bounded work, choose each child model and effort, receive background completion notices and send follow-ups to finished children with retained context. Exact IDs route messages across projects or machines.
• Cross harness: Agents delegate bounded work, choose each child model and effort, receive background completion notices and send follow-ups to finished children with retained context. Exact IDs route messages across projects or machines.
• Activation: Agents delegate bounded work, choose each child model and effort, receive background completion notices and send follow-ups to finished children with retained context. Exact IDs route messages across projects or machines.
• Retained results: Agents delegate bounded work, choose each child model and effort, receive background completion notices and send follow-ups to finished children with retained context. Exact IDs route messages across projects or machines.
• Followup: Agents delegate bounded work, choose each child model and effort, receive background completion notices and send follow-ups to finished children with retained context. Exact IDs route messages across projects or machines.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Subagents; How agents message each other

   Finding: Agents delegate bounded work, choose each child model and effort, receive background completion notices and send follow-ups to finished children with retained context. Exact IDs route messages across projects or machines.

   Locator

   Subagents; How agents message each other

   Retrieved

   2026-11-08

Native issue tracking

Typed value: Yes.

Happy creates persistent task records through its API, agent tool and Desktop UI. Native task operations rename task records. Creating a task without opening text stores an idle draft. The task catalog has a task ID separate from its linked agent and workspace IDs; each task has one root conversation. Task state is persisted as active or archived with restoration and versioned updates. Task archival persists and stops the task agent and descendants. Native unarchive restores an archived task.

• Create: Happy creates persistent task records through its API, agent tool and Desktop UI.
• Edit: Native task operations rename task records.
• Archive: Task archival persists and stops the task agent and descendants.
• Reopen: Native unarchive restores an archived task.
• Idea parking: Creating a task without opening text stores an idle draft.
• Task session separation: The task catalog has a task ID separate from its linked agent and workspace IDs; each task has one root conversation.
• Durable states: Task state is persisted as active or archived with restoration and versioned updates.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Happy Agent v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2), Desktop v0.0.103 (a369b7b0a86a344904a2e171a78e2b0daf0b4be8); targeted first-party pass 2026-11-13; no installed-product test

• The scoped first-party source pass does not establish discuss, prioritize, label, assign, search, filter, project_epic_views, explicit_dispatch, metadata, external_tracker_requirement. No hands-on scenario was run.

1. Happy task catalog schema at v2026.11.4

   Finding: Task records have independent task, agent and workspace IDs, owner and creator fields, versioned active/archived state and timestamps. Creation accepts no opening text, allowing an idle draft before work starts.

   Locator

   Task record schema and createTaskInputSchema, lines 28-151

   Retrieved

   2026-11-13

2. Happy native task operations at v2026.11.4

   Finding: The TasksModule creates distinct task and agent records, supports rename, join, reorder, archive and unarchive, and persists catalog state. The API and Desktop task creation surface expose the task catalog.

   Locator

   createWithResult and task archive/unarchive operations; corresponding TaskMigrations.ts table

   Retrieved

   2026-11-13

Unattended triggers

Typed value: Yes.

Primary sessions can schedule messages to known agent IDs, list or cancel them and survive intervening runtime restarts. Durable waits end early on new input. This establishes scheduled work, not an unrestricted external-event scheduler.

• Schedules: Primary sessions can schedule messages to known agent IDs, list or cancel them and survive intervening runtime restarts. Durable waits end early on new input. This establishes scheduled work, not an unrestricted external-event scheduler.
• Scheduler location: Primary sessions can schedule messages to known agent IDs, list or cancel them and survive intervening runtime restarts. Durable waits end early on new input. This establishes scheduled work, not an unrestricted external-event scheduler.
• Client independence: Primary sessions can schedule messages to known agent IDs, list or cancel them and survive intervening runtime restarts. Durable waits end early on new input. This establishes scheduled work, not an unrestricted external-event scheduler.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Durable waits and scheduled messages

   Finding: Primary sessions can schedule messages to known agent IDs, list or cancel them and survive intervening runtime restarts. Durable waits end early on new input. This establishes scheduled work, not an unrestricted external-event scheduler.

   Locator

   Durable waits and scheduled messages

   Retrieved

   2026-11-08

Shared prompting

Typed value: Yes.

Team members see the same projects and sessions and can speak to the agent. Changes in speaker include the member name/email; per-member drafts and task ordering stay personal.

• Visibility: Team members see the same projects and sessions and can speak to the agent. Changes in speaker include the member name/email; per-member drafts and task ordering stay personal.
• Coprompting: Team members see the same projects and sessions and can speak to the agent. Changes in speaker include the member name/email; per-member drafts and task ordering stay personal.
• Attribution: Team members see the same projects and sessions and can speak to the agent. Changes in speaker include the member name/email; per-member drafts and task ordering stay personal.
• Permissions: Team members see the same projects and sessions and can speak to the agent. Changes in speaker include the member name/email; per-member drafts and task ordering stay personal.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Shared work

   Finding: Team members see the same projects and sessions and can speak to the agent. Changes in speaker include the member name/email; per-member drafts and task ordering stay personal.

   Locator

   Shared work

   Retrieved

   2026-11-08

Team roles

Typed value: Yes.

Team mode verifies per-user WorkOS tokens. The owner alone renames the installation, toggles global skills or archives others tasks; members otherwise have equal access and can select Full access. A remove-member action is explicitly not built yet.

• Organization roles: Team mode verifies per-user WorkOS tokens. The owner alone renames the installation, toggles global skills or archives others tasks; members otherwise have equal access and can select Full access. A remove-member action is explicitly not built yet.
• Membership: Team mode verifies per-user WorkOS tokens. The owner alone renames the installation, toggles global skills or archives others tasks; members otherwise have equal access and can select Full access. A remove-member action is explicitly not built yet.
• Plan scope: Team mode verifies per-user WorkOS tokens. The owner alone renames the installation, toggles global skills or archives others tasks; members otherwise have equal access and can select Full access. A remove-member action is explicitly not built yet.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Owner; Sign-in; Leaving

   Finding: Team mode verifies per-user WorkOS tokens. The owner alone renames the installation, toggles global skills or archives others tasks; members otherwise have equal access and can select Full access. A remove-member action is explicitly not built yet.

   Locator

   Owner; Sign-in; Leaving

   Retrieved

   2026-11-08

SSO

Typed value: Yes.

Team mode verifies per-user WorkOS tokens. The owner alone renames the installation, toggles global skills or archives others tasks; members otherwise have equal access and can select Full access. A remove-member action is explicitly not built yet.

• Sso: Team mode can replace Happy's WorkOS accounts with the organization's own identity provider through an organization-run OAuth authorization server whose JWTs the daemon verifies (Agent v2026.11.4; desktop v0.0.103 discovers sign-in methods). Documented and source-inspected, not tested; the deployer must operate the authorization server.

Checked

2026-11-10 · checked 5 days ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy website source: Set up enterprise JWT sign-in

   Finding: Recipe for a team-mode Happy Agent whose members sign in through the organization's own identity provider (Okta, Entra ID, Google Workspace, Keycloak or internal SSO) instead of Happy's WorkOS accounts; the daemon verifies JWTs from an organization-owned OAuth authorization server and needs an Agent release with enterprise JWT authentication.

   Locator

   content/desktop/recepies/enterprise-sign-in.mdx lines 1-15, commit 275790d

   Retrieved

   2026-11-10

2. Happy Agent TeamJwtConfig at release v2026.11.4

   Finding: The released Happy Agent v2026.11.4 parses a [feature.team.jwt] machine configuration with an authorization URL and exactly one of a JWKS URL, public key or secret, used to verify organization-issued team tokens.

   Locator

   packages/happy-agent-modules/sources/config/TeamJwtConfig.ts lines 47-140, tag v2026.11.4 (commit db81301)

   Retrieved

   2026-11-10

3. Happy Desktop server sign-in discovery at release v0.0.103

   Finding: The released desktop app v0.0.103 queries a Happy Agent server's v0/authentication endpoint to discover its sign-in methods.

   Locator

   packages/happy-desktop-electron/sources/main/serverSessions.ts line 318, tag v0.0.103 (commit a369b7b)

   Retrieved

   2026-11-10

Pull request workflow

Typed value: No.

The pinned runtime and clients manage Git workspaces and file changes. They have no built-in PR creation or management path; users can ask a coding agent to use external shell or MCP tools.

• Pull requests: The inspected release has no built-in PR create/manage interface. External shell or MCP tools remain possible.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Happy Agent v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2), Desktop v0.0.103 (a369b7b0a86a344904a2e171a78e2b0daf0b4be8); targeted first-party pass 2026-11-13; no installed-product test

• The scoped first-party source pass does not establish branches, worktrees, commits, comments, ci_response, rebase, conflicts, product_state. No hands-on scenario was run.

1. Happy Git module and bounded PR integration inspection

   Finding: The pinned runtime Git module and clients provide file changes, branches and workspaces, but no product-owned pull-request creation or management path was found. PRs can still be operated through an external shell command or MCP service; that is not a built-in Happy PR workflow.

   Locator

   GitModule.ts and sibling sources/git, sources/api, sources/tasks; happy-desktop AppHappyAgentView.tsx at a369b7b; happy CLI/iOS/Android sources at df13fc0. Searches: pull request, pull_request, gh pr, pr create.

   Retrieved

   2026-11-13

Review interface

Typed value: Yes.

The desktop interface has conversations, files, diffs and an attachable terminal; current docs describe changed files beside each conversation. Guided batch review was not established.

• Change understanding: The desktop interface has conversations, files, diffs and an attachable terminal; current docs describe changed files beside each conversation. Guided batch review was not established.
• Evidence navigation: The desktop interface has conversations, files, diffs and an attachable terminal; current docs describe changed files beside each conversation. Guided batch review was not established.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Initial core release; Current interface

   Finding: The desktop interface has conversations, files, diffs and an attachable terminal; current docs describe changed files beside each conversation. Guided batch review was not established.

   Locator

   Initial core release; Current interface

   Retrieved

   2026-11-08

Product license: Apache-2.0

Typed value: No. MIT.

The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

• Client license: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Server license: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Source visibility: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Source revision: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: MIT License

   Finding: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

   Locator

   MIT License

   Retrieved

   2026-11-08

Product license: MIT

Typed value: Yes. MIT.

The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

• Client license: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Server license: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Source visibility: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Source revision: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: MIT License

   Finding: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

   Locator

   MIT License

   Retrieved

   2026-11-08

Product license: GPL-3.0

Typed value: No. MIT.

The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

• Client license: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Server license: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Source visibility: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Source revision: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: MIT License

   Finding: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

   Locator

   MIT License

   Retrieved

   2026-11-08

Product license: GPL-3.0-or-later

Typed value: No. MIT.

The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

• Client license: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Server license: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Source visibility: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Source revision: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: MIT License

   Finding: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

   Locator

   MIT License

   Retrieved

   2026-11-08

Product license: AGPL-3.0

Typed value: No. MIT.

The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

• Client license: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Server license: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Source visibility: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Source revision: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: MIT License

   Finding: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

   Locator

   MIT License

   Retrieved

   2026-11-08

Product license: AGPL-3.0-or-later

Typed value: No. MIT.

The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

• Client license: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Server license: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Source visibility: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Source revision: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: MIT License

   Finding: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

   Locator

   MIT License

   Retrieved

   2026-11-08

Product license: Elastic License 2.0

Typed value: No. MIT.

The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

• Client license: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Server license: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Source visibility: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Source revision: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: MIT License

   Finding: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

   Locator

   MIT License

   Retrieved

   2026-11-08

Product license: Custom terms

Typed value: No. MIT.

The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

• Client license: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Server license: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Source visibility: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Source revision: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: MIT License

   Finding: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

   Locator

   MIT License

   Retrieved

   2026-11-08

Product license: Proprietary

Typed value: No. MIT.

The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

• Client license: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Server license: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Source visibility: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Source revision: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: MIT License

   Finding: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

   Locator

   MIT License

   Retrieved

   2026-11-08

Self-hosting

Typed value: Yes.

The core Happy Agent runs self-hosted on user machines or servers, with Desktop connecting remotely. Happy Social/WorkOS team sign-in and the mobile relay are distinct service dependencies.

• Self hosting: The core Happy Agent runs self-hosted on user machines or servers, with Desktop connecting remotely. Happy Social/WorkOS team sign-in and the mobile relay are distinct service dependencies.
• Vendor dependencies: The core Happy Agent runs self-hosted on user machines or servers, with Desktop connecting remotely. Happy Social/WorkOS team sign-in and the mobile relay are distinct service dependencies.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: How a Happy team server works

   Finding: The core Happy Agent runs self-hosted on user machines or servers, with Desktop connecting remotely. Happy Social/WorkOS team sign-in and the mobile relay are distinct service dependencies.

   Locator

   How a Happy team server works

   Retrieved

   2026-11-08

Telemetry opt-out

Typed value: Yes.

Happy apps send pseudonymous usage events to PostHog, excluding message content, prompts, code and file names, and offer a Settings opt-out that stops them; the desktop app has its own switch. Happy Agent itself sends no analytics.

• Telemetry disclosure: Happy apps send product usage events to PostHog and offer a Settings opt-out that stops analytics events. Happy Agent itself sends no analytics. Provider/model work still follows provider policies.
• Telemetry defaults: Happy apps send product usage events to PostHog and offer a Settings opt-out that stops analytics events. Happy Agent itself sends no analytics. Provider/model work still follows provider policies.
• Telemetry controls: Happy apps send product usage events to PostHog and offer a Settings opt-out that stops analytics events. Happy Agent itself sends no analytics. Provider/model work still follows provider policies.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Analytics: PostHog

   Finding: Happy apps send pseudonymous product usage events to PostHog, excluding message content, prompts, code and file names, and offer a Settings opt-out that stops them; the desktop app has its own switch. Happy Agent itself sends no analytics.

   Locator

   Analytics: PostHog

   Retrieved

   2026-11-08

Free access

Typed value: Yes.

The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.

• Ongoing free: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.
• Self host cost: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.
• Free scenarios: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: What does Happy cost?

   Finding: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.

   Locator

   What does Happy cost?

   Retrieved

   2026-11-08

Starting price: Free

Typed value: Yes. Free.

The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.

• Ongoing free: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.
• Self host cost: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.
• Free scenarios: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: What does Happy cost?

   Finding: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.

   Locator

   What does Happy cost?

   Retrieved

   2026-11-08

Starting price: Up to $20/month

Typed value: No. Free.

The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.

• Ongoing free: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.
• Self host cost: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.
• Free scenarios: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: What does Happy cost?

   Finding: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.

   Locator

   What does Happy cost?

   Retrieved

   2026-11-08

Starting price: $21–40/month

Typed value: No. Free.

The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.

• Ongoing free: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.
• Self host cost: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.
• Free scenarios: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: What does Happy cost?

   Finding: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.

   Locator

   What does Happy cost?

   Retrieved

   2026-11-08

Starting price: $41–100/month

Typed value: No. Free.

The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.

• Ongoing free: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.
• Self host cost: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.
• Free scenarios: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: What does Happy cost?

   Finding: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.

   Locator

   What does Happy cost?

   Retrieved

   2026-11-08

Starting price: Over $100/month

Typed value: No. Free.

The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.

• Ongoing free: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.
• Self host cost: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.
• Free scenarios: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: What does Happy cost?

   Finding: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.

   Locator

   What does Happy cost?

   Retrieved

   2026-11-08

Starting price: Contact for pricing

Typed value: No. Free.

The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.

• Ongoing free: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.
• Self host cost: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.
• Free scenarios: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: What does Happy cost?

   Finding: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.

   Locator

   What does Happy cost?

   Retrieved

   2026-11-08

Pricing model: Free, no paid plan

Typed value: No.

Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.

• Included usage: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.
• Model cost: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.
• Compute cost: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: What does Happy cost?

   Finding: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.

   Locator

   What does Happy cost?

   Retrieved

   2026-11-08

Pricing model: Free plan

Typed value: Yes.

Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.

• Included usage: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.
• Model cost: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.
• Compute cost: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: What does Happy cost?

   Finding: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.

   Locator

   What does Happy cost?

   Retrieved

   2026-11-08

Pricing model: Subscription

Typed value: Yes.

Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.

• Included usage: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.
• Model cost: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.
• Compute cost: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: What does Happy cost?

   Finding: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.

   Locator

   What does Happy cost?

   Retrieved

   2026-11-08

Pricing model: Per seat

Typed value: No.

Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.

• Included usage: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.
• Model cost: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.
• Compute cost: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: What does Happy cost?

   Finding: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.

   Locator

   What does Happy cost?

   Retrieved

   2026-11-08

Pricing model: Usage-based

Typed value: No.

Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.

• Included usage: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.
• Model cost: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.
• Compute cost: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: What does Happy cost?

   Finding: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.

   Locator

   What does Happy cost?

   Retrieved

   2026-11-08

Pricing model: Per machine or compute

Typed value: No.

Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.

• Included usage: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.
• Model cost: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.
• Compute cost: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: What does Happy cost?

   Finding: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.

   Locator

   What does Happy cost?

   Retrieved

   2026-11-08

Pricing model: Bring your own key

Typed value: Yes.

Happy reuses existing Claude Code, Codex and Grok CLI sign-ins and their subscriptions; Antigravity and ACP agents use their own login. Bedrock API keys or the AWS credential chain are supported.

• Agent subscriptions: Happy reuses Claude Code, Codex and Grok CLI sign-ins and their subscriptions; Antigravity and ACP use their own login. Bedrock API keys or the AWS credential chain are supported. Happy does not proxy these provider requests.
• Api accounts: Happy reuses Claude Code, Codex and Grok CLI sign-ins and their subscriptions; Antigravity and ACP use their own login. Bedrock API keys or the AWS credential chain are supported. Happy does not proxy these provider requests.
• Account switching: Happy reuses Claude Code, Codex and Grok CLI sign-ins and their subscriptions; Antigravity and ACP use their own login. Bedrock API keys or the AWS credential chain are supported. Happy does not proxy these provider requests.
• Provider restrictions: Happy reuses Claude Code, Codex and Grok CLI sign-ins and their subscriptions; Antigravity and ACP use their own login. Bedrock API keys or the AWS credential chain are supported. Happy does not proxy these provider requests.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Models and Subscriptions

   Finding: Happy uses existing Claude Code, Codex and Grok CLI sign-ins, so no Happy plan or pasted key is needed for model access; Antigravity and ACP agents use their own login. Bedrock works with an API key or the AWS credential chain.

   Locator

   Models and Subscriptions

   Retrieved

   2026-11-08

Pricing model: One-time purchase

Typed value: No.

Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.

• Included usage: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.
• Model cost: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.
• Compute cost: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: What does Happy cost?

   Finding: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.

   Locator

   What does Happy cost?

   Retrieved

   2026-11-08

Keeps going with laptop closed

Typed value: Yes.

Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.

• Local: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Byo remote: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Self hosted: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Hybrid: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Payer: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Client disconnect: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.
• Other device continuation: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Remote server

   Finding: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.

   Locator

   Remote server

   Retrieved

   2026-11-08

Open-source license

Typed value: Yes. MIT.

The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

• Client license: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Server license: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Source visibility: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.
• Source revision: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: MIT License

   Finding: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

   Locator

   MIT License

   Retrieved

   2026-11-08

Any desktop app

Typed value: Yes.

Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams. Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop. The first-party repository describes the mobile app as available on iOS, Android and web. This establishes the phone web client, not desktop parity.

• Desktop os: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Mobile apps: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Browser: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Mobile browser: The first-party repository describes the mobile app as available on iOS, Android and web. This establishes the phone web client, not desktop parity.
• Cli: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Task actions: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.
• Cross device continuity: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.

Checked

2026-11-08 · checked 1 week ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Happy Agent v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2), Desktop v0.0.103 (a369b7b0a86a344904a2e171a78e2b0daf0b4be8); targeted first-party pass 2026-11-13; no installed-product test

• The scoped first-party source pass does not establish editor_extensions, notifications. No hands-on scenario was run.

1. Happy: How Happy fits together; Original Happy CLI

   Finding: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.

   Locator

   How Happy fits together; Original Happy CLI

   Retrieved

   2026-11-08

2. Happy: Mobile access

   Finding: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.

   Locator

   Mobile access

   Retrieved

   2026-11-08

Any phone client

Typed value: Yes.

Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams. Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop. The first-party repository describes the mobile app as available on iOS, Android and web. This establishes the phone web client, not desktop parity.

• Desktop os: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Mobile apps: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Browser: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Mobile browser: The first-party repository describes the mobile app as available on iOS, Android and web. This establishes the phone web client, not desktop parity.
• Cli: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.
• Task actions: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.
• Cross device continuity: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.

Checked

2026-11-08 · checked 1 week ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Happy Agent v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2), Desktop v0.0.103 (a369b7b0a86a344904a2e171a78e2b0daf0b4be8); targeted first-party pass 2026-11-13; no installed-product test

• The scoped first-party source pass does not establish editor_extensions, notifications. No hands-on scenario was run.

1. Happy: How Happy fits together; Original Happy CLI

   Finding: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.

   Locator

   How Happy fits together; Original Happy CLI

   Retrieved

   2026-11-08

2. Happy: Mobile access

   Finding: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.

   Locator

   Mobile access

   Retrieved

   2026-11-08

happy:ACC-01

Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams. Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop. The first-party repository describes the mobile app as available on iOS, Android and web. This establishes the phone web client, not desktop parity.

Checked

2026-11-08 · checked 1 week ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Happy Agent v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2), Desktop v0.0.103 (a369b7b0a86a344904a2e171a78e2b0daf0b4be8); targeted first-party pass 2026-11-13; no installed-product test

• The scoped first-party source pass does not establish editor_extensions, notifications. No hands-on scenario was run.

1. Happy: How Happy fits together; Original Happy CLI

   Finding: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.

   Locator

   How Happy fits together; Original Happy CLI

   Retrieved

   2026-11-08

2. Happy: Mobile access

   Finding: Paired phone apps continue the same encrypted sessions and allow users to read work and respond away from the desktop.

   Locator

   Mobile access

   Retrieved

   2026-11-08

happy:ACC-02

Happy Agent runs its own loop by default and calls Claude, Codex and Grok models on existing CLI sign-ins. Optional harnesses run Claude Code itself (claude_code) and Codex CLI itself (codex_cli); Gemini runs through Antigravity and OpenCode or other ACP agents through ACP (beta). Grok is a model choice, not a separate harness. Model and effort can change mid-session without discarding the transcript. The original happy CLI wraps Claude Code and Codex directly. Happy Agent v2026.11.4 runs the Antigravity whole-agent harness through antigravity-acp@1.2.0, a community ACP adapter driving the signed-in agy CLI.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08 Antigravity source pass: v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2). Antigravity integration is beta.

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.
• Antigravity is a beta foreign-harness integration using a community ACP adapter and its own login; new sessions are serialized to avoid conversation binding collisions.

1. Happy: How Happy fits together; Original Happy CLI

   Finding: Happy provides Desktop for macOS, Windows and Linux; mobile iOS, Android and web; and its original happy CLI wrapping Claude Code or Codex. Desktop uses a separate Happy Agent runtime for multi-model sessions and teams.

   Locator

   How Happy fits together; Original Happy CLI

   Retrieved

   2026-11-08

2. Happy: Supported providers; Switch models

   Finding: Happy runs Claude, Codex and Grok on the user's existing Claude Code, Codex or Grok CLI sign-ins, Gemini through Antigravity, and OpenCode or other ACP agents on their own login (beta). Model or effort can change mid-session without discarding the transcript.

   Locator

   Supported providers; Switch models

   Retrieved

   2026-11-08

3. Happy: Harnesses: Claude Code, Codex CLI, Antigravity, OpenCode, and ACP agents

   Finding: Happy's own harness runs the loop by default; the claude_code harness runs Claude Code itself on a claude account and codex_cli does the same for Codex, while Antigravity, OpenCode and other ACP agents sign in themselves. Grok is not listed as a harness.

   Locator

   Harnesses

   Retrieved

   2026-11-08

4. Happy Antigravity support at v2026.11.4

   Finding: Happy Agent v2026.11.4 runs the Antigravity whole-agent harness through antigravity-acp@1.2.0, a community ACP adapter driving the signed-in agy CLI.

   Locator

   packages/happy-providers/sources/vendors/foreignAgents/antigravityAgent.ts lines 30-63, v2026.11.4, commit db813011c038b2288fbc1efd0e10ef2149c838d2

   Retrieved

   2026-11-10

   Source date

   2026-11-10

happy:ACC-03

Happy reuses existing Claude Code, Codex and Grok CLI sign-ins and their subscriptions; Antigravity and ACP agents use their own login. Bedrock API keys or the AWS credential chain are supported.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Models and Subscriptions

   Finding: Happy uses existing Claude Code, Codex and Grok CLI sign-ins, so no Happy plan or pasted key is needed for model access; Antigravity and ACP agents use their own login. Bedrock works with an API key or the AWS credential chain.

   Locator

   Models and Subscriptions

   Retrieved

   2026-11-08

happy:ACC-04

Importing registers an existing folder without moving, copying or initializing Git. A project without Git uses a plain folder copy when a workspace is needed.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Add a project

   Finding: Importing registers an existing folder without moving, copying or initializing Git. A project without Git uses a plain folder copy when a workspace is needed.

   Locator

   Add a project

   Retrieved

   2026-11-08

happy:ACC-05

Happy Agent exposes a token-authenticated REST API for sessions, streaming events and control on user infrastructure. The original happy CLI is a separate product-owned terminal entry point.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: REST API

   Finding: Happy Agent exposes a token-authenticated REST API for sessions, streaming events and control on user infrastructure. The original happy CLI is a separate product-owned terminal entry point.

   Locator

   REST API

   Retrieved

   2026-11-08

happy:ACC-06

Skills are SKILL.md files and MCP servers are mcp.toml entries; agents can write both. MCP tools need Auto or Full access, every Auto call is reviewed, and MCP servers run outside the OS sandbox.

Checked

2026-11-08 · checked 1 week ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Skills and MCP

   Finding: Skills are SKILL.md files and MCP servers are mcp.toml entries, shared by every model; an agent can write both. MCP tools need Auto or Full access and every Auto call is reviewed. MCP servers from Codex or Claude Code configuration are not imported.

   Locator

   Skills and MCP

   Retrieved

   2026-11-08

2. Happy: What the OS sandbox enforces

   Finding: The documented OS sandbox uses macOS Seatbelt or Linux namespaces and seccomp. Shell writes, network and host sockets are restricted; file tools can still read credential folders, and MCP servers run outside the sandbox. Docker-backed sessions nest that sandbox inside the container.

   Locator

   What the OS sandbox enforces

   Retrieved

   2026-11-08

happy:PLAN-01

The built-in Chief of Staff handles setup and task creation through ordinary conversation, including projects, remote hosts and teams. Persistent standalone issue metadata is not established.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Chief of Staff

   Finding: The built-in Chief of Staff handles setup and task creation through ordinary conversation, including projects, remote hosts and teams. Persistent standalone issue metadata is not established.

   Locator

   Chief of Staff

   Retrieved

   2026-11-08

happy:PLAN-03

Subagent trees are capped at depth three and at most five agents including finished children. Sessions have exact agent IDs for messaging and retained follow-up. This is session hierarchy, not verified issue dependency enforcement.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Subagents

   Finding: Subagent trees are capped at depth three and at most five agents including finished children. Sessions have exact agent IDs for messaging and retained follow-up. This is session hierarchy, not verified issue dependency enforcement.

   Locator

   Subagents

   Retrieved

   2026-11-08

happy:PLAN-04

AGENTS.md files in the project tree are read by each agent and reread when they change; global AGENTS.md applies across projects.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Add a project

   Finding: AGENTS.md files in the project tree are read by each agent and reread when they change; global AGENTS.md applies across projects.

   Locator

   Add a project

   Retrieved

   2026-11-08

happy:PLAN-06

Happy creates persistent task records through its API, agent tool and Desktop UI. Native task operations rename task records. Creating a task without opening text stores an idle draft. The task catalog has a task ID separate from its linked agent and workspace IDs; each task has one root conversation. Task state is persisted as active or archived with restoration and versioned updates. Task archival persists and stops the task agent and descendants. Native unarchive restores an archived task.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Happy Agent v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2), Desktop v0.0.103 (a369b7b0a86a344904a2e171a78e2b0daf0b4be8); targeted first-party pass 2026-11-13; no installed-product test

• The scoped first-party source pass does not establish discuss, prioritize, label, assign, search, filter, project_epic_views, explicit_dispatch, metadata, external_tracker_requirement. No hands-on scenario was run.

1. Happy task catalog schema at v2026.11.4

   Finding: Task records have independent task, agent and workspace IDs, owner and creator fields, versioned active/archived state and timestamps. Creation accepts no opening text, allowing an idle draft before work starts.

   Locator

   Task record schema and createTaskInputSchema, lines 28-151

   Retrieved

   2026-11-13

2. Happy native task operations at v2026.11.4

   Finding: The TasksModule creates distinct task and agent records, supports rename, join, reorder, archive and unarchive, and persists catalog state. The API and Desktop task creation surface expose the task catalog.

   Locator

   createWithResult and task archive/unarchive operations; corresponding TaskMigrations.ts table

   Retrieved

   2026-11-13

happy:COORD-01

Subagents run in the background by default and return completion to the parent. Desktop displays subagents and running tools; tree size is bounded.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Subagents; What Happy Desktop shows

   Finding: Subagents run in the background by default and return completion to the parent. Desktop displays subagents and running tools; tree size is bounded.

   Locator

   Subagents; What Happy Desktop shows

   Retrieved

   2026-11-08

happy:COORD-02

Bots and their subtasks may create a full conversation in a new workspace, with the creator as coordinator. Only the creating session may archive that workspace.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: How agents work in another workspace

   Finding: Bots and their subtasks may create a full conversation in a new workspace, with the creator as coordinator. Only the creating session may archive that workspace.

   Locator

   How agents work in another workspace

   Retrieved

   2026-11-08

happy:COORD-03

Agents delegate bounded work, choose each child model and effort, receive background completion notices and send follow-ups to finished children with retained context. Exact IDs route messages across projects or machines.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Subagents; How agents message each other

   Finding: Agents delegate bounded work, choose each child model and effort, receive background completion notices and send follow-ups to finished children with retained context. Exact IDs route messages across projects or machines.

   Locator

   Subagents; How agents message each other

   Retrieved

   2026-11-08

happy:COORD-04

Primary sessions can schedule messages to known agent IDs, list or cancel them and survive intervening runtime restarts. Durable waits end early on new input. This establishes scheduled work, not an unrestricted external-event scheduler.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Durable waits and scheduled messages

   Finding: Primary sessions can schedule messages to known agent IDs, list or cancel them and survive intervening runtime restarts. Durable waits end early on new input. This establishes scheduled work, not an unrestricted external-event scheduler.

   Locator

   Durable waits and scheduled messages

   Retrieved

   2026-11-08

happy:COORD-05

Agent questions remain in the conversation and experimental Inbox; answering on one device closes the shared state. Away presence instructs agents to continue with notes instead of waiting indefinitely.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Inbox and presence

   Finding: Agent questions remain in the conversation and experimental Inbox; answering on one device closes the shared state. Away presence instructs agents to continue with notes instead of waiting indefinitely.

   Locator

   Inbox and presence

   Retrieved

   2026-11-08

happy:COORD-06

Per-session UI shows phase, tools, background processes, subagents, waiting state, whole-tree token usage and changed files. Fleet navigation has not been measured.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: What Happy Desktop shows

   Finding: Per-session UI shows phase, tools, background processes, subagents, waiting state, whole-tree token usage and changed files. Fleet navigation has not been measured.

   Locator

   What Happy Desktop shows

   Retrieved

   2026-11-08

happy:COORD-07

The built-in Chief of Staff configures accounts, imports projects, pairs phones, deploys remote agents and creates teams through conversation.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: What you get

   Finding: The built-in Chief of Staff configures accounts, imports projects, pairs phones, deploys remote agents and creates teams through conversation.

   Locator

   What you get

   Retrieved

   2026-11-08

happy:RUN-01

Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Remote server

   Finding: Happy Agent can run on an always-on user server while Desktop connects over Tailcat and phones connect through an encrypted relay. Closing the controlling laptop does not stop work on that reachable host. Users supply host compute.

   Locator

   Remote server

   Retrieved

   2026-11-08

happy:RUN-02

Parallel workspaces use Git worktrees on branches cut from the remote trunk. File sync and setup commands run per workspace; nongit projects use a plain copy. The documented OS sandbox uses macOS Seatbelt or Linux namespaces and seccomp. Shell writes, network and host sockets are restricted; file tools can still read credential folders, and MCP servers run outside the sandbox. Docker-backed sessions nest that sandbox inside the container. No VM or microVM isolation backend exists in the inspected runtime; local OS sandboxing and Docker are separate options.

Checked

2026-11-08 · checked 1 week ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Happy Agent v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2), Desktop v0.0.103 (a369b7b0a86a344904a2e171a78e2b0daf0b4be8); targeted first-party pass 2026-11-13; no installed-product test

• The scoped first-party source pass does not establish checkout, process. No hands-on scenario was run.

1. Happy: How Happy creates a workspace

   Finding: Parallel workspaces use Git worktrees on branches cut from the remote trunk. File sync and setup commands run per workspace; nongit projects use a plain copy.

   Locator

   How Happy creates a workspace

   Retrieved

   2026-11-08

2. Happy: What the OS sandbox enforces

   Finding: The documented OS sandbox uses macOS Seatbelt or Linux namespaces and seccomp. Shell writes, network and host sockets are restricted; file tools can still read credential folders, and MCP servers run outside the sandbox. Docker-backed sessions nest that sandbox inside the container.

   Locator

   What the OS sandbox enforces

   Retrieved

   2026-11-08

3. Happy execution configuration at v2026.11.4

   Finding: The scoped runtime config and runner implementation provide host process execution and optional Docker image/container execution, with OS sandbox restrictions. No VM or microVM isolation backend is implemented in the inspected release. A user provisioning a host VM is separate.

   Locator

   Docker configuration lines 261-272; sources/runners and runtime inspection; search terms docker, virtual machine, microvm

   Retrieved

   2026-11-13

happy:RUN-03

Conversations and child sessions persist across window closure and runtime restart; finished children accept follow-ups with their full context. This is a documentation claim, not a crash test.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Agents That Never Die

   Finding: Conversations and child sessions persist across window closure and runtime restart; finished children accept follow-ups with their full context. This is a documentation claim, not a crash test.

   Locator

   Agents That Never Die

   Retrieved

   2026-11-08

happy:RUN-04

New workspaces copy configured sync files and run setup_commands. They start with a cold build cache. A failed setup command logs a warning while checkout and file sync determine readiness.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: How Happy creates a workspace

   Finding: New workspaces copy configured sync files and run setup_commands. They start with a cold build cache. A failed setup command logs a warning while checkout and file sync determine readiness.

   Locator

   How Happy creates a workspace

   Retrieved

   2026-11-08

happy:RUN-05

Smart provider pools can rotate same-provider accounts after authentication or quota-exhaustion errors. Provider quotas are polled about every fifteen minutes and are observations rather than billing records.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Use several accounts; Provider usage and quotas

   Finding: Smart provider pools can rotate same-provider accounts after authentication or quota-exhaustion errors. Provider quotas are polled about every fifteen minutes and are observations rather than billing records.

   Locator

   Use several accounts; Provider usage and quotas

   Retrieved

   2026-11-08

happy:RUN-06

Session status includes active tools, background work, subagents, waiting state, tokens and changed files. Deliberate failure and approval consistency after reconnect remain untested.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: What Happy Desktop shows

   Finding: Session status includes active tools, background work, subagents, waiting state, tokens and changed files. Deliberate failure and approval consistency after reconnect remain untested.

   Locator

   What Happy Desktop shows

   Retrieved

   2026-11-08

happy:RUN-07

Provider quotas are polled about every fifteen minutes and shown in the app; they are observations, not billing records.

Checked

2026-11-08 · checked 1 week ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Provider usage and quotas

   Finding: Provider quotas are polled about every fifteen minutes and shown in the app; they are observations, not billing records.

   Locator

   Provider usage and quotas

   Retrieved

   2026-11-08

happy:TEAM-01

Team members see the same projects and sessions and can speak to the agent. Changes in speaker include the member name/email; per-member drafts and task ordering stay personal.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Shared work

   Finding: Team members see the same projects and sessions and can speak to the agent. Changes in speaker include the member name/email; per-member drafts and task ordering stay personal.

   Locator

   Shared work

   Retrieved

   2026-11-08

happy:TEAM-02

Team mode verifies per-user WorkOS tokens. The owner alone renames the installation, toggles global skills or archives others tasks; members otherwise have equal access and can select Full access. A remove-member action is explicitly not built yet.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Owner; Sign-in; Leaving

   Finding: Team mode verifies per-user WorkOS tokens. The owner alone renames the installation, toggles global skills or archives others tasks; members otherwise have equal access and can select Full access. A remove-member action is explicitly not built yet.

   Locator

   Owner; Sign-in; Leaving

   Retrieved

   2026-11-08

2. Happy website source: Set up enterprise JWT sign-in

   Finding: Recipe for a team-mode Happy Agent whose members sign in through the organization's own identity provider (Okta, Entra ID, Google Workspace, Keycloak or internal SSO) instead of Happy's WorkOS accounts; the daemon verifies JWTs from an organization-owned OAuth authorization server and needs an Agent release with enterprise JWT authentication.

   Locator

   content/desktop/recepies/enterprise-sign-in.mdx lines 1-15, commit 275790d

   Retrieved

   2026-11-10

3. Happy Agent TeamJwtConfig at release v2026.11.4

   Finding: The released Happy Agent v2026.11.4 parses a [feature.team.jwt] machine configuration with an authorization URL and exactly one of a JWKS URL, public key or secret, used to verify organization-issued team tokens.

   Locator

   packages/happy-agent-modules/sources/config/TeamJwtConfig.ts lines 47-140, tag v2026.11.4 (commit db81301)

   Retrieved

   2026-11-10

4. Happy Desktop server sign-in discovery at release v0.0.103

   Finding: The released desktop app v0.0.103 queries a Happy Agent server's v0/authentication endpoint to discover its sign-in methods.

   Locator

   packages/happy-desktop-electron/sources/main/serverSessions.ts line 318, tag v0.0.103 (commit a369b7b)

   Retrieved

   2026-11-10

happy:TEAM-03

Read only, Workspace write, Auto and Full access share a permission model. Auto sends boundary-crossing actions to a separate read-only reviewer and grants only that execution if allowed. Reads and workspace edits are not reviewed.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Four permission modes; Auto review

   Finding: Read only, Workspace write, Auto and Full access share a permission model. Auto sends boundary-crossing actions to a separate read-only reviewer and grants only that execution if allowed. Reads and workspace edits are not reviewed.

   Locator

   Four permission modes; Auto review

   Retrieved

   2026-11-08

happy:TEAM-04

Session transcripts retain provider-specific opaque data; compaction creates a visible message describing replaced content. No immutable audit retention guarantee was verified.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Switch models; How compaction works

   Finding: Session transcripts retain provider-specific opaque data; compaction creates a visible message describing replaced content. No immutable audit retention guarantee was verified.

   Locator

   Switch models; How compaction works

   Retrieved

   2026-11-08

happy:TEAM-05

The desktop interface has conversations, files, diffs and an attachable terminal; current docs describe changed files beside each conversation. Guided batch review was not established.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Initial core release; Current interface

   Finding: The desktop interface has conversations, files, diffs and an attachable terminal; current docs describe changed files beside each conversation. Guided batch review was not established.

   Locator

   Initial core release; Current interface

   Retrieved

   2026-11-08

happy:TEAM-06

Named teammates operate on shared sessions and projects on the same team server. This is not a verified transfer preserving every permission and runtime detail after owner disconnect.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Shared work

   Finding: Named teammates operate on shared sessions and projects on the same team server. This is not a verified transfer preserving every permission and runtime detail after owner disconnect.

   Locator

   Shared work

   Retrieved

   2026-11-08

happy:SHIP-01

Happy Desktop shows files and diffs with conversations, and its documentation includes a recipe for a live, shared HTML artifact. No exact-revision cross-task gallery test was run.

Checked

2026-11-08 · checked 1 week ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Initial core release; Current interface

   Finding: The desktop interface has conversations, files, diffs and an attachable terminal; current docs describe changed files beside each conversation. Guided batch review was not established.

   Locator

   Initial core release; Current interface

   Retrieved

   2026-11-08

2. Happy: Artifacts

   Finding: The Chief of Staff documentation links a recipe for building a live, shared HTML artifact. No exact-revision cross-task gallery test was run.

   Locator

   Artifacts

   Retrieved

   2026-11-08

happy:SHIP-03

The pinned runtime and clients manage Git workspaces and file changes. They have no built-in PR creation or management path; users can ask a coding agent to use external shell or MCP tools.

Checked

2026-11-13 · checked 2 days ago

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Happy Agent v2026.11.4 (db813011c038b2288fbc1efd0e10ef2149c838d2), Desktop v0.0.103 (a369b7b0a86a344904a2e171a78e2b0daf0b4be8); targeted first-party pass 2026-11-13; no installed-product test

• The scoped first-party source pass does not establish branches, worktrees, commits, comments, ci_response, rebase, conflicts, product_state. No hands-on scenario was run.

1. Happy Git module and bounded PR integration inspection

   Finding: The pinned runtime Git module and clients provide file changes, branches and workspaces, but no product-owned pull-request creation or management path was found. PRs can still be operated through an external shell command or MCP service; that is not a built-in Happy PR workflow.

   Locator

   GitModule.ts and sibling sources/git, sources/api, sources/tasks; happy-desktop AppHappyAgentView.tsx at a369b7b; happy CLI/iOS/Android sources at df13fc0. Searches: pull request, pull_request, gh pr, pr create.

   Retrieved

   2026-11-13

happy:OWN-01

The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: MIT License

   Finding: The mobile app, original CLI and relay repository has the MIT license. Happy Desktop documentation also explicitly describes its app/runtime as MIT. Hosted and provider services remain separate.

   Locator

   MIT License

   Retrieved

   2026-11-08

happy:OWN-02

The core Happy Agent runs self-hosted on user machines or servers, with Desktop connecting remotely. Happy Social/WorkOS team sign-in and the mobile relay are distinct service dependencies.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: How a Happy team server works

   Finding: The core Happy Agent runs self-hosted on user machines or servers, with Desktop connecting remotely. Happy Social/WorkOS team sign-in and the mobile relay are distinct service dependencies.

   Locator

   How a Happy team server works

   Retrieved

   2026-11-08

happy:OWN-03

Happy apps send pseudonymous usage events to PostHog, excluding message content, prompts, code and file names, and offer a Settings opt-out that stops them; the desktop app has its own switch. Happy Agent itself sends no analytics.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-10

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: Analytics: PostHog

   Finding: Happy apps send pseudonymous product usage events to PostHog, excluding message content, prompts, code and file names, and offer a Settings opt-out that stops them; the desktop app has its own switch. Happy Agent itself sends no analytics.

   Locator

   Analytics: PostHog

   Retrieved

   2026-11-08

happy:OWN-04

Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: What does Happy cost?

   Finding: Happy is free and MIT licensed. Model use is paid through existing subscriptions and user compute. Phone voice has twenty free minutes per thirty days and an optional paid allowance; custom ElevenLabs use is separate.

   Locator

   What does Happy cost?

   Retrieved

   2026-11-08

happy:OWN-06

Happy Agent v0.4.108 adds GPT-6.1 Terra and stop-state persistence; Desktop v0.0.102 has opt-in beta Stem cells. Current release activity does not imply all experimental UI is enabled by default.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: October 26, 2026

   Finding: Happy Agent v0.4.108 adds GPT-6.1 Terra and stop-state persistence; Desktop v0.0.102 has opt-in beta Stem cells. Current release activity does not imply all experimental UI is enabled by default.

   Locator

   October 26, 2026

   Retrieved

   2026-11-08

   Source date

   2026-10-26

happy:OWN-08

The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: What does Happy cost?

   Finding: The desktop application and self-hosted runtime are free. Model subscriptions and host compute are separate costs; optional phone voice has its own allowance.

   Locator

   What does Happy cost?

   Retrieved

   2026-11-08

happy:OWN-09

The core ADE has no software subscription charge; coding-model subscriptions, host resources and optional voice are separately scoped. No standardized task-scenario total was invented.

Checked

2026-11-08 · checked 1 week ago

Cross-check

cross-checked 2026-11-08

Plan

Not specified in this finding

Surface

Happy Desktop with Happy Agent runtime; native mobile apps, original CLI and self-hosted team mode where named

Version

Public documentation retrieved 2026-11-08

• Documentation evidence only. Remaining atomic questions and enforcement under failure have not been established by a bounded workflow test.

1. Happy: What does Happy cost?

   Finding: The core ADE has no software subscription charge; coding-model subscriptions, host resources and optional voice are separately scoped. No standardized task-scenario total was invented.

   Locator

   What does Happy cost?

   Retrieved

   2026-11-08