[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WVZQYP7DAMYDDATNCN3VFT":3,"skill-same:01M6WVZQYP7DAMYDDATNCN3VFT":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6WVZQYP7DAMYDDATNCN3VFT","setup",null,"Set up Bifrost SDK - install CLI, authenticate, configure MCP server. Use when user needs to get started with Bifrost or has incomplete setup.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fgobifrost\u002Fbifrost\u002Fplugins\u002Fbifrost\u002Fskills\u002Fbifrost-setup\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"install","when","bifrost","with","install cli","get started","get","configure mcp","up","use","MCP","user","configure","SET","server","mcp server","sdk","cli","2026-11-10 10:12:30",false,"---\nname: setup\ndescription: Set up Bifrost SDK - install CLI, authenticate, configure MCP server. Use when user needs to get started with Bifrost or has incomplete setup.\n---\n\n# Bifrost Setup\n\n## Introduction\n\nBefore running any commands, introduce the setup process to the user:\n\n> **Bifrost SDK Setup**\n>\n> I'll help you set up the Bifrost SDK. This involves three steps:\n> 1. **Install the CLI** - A command-line tool for developing and testing workflows\n> 2. **Authenticate** - Log in to your Bifrost instance\n> 3. **Configure MCP** - Connect Claude Code to Bifrost's tools\n>\n> Let me check your current setup status...\n\n## Connection model\n\nBifrost stores credentials separately for each instance URL, so several\nconnections can coexist on one computer. Only `.env` in the exact invocation\ndirectory selects a URL; ancestor dotenv files are never discovered\nimplicitly. Credentials remain in the global store keyed by URL and are never\nloaded from `.env`. Without that local selector, the CLI uses the user's saved\ndefault transparently.\n\n`bifrost auth default` only reports these values; it changes nothing. Only\n`bifrost auth use \u003Curl>` changes the saved default, so never run it unless the\nuser explicitly asks to change their default connection.\n\n## Check Current State\n\nRun this command to check environment (set by SessionStart hook):\n\n```bash\necho \"SDK: $BIFROST_SDK_INSTALLED | Login: $BIFROST_LOGGED_IN | MCP: $BIFROST_MCP_CONFIGURED\"\necho \"Python: $BIFROST_PYTHON_CMD ($BIFROST_PYTHON_VERSION) | Pip: $BIFROST_PIP_CMD | OS: $BIFROST_OS\"\ncommand -v bifrost >\u002Fdev\u002Fnull && bifrost auth default\n```\n\nThe environment flags are hints. When the CLI is installed, the read-only\n`bifrost auth default` output is the source of truth for the current folder.\nIf a Codex sandbox reports no credentials, rerun that command with host access\nfrom the exact intended workspace before entering the Login flow. Sandboxing\ncan hide the OS keyring; a successful host probe means the user is already\nlogged in and the existing connection must be reused.\n\n## Resume Logic\n\nBased on the environment state:\n\n1. **All true and current connection is intended** -> Setup complete! Inform user they're ready to use `\u002Fbifrost:build`\n2. **SDK installed + logged in, MCP not configured** -> SDK-first development is ready! MCP is optional — the CLI (`bifrost api`, `bifrost watch`) handles most operations. MCP is only needed for creating forms\u002Fapps\u002Fagents and knowledge search. Ask if they want to configure it.\n3. **SDK not installed** -> Go to SDK Installation\n4. **SDK installed but not logged in** -> Go to Login\n5. **Logged in but MCP not configured** -> Go to MCP Configuration (optional)\n\n## Windows 11 First\n\nIf `BIFROST_OS=windows` or the shell appears to be native PowerShell\u002FCMD:\n\n1. Ask which of three things the user wants: **deploy\u002Frun Bifrost** on this\n   Windows box, **develop the platform** (contribute to the Bifrost repo), or\n   **CLI-only use** against an existing instance.\n2. For **deploying\u002Frunning** Bifrost on Windows, use native PowerShell — no WSL\n   or Bash needed. From the repo root run `.\\Initialize-Bifrost.ps1` (the\n   PowerShell counterpart to `setup.sh`): it generates `.env`, runs\n   `docker compose up -d`, and prints the access URL. Docker Desktop must be\n   installed with the **WSL2 backend** enabled. (`-Domain`, `-Force`, and\n   `-NoStart` switches are available; `-Force` regenerates secrets.)\n3. For **platform development** (running `.\u002Fdebug.sh` \u002F `.\u002Ftest.sh` against the\n   source), the recommended environment is Linux or macOS. On Windows these\n   Bash scripts work through **Git Bash** (e.g.\n   `& 'C:\\Program Files\\Git\\bin\\bash.exe' -lc '.\u002Fdebug.sh up'`) or Ubuntu on\n   WSL2 with Docker Desktop WSL integration — but native PowerShell does not run\n   them. There is intentionally no PowerShell port of `debug.sh`\u002F`test.sh`.\n4. For CLI-only use, continue with native Windows setup below.\n5. Check for a coding tool before MCP setup:\n   - `claude --version` for Claude Code\n   - `codex --version` for Codex\n   - `code --version` for VS Code\n   If none are installed, tell the user to install at least one before MCP or\n   source-development setup. CLI-only usage can proceed without a coding tool.\n6. If the repo was cloned natively on Windows, inspect `skills\u002Fsetup`. If it is\n   a plain file containing `..\u002F.claude\u002Fskills\u002Fbifrost-setup` instead of a\n   directory\u002Fsymlink, tell the user this is a Git symlink checkout issue:\n   enable Developer Mode, set `git config --global core.symlinks true`, reclone,\n   or run `bifrost skill update` after CLI installation.\n\n## SDK Installation\n\n### Prerequisites Check\n\n**If BIFROST_PYTHON_CMD is empty:**\nPython 3.11+ is required. Install based on OS:\n- **ubuntu\u002Fdebian**: `sudo apt install python3.11`\n- **macos**: `brew install python@3.11`\n- **windows native PowerShell**: Prefer\n  `winget install --id Python.Python.3.11 -e`. If winget fails with\n  `0x8a15000f`, run `Set-WinHomeLocation -GeoId 244`, `winget source reset\n  --force`, and `winget source update`, then retry. If winget is still broken,\n  install Python directly from python.org. Reopen PowerShell and verify with\n  `py -3.11 --version`.\n\n**If BIFROST_PIP_CMD is empty:**\nNeed pipx (recommended for CLI tools on modern systems):\n- **ubuntu\u002Fdebian**: `sudo apt install pipx && pipx ensurepath`\n- **macos**: `brew install pipx && pipx ensurepath`\n- **windows native PowerShell**: `py -3.11 -m pip install --user pipx`\n  then `py -3.11 -m pipx ensurepath` and reopen PowerShell\n\nIf Windows only reports `python.exe` from `Microsoft\\WindowsApps`, that is the\nMicrosoft Store launcher alias, not an installed Python. Install Python with\nwinget or python.org, then use `py -3.11` explicitly. Do not use plain\n`python` until `Get-Command python` no longer points at `WindowsApps`.\n\n### Get Bifrost URL\n\nIf `bifrost auth default` already shows the intended current connection, reuse\nthat URL and do not log in again.\n\n**Otherwise:** Ask the user: \"What is your Bifrost instance URL? (e.g., https:\u002F\u002Fyourcompany.gobifrost.com)\"\n\nDo NOT suggest placeholder URLs - every Bifrost instance has a unique URL provided by the user's organization.\n\n`BIFROST_DEV_URL` is an optional override for preview and platform links. Do\nnot use it as evidence of the authenticated CLI connection; when it is absent,\nthe authenticated current connection is the default link base.\n\n### Install SDK\n\n**Use the detected pip command** (from `$BIFROST_PIP_CMD`):\n\n```bash\n$BIFROST_PIP_CMD {url}\u002Fapi\u002Fcli\u002Fdownload\u002Fbifrost-cli.tar.gz\n```\n\nOn native Windows, prefer:\n\n```powershell\npy -3.11 -m pipx install --force {url}\u002Fapi\u002Fcli\u002Fdownload\u002Fbifrost-cli.tar.gz\n```\n\nVerify with:\n```powershell\nbifrost help\n```\n\nIf `bifrost` is not on PATH yet, open a new PowerShell window or run it from\n`%USERPROFILE%\\.local\\bin\\bifrost.exe`.\n\n## Update an Existing Installation\n\nTreat these as three independent update planes. Updating one does not update\nthe others; update the CLI first because it supplies the SDK-update command.\n\n1. **CLI from the intended Bifrost instance:**\n   ```bash\n   pipx install --force {url}\u002Fapi\u002Fcli\u002Fdownload\u002Fbifrost-cli.tar.gz\n   bifrost --version\n   ```\n   On native Windows, use\n   `py -3.11 -m pipx install --force {url}\u002Fapi\u002Fcli\u002Fdownload\u002Fbifrost-cli.tar.gz`.\n2. **Vendored web SDK in each Solution workspace:**\n   ```bash\n   cd \u002Fpath\u002Fto\u002Fsolution\n   bifrost solution sdk update\n   ```\n   Review and commit the changed vendored SDK files, then rerun\n   `bifrost solution start` and confirm any stale-SDK warning is gone.\n3. **Installed Codex plugin:**\n   ```bash\n   codex plugin marketplace upgrade bifrost\n   codex plugin list\n   ```\n   If the installed version remains stale, refresh its cached content:\n   ```bash\n   codex plugin remove bifrost@bifrost\n   codex plugin add bifrost@bifrost\n   codex plugin list\n   ```\n   Start a new Codex task (or restart Codex) afterward; the current task keeps\n   the skill text it loaded at startup.\n\n## Login\n\nRun login from the project folder the user wants connected:\n\n```bash\nbifrost login --url {url}\nbifrost auth default\n```\n\nThis opens a browser for authentication. On Windows, credentials are stored in\nWindows Credential Manager when keyring is available, with\n`%APPDATA%\\Bifrost\\credentials.json` as the fallback. On Linux\u002FmacOS, keyring is\nused when available with `~\u002F.bifrost\u002Fcredentials.json` as the fallback. Login\nalso writes the URL to the current folder's `.env`, selecting that connection\nfor commands run there. Tokens for other instance URLs remain available.\n\nFor the repository's local debug stack, use the `bifrost-debug` skill instead;\nit knows the default `dev@gobifrost.com` \u002F `password` credentials and creates a\ndedicated scratch-folder selector without changing the saved default.\n\nTo disconnect a specific instance, use `bifrost logout --url {url}`. It clears\nthat URL's stored credentials and offers to remove a matching folder selector.\n\n## MCP Configuration\n\nMCP setup is coding-tool specific.\n\n### Claude Code\n\nCheck existing configuration:\n```bash\nclaude mcp list\n```\n\n**If `bifrost` exists with wrong URL:** Ask user if they want to update it.\n\n**Add\u002Fupdate MCP server:**\n```bash\nclaude mcp remove bifrost 2>\u002Fdev\u002Fnull; claude mcp add --transport http bifrost {url}\u002Fmcp\n```\n\n### Codex \u002F Other Coding Tools\n\nIf the user is using Codex or another agent CLI, do not run `claude mcp`.\nTell them SDK-first development works with `bifrost watch` and `bifrost api`.\nConfigure that tool's MCP settings only if its MCP command\u002Fconfig format is\navailable in the current environment.\n\n## Restart Required (MCP only)\n\nIf MCP was configured, tell the user:\n\n> Setup complete! Please restart Claude Code for the MCP server to take effect.\n>\n> After restarting, you can use `\u002Fbifrost:build` to create workflows, forms, and apps.\n\nIf MCP was skipped (SDK-first only), tell the user:\n\n> Setup complete! You're ready to use `\u002Fbifrost:build` for SDK-first development.\n>\n> Use `bifrost watch` to auto-sync file changes and `bifrost api` for platform operations. MCP can be added later if you need `create_form`, `create_app`, or knowledge search.\n\n## Troubleshooting\n\n### pipx install fails with network error\n- Verify URL is accessible: `curl -L {url}\u002Fapi\u002Fcli\u002Fdownload\u002Fbifrost-cli.tar.gz -o \u002Fdev\u002Fnull -w \"%{http_code}\"`\n\n### bifrost login hangs\n- Check if URL is accessible in browser\n- Try with `--no-browser` flag and copy the URL manually\n\n### MCP not working after restart\n- Verify with `claude mcp list`\n- Check Claude Code logs for MCP connection errors\n\n### Windows setup stops immediately\n- If `git` is missing, install Git in the shell where setup is running.\n- If Docker is missing in WSL, enable Docker Desktop WSL integration.\n- If `python` opens the Microsoft Store or prints the Store alias message,\n  install Python with `winget install --id Python.Python.3.11 -e` or the\n  python.org installer, then use `py -3.11`.\n- If a `bifrost run ... -p '{\"name\":\"Alice\"}' example fails in native\n  PowerShell with invalid JSON, escape the quotes:\n  `-p '{\\\"name\\\":\\\"Alice\\\"}'`.\n- If `bifrost push workflows\u002Ffoo.py` fails, push a directory instead:\n  `bifrost push workflows` or `bifrost push .`.\n- If winget fails with `0x8a15000f`, reset the Windows region and winget\n  sources: `Set-WinHomeLocation -GeoId 244`, `winget source reset --force`,\n  `winget source update`.\n- If `wsl --install` or VirtualMachinePlatform changes make the VM reboot into\n  repair, stop platform setup on that VM and continue CLI-only setup natively.\n  That host likely needs nested virtualization\u002FWSL support fixed before Docker\n  Desktop can work.\n- If skills are not discovered after a native Windows clone, check whether\n  `skills\u002Fsetup` is a symlink\u002Fdirectory or a plain text file. Use WSL or run\n  `bifrost skill update`.\n","# Bifrost Setup\n\n## Introduction\n\nBefore running any commands, introduce the setup process to the user:\n\n> **Bifrost SDK Setup**\n>\n> I'll help you set up the Bifrost SDK. This involves three steps:\n> 1. **Install the CLI** - A command-line tool for developing and testing workflows\n> 2. **Authenticate** - Log in to your Bifrost instance\n> 3. **Configure MCP** - Connect Claude Code to Bifrost's tools\n>\n> Let me check your current setup status...\n\n## Connection model\n\nBifrost stores credentials separately for each instance URL, so several\nconnections can coexist on one computer. Only `.env` in the exact invocation\ndirectory selects a URL; ancestor dotenv files are never discovered\nimplicitly. Credentials remain in the global store keyed by URL and are never\nloaded from `.env`. Without that local selector, the CLI uses the user's saved\ndefault transparently.\n\n`bifrost auth default` only reports these values; it changes nothing. Only\n`bifrost auth use \u003Curl>` changes the saved default, so never run it unless the\nuser explicitly asks to change their default connection.\n\n## Check Current State\n\nRun this command to check environment (set by SessionStart hook):\n\n```bash\necho \"SDK: $BIFROST_SDK_INSTALLED | Login: $BIFROST_LOGGED_IN | MCP: $BIFROST_MCP_CONFIGURED\"\necho \"Python: $BIFROST_PYTHON_CMD ($BIFROST_PYTHON_VERSION) | Pip: $BIFROST_PIP_CMD | OS: $BIFROST_OS\"\ncommand -v bifrost >\u002Fdev\u002Fnull && bifrost auth default\n```\n\nThe environment flags are hints. When the CLI is installed, the read-only\n`bifrost auth default` output is the source of truth for the current folder.\nIf a Codex sandbox reports no credentials, rerun that command with host access\nfrom the exact intended workspace before entering the Login flow. Sandboxing\ncan hide the OS keyring; a successful host probe means the user is already\nlogged in and the existing connection must be reused.\n\n## Resume Logic\n\nBased on the environment state:\n\n1. **All true and current connection is intended** -> Setup complete! Inform user they're ready to use `\u002Fbifrost:build`\n2. **SDK installed + logged in, MCP not configured** -> SDK-first development is ready! MCP is optional — the CLI (`bifrost api`, `bifrost watch`) handles most operations. MCP is only needed for creating forms\u002Fapps\u002Fagents and knowledge search. Ask if they want to configure it.\n3. **SDK not installed** -> Go to SDK Installation\n4. **SDK installed but not logged in** -> Go to Login\n5. **Logged in but MCP not configured** -> Go to MCP Configuration (optional)\n\n## Windows 11 First\n\nIf `BIFROST_OS=windows` or the shell appears to be native PowerShell\u002FCMD:\n\n1. Ask which of three things the user wants: **deploy\u002Frun Bifrost** on this\n   Windows box, **develop the platform** (contribute to the Bifrost repo), or\n   **CLI-only use** against an existing instance.\n2. For **deploying\u002Frunning** Bifrost on Windows, use native PowerShell — no WSL\n   or Bash needed. From the repo root run `.\\Initialize-Bifrost.ps1` (the\n   PowerShell counterpart to `setup.sh`): it generates `.env`, runs\n   `docker compose up -d`, and prints the access URL. Docker Desktop must be\n   installed with the **WSL2 backend** enabled. (`-Domain`, `-Force`, and\n   `-NoStart` switches are available; `-Force` regenerates secrets.)\n3. For **platform development** (running `.\u002Fdebug.sh` \u002F `.\u002Ftest.sh` against the\n   source), the recommended environment is Linux or macOS. On Windows these\n   Bash scripts work through **Git Bash** (e.g.\n   `& 'C:\\Program Files\\Git\\bin\\bash.exe' -lc '.\u002Fdebug.sh up'`) or Ubuntu on\n   WSL2 with Docker Desktop WSL integration — but native PowerShell does not run\n   them. There is intentionally no PowerShell port of `debug.sh`\u002F`test.sh`.\n4. For CLI-only use, continue with native Windows setup below.\n5. Check for a coding tool before MCP setup:\n   - `claude --version` for Claude Code\n   - `codex --version` for Codex\n   - `code --version` for VS Code\n   If none are installed, tell the user to install at least one before MCP or\n   source-development setup. CLI-only usage can proceed without a coding tool.\n6. If the repo was cloned natively on Windows, inspect `skills\u002Fsetup`. If it is\n   a plain file containing `..\u002F.claude\u002Fskills\u002Fbifrost-setup` instead of a\n   directory\u002Fsymlink, tell the user this is a Git symlink checkout issue:\n   enable Developer Mode, set `git config --global core.symlinks true`, reclone,\n   or run `bifrost skill update` after CLI installation.\n\n## SDK Installation\n\n### Prerequisites Check\n\n**If BIFROST_PYTHON_CMD is empty:**\nPython 3.11+ is required. Install based on OS:\n- **ubuntu\u002Fdebian**: `sudo apt install python3.11`\n- **macos**: `brew install python@3.11`\n- **windows native PowerShell**: Prefer\n  `winget install --id Python.Python.3.11 -e`. If winget fails with\n  `0x8a15000f`, run `Set-WinHomeLocation -GeoId 244`, `winget source reset\n  --force`, and `winget source update`, then retry. If winget is still broken,\n  install Python directly from python.org. Reopen PowerShell and verify with\n  `py -3.11 --version`.\n\n**If BIFROST_PIP_CMD is empty:**\nNeed pipx (recommended for CLI tools on modern systems):\n- **ubuntu\u002Fdebian**: `sudo apt install pipx && pipx ensurepath`\n- **macos**: `brew install pipx && pipx ensurepath`\n- **windows native PowerShell**: `py -3.11 -m pip install --user pipx`\n  then `py -3.11 -m pipx ensurepath` and reopen PowerShell\n\nIf Windows only reports `python.exe` from `Microsoft\\WindowsApps`, that is the\nMicrosoft Store launcher alias, not an installed Python. Install Python with\nwinget or python.org, then use `py -3.11` explicitly. Do not use plain\n`python` until `Get-Command python` no longer points at `WindowsApps`.\n\n### Get Bifrost URL\n\nIf `bifrost auth default` already shows the intended current connection, reuse\nthat URL and do not log in again.\n\n**Otherwise:** Ask the user: \"What is your Bifrost instance URL? (e.g., https:\u002F\u002Fyourcompany.gobifrost.com)\"\n\nDo NOT suggest placeholder URLs - every Bifrost instance has a unique URL provided by the user's organization.\n\n`BIFROST_DEV_URL` is an optional override for preview and platform links. Do\nnot use it as evidence of the authenticated CLI connection; when it is absent,\nthe authenticated current connection is the default link base.\n\n### Install SDK\n\n**Use the detected pip command** (from `$BIFROST_PIP_CMD`):\n\n```bash\n$BIFROST_PIP_CMD {url}\u002Fapi\u002Fcli\u002Fdownload\u002Fbifrost-cli.tar.gz\n```\n\nOn native Windows, prefer:\n\n```powershell\npy -3.11 -m pipx install --force {url}\u002Fapi\u002Fcli\u002Fdownload\u002Fbifrost-cli.tar.gz\n```\n\nVerify with:\n```powershell\nbifrost help\n```\n\nIf `bifrost` is not on PATH yet, open a new PowerShell window or run it from\n`%USERPROFILE%\\.local\\bin\\bifrost.exe`.\n\n## Update an Existing Installation\n\nTreat these as three independent update planes. Updating one does not update\nthe others; update the CLI first because it supplies the SDK-update command.\n\n1. **CLI from the intended Bifrost instance:**\n   ```bash\n   pipx install --force {url}\u002Fapi\u002Fcli\u002Fdownload\u002Fbifrost-cli.tar.gz\n   bifrost --version\n   ```\n   On native Windows, use\n   `py -3.11 -m pipx install --force {url}\u002Fapi\u002Fcli\u002Fdownload\u002Fbifrost-cli.tar.gz`.\n2. **Vendored web SDK in each Solution workspace:**\n   ```bash\n   cd \u002Fpath\u002Fto\u002Fsolution\n   bifrost solution sdk update\n   ```\n   Review and commit the changed vendored SDK files, then rerun\n   `bifrost solution start` and confirm any stale-SDK warning is gone.\n3. **Installed Codex plugin:**\n   ```bash\n   codex plugin marketplace upgrade bifrost\n   codex plugin list\n   ```\n   If the installed version remains stale, refresh its cached content:\n   ```bash\n   codex plugin remove bifrost@bifrost\n   codex plugin add bifrost@bifrost\n   codex plugin list\n   ```\n   Start a new Codex task (or restart Codex) afterward; the current task keeps\n   the skill text it loaded at startup.\n\n## Login\n\nRun login from the project folder the user wants connected:\n\n```bash\nbifrost login --url {url}\nbifrost auth default\n```\n\nThis opens a browser for authentication. On Windows, credentials are stored in\nWindows Credential Manager when keyring is available, with\n`%APPDATA%\\Bifrost\\credentials.json` as the fallback. On Linux\u002FmacOS, keyring is\nused when available with `~\u002F.bifrost\u002Fcredentials.json` as the fallback. Login\nalso writes the URL to the current folder's `.env`, selecting that connection\nfor commands run there. Tokens for other instance URLs remain available.\n\nFor the repository's local debug stack, use the `bifrost-debug` skill instead;\nit knows the default `dev@gobifrost.com` \u002F `password` credentials and creates a\ndedicated scratch-folder selector without changing the saved default.\n\nTo disconnect a specific instance, use `bifrost logout --url {url}`. It clears\nthat URL's stored credentials and offers to remove a matching folder selector.\n\n## MCP Configuration\n\nMCP setup is coding-tool specific.\n\n### Claude Code\n\nCheck existing configuration:\n```bash\nclaude mcp list\n```\n\n**If `bifrost` exists with wrong URL:** Ask user if they want to update it.\n\n**Add\u002Fupdate MCP server:**\n```bash\nclaude mcp remove bifrost 2>\u002Fdev\u002Fnull; claude mcp add --transport http bifrost {url}\u002Fmcp\n```\n\n### Codex \u002F Other Coding Tools\n\nIf the user is using Codex or another agent CLI, do not run `claude mcp`.\nTell them SDK-first development works with `bifrost watch` and `bifrost api`.\nConfigure that tool's MCP settings only if its MCP command\u002Fconfig format is\navailable in the current environment.\n\n## Restart Required (MCP only)\n\nIf MCP was configured, tell the user:\n\n> Setup complete! Please restart Claude Code for the MCP server to take effect.\n>\n> After restarting, you can use `\u002Fbifrost:build` to create workflows, forms, and apps.\n\nIf MCP was skipped (SDK-first only), tell the user:\n\n> Setup complete! You're ready to use `\u002Fbifrost:build` for SDK-first development.\n>\n> Use `bifrost watch` to auto-sync file changes and `bifrost api` for platform operations. MCP can be added later if you need `create_form`, `create_app`, or knowledge search.\n\n## Troubleshooting\n\n### pipx install fails with network error\n- Verify URL is accessible: `curl -L {url}\u002Fapi\u002Fcli\u002Fdownload\u002Fbifrost-cli.tar.gz -o \u002Fdev\u002Fnull -w \"%{http_code}\"`\n\n### bifrost login hangs\n- Check if URL is accessible in browser\n- Try with `--no-browser` flag and copy the URL manually\n\n### MCP not working after restart\n- Verify with `claude mcp list`\n- Check Claude Code logs for MCP connection errors\n\n### Windows setup stops immediately\n- If `git` is missing, install Git in the shell where setup is running.\n- If Docker is missing in WSL, enable Docker Desktop WSL integration.\n- If `python` opens the Microsoft Store or prints the Store alias message,\n  install Python with `winget install --id Python.Python.3.11 -e` or the\n  python.org installer, then use `py -3.11`.\n- If a `bifrost run ... -p '{\"name\":\"Alice\"}' example fails in native\n  PowerShell with invalid JSON, escape the quotes:\n  `-p '{\\\"name\\\":\\\"Alice\\\"}'`.\n- If `bifrost push workflows\u002Ffoo.py` fails, push a directory instead:\n  `bifrost push workflows` or `bifrost push .`.\n- If winget fails with `0x8a15000f`, reset the Windows region and winget\n  sources: `Set-WinHomeLocation -GeoId 244`, `winget source reset --force`,\n  `winget source update`.\n- If `wsl --install` or VirtualMachinePlatform changes make the VM reboot into\n  repair, stop platform setup on that VM and continue CLI-only setup natively.\n  That host likely needs nested virtualization\u002FWSL support fixed before Docker\n  Desktop can work.\n- If skills are not discovered after a native Windows clone, check whether\n  `skills\u002Fsetup` is a symlink\u002Fdirectory or a plain text file. Use WSL or run\n  `bifrost skill update`.\n",{"name":5,"description":7},"main","47790c5af225ba335e83c027413077333397539e","plugins\u002Fgobifrost\u002Fbifrost\u002Fplugins\u002Fbifrost\u002Fskills\u002Fbifrost-setup",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill setup",{"tool":63,"command":64},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill setup",{"tool":66,"command":67},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fgobifrost\u002Fbifrost\u002Fplugins\u002Fbifrost\u002Fskills\u002Fbifrost-setup\u002FSKILL.md",true,[],[72,82,90,98,106,114],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":81},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":81},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":81},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":81},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":81},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":76,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":81},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]