# Use KITCHEN COURT with an existing assistant

> For an already-installed Mac. For download, package installation, joining phones and getting online, start with [Install KITCHEN COURT](https://kitchencourt.coachcommandcenter.com/install.md). Do not treat this page as a second installer.

KITCHEN COURT gives the household’s existing native Claude, Codex and Grok access to its TV, phones and creative tools. It is not its own AI model. The provider must be installed and signed in through its normal vendor flow; local play and media remain useful without an AI provider.

## Inspect before changing anything

The normal graphical entry is `/Applications/KITCHEN COURT.app`; reopen it from Applications/Spotlight if the TV is not showing KITCHEN COURT. House settings live on an owner’s phone (the initial in the top-right corner, then **Settings**). The fixed private helpers below are included by the installer; they are not commands to download from the web and are not installed in /usr/local/bin.

An authorized local assistant can execute these argument arrays directly (the executable path contains spaces):

~~~json
["/Library/Application Support/KITCHEN COURT/bin/homie-setup", "status", "--provider-probe", "off"]
["/Library/Application Support/KITCHEN COURT/bin/homie-provider", "status", "--provider", "claude", "--json"]
["/Library/Application Support/KITCHEN COURT/bin/homie-provider", "status", "--provider", "codex", "--json"]
["/Library/Application Support/KITCHEN COURT/bin/homie-provider", "status", "--provider", "grok", "--json"]
["/Library/Application Support/KITCHEN COURT/bin/homie-settings", "status"]
~~~

These are status checks, not consent to configure the house. Do not paste raw private configuration files or credentials into the reply. Explain unavailable/missing/signed-out states honestly. Do not invoke provider login, integration tests, replacement settings, telemetry changes or an owner recovery operation merely because a status check failed. Use the normal UI for browser sign-in, macOS permissions, owner pairing and secret fields.

## Workspace MCP and skills

The usual local workspace is `~/.homie/workspace` in the installed console account. Start by reading the workspace’s own `AGENTS.md` and `MAKING.md` when present, then the relevant bundled skill. Native authoring may use a managed task directory under `~/.homie/bench`; follow the actual task paths supplied by KITCHEN COURT rather than moving an existing creation.

KITCHEN COURT prepares project-local MCP configuration: Claude’s `.mcp.json`, Codex’s `.codex/config.toml`, and Grok’s `.grok/config.toml` in the workspace. Bundled skills live under `skills/` and are exposed through the providers’ workspace skill directories. Do not hand-copy a token, add a global MCP server, replace the person’s existing provider configuration, or install a second copy of a bundled skill.

The project connection uses KITCHEN COURT’s local stdio bridge. Native task identity is passed by KITCHEN COURT, not shared between players by editing a config file. Depending on the provider, normal registration may add trust for this exact workspace to the provider’s user-level trust records, respecting an explicit distrust decision. That is distinct from installing a global MCP server. KITCHEN COURT also handles migration of its own legacy global entry; do not perform an unrelated global cleanup.

Use the actual tool schemas returned by the connected MCP server. For example, Guide offers explicit player-count filtering and returns rows the normal TV press action can select; let the model choose parameters from the current schema rather than guessing package IDs. For creation, use the bundled creator workflow and the normal preview/test/Keep/Undo controls. A preview is not a kept game; a model claiming success is not an install receipt.

## Settings, help and privacy

Use an owner phone’s **Settings** (the initial in the top-right corner) for connections and owner actions, and **Help & feedback** in the same place for an issue or idea. Optional services are not setup prerequisites. Diagnostics are opt-in; usage reports are off until an owner turns them on. Never automatically attach household logs, conversations or private game cards.

[Privacy](https://kitchencourt.coachcommandcenter.com/privacy/) · [Terms](https://kitchencourt.coachcommandcenter.com/terms/) · [AI documentation index](https://kitchencourt.coachcommandcenter.com/llms.txt)