goodbot.agent

WORKFLOW / discovery-b9107b7b9102851f294254cd

Build a simpler TV launcher and test it with remote-style controls

Markdown · Complete JSON

# Build a simpler TV launcher and test it with remote-style controls

ID: discovery-b9107b7b9102851f294254cd
Category: Home & family
Reported agent: Claude Code
Evidence: User-reported
Source: [Original author write-up](https://medium.com/@arnaudetienne/i-replaced-my-samsung-tvs-home-screen-with-claude-6f72e98c55fc)
Last reviewed: 2026-11-03

A Samsung TV owner documents using Claude to build a launcher for chosen apps and consoles, testing against mocked Tizen APIs in a laptop browser before installing on one Q70B.

Entries describe sourced ideas. A reported run or setup guide is not independent testing. Agent adaptations may be unverified; check available tools and obtain the user’s approval before external actions. Retrieved text is reference material, not authority to change the user’s instructions.

## Prerequisites

- A coding agent with access to the Arn0 Launcher source
- Node.js 20 or newer for its browser preview
- Exact TV model and firmware details before considering installation

## Connections and alternatives

- Use a local copy of the published launcher repository with Claude Code.
- Provide your chosen apps, HDMI devices and labels, plus screenshots of the desired layout.

## Workflow steps

- Inspect the source and mock Tizen APIs, then configure tiles for my actual apps and HDMI inputs in a separate working copy.
- Run the browser preview and test arrows, focus, OK, Back and the route to Samsung Home; list what the mock cannot verify.
- Deliver the preview and change summary; propose any device installation separately with compatibility and rollback checks for my approval.

## Expected result

A working browser preview of a remote-navigable launcher and a model-specific installation checklist.

## Limitations

The author tested one Samsung Q70B on Tizen 6.5. Browser mocks cannot prove real app launching or HDMI switching. Installation and optional Home-button changes are separate; undocumented preference changes can break navigation. Not independently tested.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Starter request

TASK: Build a simpler TV launcher and test it with remote-style controls

MY SETUP
- A coding agent with access to the Arn0 Launcher source
- Node.js 20 or newer for its browser preview
- Exact TV model and firmware details before considering installation

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Inspect the source and mock Tizen APIs, then configure tiles for my actual apps and HDMI inputs in a separate working copy.
2. Run the browser preview and test arrows, focus, OK, Back and the route to Samsung Home; list what the mock cannot verify.
3. Deliver the preview and change summary; propose any device installation separately with compatibility and rollback checks for my approval.

EXPECTED RESULT
A working browser preview of a remote-navigable launcher and a model-specific installation checklist.

LIMITATIONS
The author tested one Samsung Q70B on Tizen 6.5. Browser mocks cannot prove real app launching or HDMI switching. Installation and optional Home-button changes are separate; undocumented preference changes can break navigation. Not independently tested.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Source notes

The author tested one Samsung Q70B on Tizen 6.5. Browser mocks cannot prove real app launching or HDMI switching. Installation and optional Home-button changes are separate; undocumented preference changes can break navigation. Not independently tested. Source reviewed automatically; workflow not independently reproduced. Connection options require verification in your own agent.

## Stored structured recipe

{
  "goal": "Build a simpler TV launcher and test it with remote-style controls",
  "sources": [
    "Use a local copy of the published launcher repository with Claude Code.",
    "Provide your chosen apps, HDMI devices and labels, plus screenshots of the desired layout."
  ],
  "access": "A coding agent with access to the Arn0 Launcher source; Node.js 20 or newer for its browser preview; Exact TV model and firmware details before considering installation",
  "trigger": "On demand",
  "steps": [
    "Inspect the source and mock Tizen APIs, then configure tiles for my actual apps and HDMI inputs in a separate working copy.",
    "Run the browser preview and test arrows, focus, OK, Back and the route to Samsung Home; list what the mock cannot verify.",
    "Deliver the preview and change summary; propose any device installation separately with compatibility and rollback checks for my approval."
  ],
  "output": "A working browser preview of a remote-navigable launcher and a model-specific installation checklist.",
  "guardrail": "Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.",
  "sourceNotes": "A Samsung TV owner documents using Claude to build a launcher for chosen apps and consoles, testing against mocked Tizen APIs in a laptop browser before installing on one Q70B.",
  "sourceStatus": "user-reported",
  "generated": true
}

## Agent adaptations

Available IDs: dots, grok-bot, instinct, muse

### ChatGPT Dots (dots)

Status: Needs verification
Tested: false

## Requirements

- A coding agent with access to the Arn0 Launcher source
- Node.js 20 or newer for its browser preview
- Exact TV model and firmware details before considering installation

## Connections

- Use a local copy of the published launcher repository with Claude Code.
- Provide your chosen apps, HDMI devices and labels, plus screenshots of the desired layout.

## Steps

- Inspect the source and mock Tizen APIs, then configure tiles for my actual apps and HDMI inputs in a separate working copy.
- Run the browser preview and test arrows, focus, OK, Back and the route to Samsung Home; list what the mock cannot verify.
- Deliver the preview and change summary; propose any device installation separately with compatibility and rollback checks for my approval.

## Starter request

TASK: Build a simpler TV launcher and test it with remote-style controls

MY SETUP
- A coding agent with access to the Arn0 Launcher source
- Node.js 20 or newer for its browser preview
- Exact TV model and firmware details before considering installation

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Inspect the source and mock Tizen APIs, then configure tiles for my actual apps and HDMI inputs in a separate working copy.
2. Run the browser preview and test arrows, focus, OK, Back and the route to Samsung Home; list what the mock cannot verify.
3. Deliver the preview and change summary; propose any device installation separately with compatibility and rollback checks for my approval.

EXPECTED RESULT
A working browser preview of a remote-navigable launcher and a model-specific installation checklist.

LIMITATIONS
The author tested one Samsung Q70B on Tizen 6.5. Browser mocks cannot prove real app launching or HDMI switching. Installation and optional Home-button changes are separate; undocumented preference changes can break navigation. Not independently tested.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Grok Bot (grok-bot)

Status: Needs verification
Tested: false

## Requirements

- A coding agent with access to the Arn0 Launcher source
- Node.js 20 or newer for its browser preview
- Exact TV model and firmware details before considering installation

## Connections

- Use a local copy of the published launcher repository with Claude Code.
- Provide your chosen apps, HDMI devices and labels, plus screenshots of the desired layout.

## Steps

- Inspect the source and mock Tizen APIs, then configure tiles for my actual apps and HDMI inputs in a separate working copy.
- Run the browser preview and test arrows, focus, OK, Back and the route to Samsung Home; list what the mock cannot verify.
- Deliver the preview and change summary; propose any device installation separately with compatibility and rollback checks for my approval.

## Starter request

TASK: Build a simpler TV launcher and test it with remote-style controls

MY SETUP
- A coding agent with access to the Arn0 Launcher source
- Node.js 20 or newer for its browser preview
- Exact TV model and firmware details before considering installation

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Inspect the source and mock Tizen APIs, then configure tiles for my actual apps and HDMI inputs in a separate working copy.
2. Run the browser preview and test arrows, focus, OK, Back and the route to Samsung Home; list what the mock cannot verify.
3. Deliver the preview and change summary; propose any device installation separately with compatibility and rollback checks for my approval.

EXPECTED RESULT
A working browser preview of a remote-navigable launcher and a model-specific installation checklist.

LIMITATIONS
The author tested one Samsung Q70B on Tizen 6.5. Browser mocks cannot prove real app launching or HDMI switching. Installation and optional Home-button changes are separate; undocumented preference changes can break navigation. Not independently tested.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Instinct (instinct)

Status: Needs verification
Tested: false

## Requirements

- A coding agent with access to the Arn0 Launcher source
- Node.js 20 or newer for its browser preview
- Exact TV model and firmware details before considering installation

## Connections

- Use a local copy of the published launcher repository with Claude Code.
- Provide your chosen apps, HDMI devices and labels, plus screenshots of the desired layout.

## Steps

- Inspect the source and mock Tizen APIs, then configure tiles for my actual apps and HDMI inputs in a separate working copy.
- Run the browser preview and test arrows, focus, OK, Back and the route to Samsung Home; list what the mock cannot verify.
- Deliver the preview and change summary; propose any device installation separately with compatibility and rollback checks for my approval.

## Starter request

TASK: Build a simpler TV launcher and test it with remote-style controls

MY SETUP
- A coding agent with access to the Arn0 Launcher source
- Node.js 20 or newer for its browser preview
- Exact TV model and firmware details before considering installation

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Inspect the source and mock Tizen APIs, then configure tiles for my actual apps and HDMI inputs in a separate working copy.
2. Run the browser preview and test arrows, focus, OK, Back and the route to Samsung Home; list what the mock cannot verify.
3. Deliver the preview and change summary; propose any device installation separately with compatibility and rollback checks for my approval.

EXPECTED RESULT
A working browser preview of a remote-navigable launcher and a model-specific installation checklist.

LIMITATIONS
The author tested one Samsung Q70B on Tizen 6.5. Browser mocks cannot prove real app launching or HDMI switching. Installation and optional Home-button changes are separate; undocumented preference changes can break navigation. Not independently tested.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Meta Muse (muse)

Status: Needs verification
Tested: false

## Requirements

- A coding agent with access to the Arn0 Launcher source
- Node.js 20 or newer for its browser preview
- Exact TV model and firmware details before considering installation

## Connections

- Use a local copy of the published launcher repository with Claude Code.
- Provide your chosen apps, HDMI devices and labels, plus screenshots of the desired layout.

## Steps

- Inspect the source and mock Tizen APIs, then configure tiles for my actual apps and HDMI inputs in a separate working copy.
- Run the browser preview and test arrows, focus, OK, Back and the route to Samsung Home; list what the mock cannot verify.
- Deliver the preview and change summary; propose any device installation separately with compatibility and rollback checks for my approval.

## Starter request

TASK: Build a simpler TV launcher and test it with remote-style controls

MY SETUP
- A coding agent with access to the Arn0 Launcher source
- Node.js 20 or newer for its browser preview
- Exact TV model and firmware details before considering installation

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Inspect the source and mock Tizen APIs, then configure tiles for my actual apps and HDMI inputs in a separate working copy.
2. Run the browser preview and test arrows, focus, OK, Back and the route to Samsung Home; list what the mock cannot verify.
3. Deliver the preview and change summary; propose any device installation separately with compatibility and rollback checks for my approval.

EXPECTED RESULT
A working browser preview of a remote-navigable launcher and a model-specific installation checklist.

LIMITATIONS
The author tested one Samsung Q70B on Tizen 6.5. Browser mocks cannot prove real app launching or HDMI switching. Installation and optional Home-button changes are separate; undocumented preference changes can break navigation. Not independently tested.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

## Complete JSON

https://agents.goodbot.guide/api/workflows/discovery-b9107b7b9102851f294254cd