scriptoriumadmin/openpetswithchatandmcp
1
0
Fork 0
Code Issues Pull requests 6 Projects Releases Packages Wiki Activity Actions
openpetswithchatandmcp/skills/openpets/workflows/verify-claude.md
OpenPets Dev 6ab3bb64d8 feat(rebrand): rename OpenPets to FamiliarOS and pets to familiars 
- Rename all user-facing and technical identifiers from OpenPets/Pet to FamiliarOS/Familiar.
- Rename packages from @open-pets/* to @familiaros/*; rename install-pet/pet-format packages.
- Rename plugin IDs and directories from openpets.* to familiaros.*.
- Rename IPC namespace from openpets:* to familiaros:* and state filenames from openpets-* to familiaros-* with legacy migration.
- Rename source files (pet-window, built-in-pet, default-pet-controller, etc.) to familiar equivalents.
- Update locales (en, es-419, ja, ko, pt-BR, zh-Hans, zh-Hant) and tray/pet context menu strings.
- Add Familiar naming feature: preference, settings input, tray menu display.
- Update assets and packaging config; all desktop tests pass.
2026-06-17 01:42:08 +00:00

873 B
Raw Permalink Blame History

Verify Claude Code

Use this workflow when the user asks whether Claude Code is connected to FamiliarOS.

Steps

  1. Check Claude is available:
claude --version
  1. Check the FamiliarOS MCP entry:
claude mcp list
claude mcp get familiaros
  1. If configuration is missing, configure it:
familiaros configure --agent claude --familiar <familiar-id> --cwd <project-path> --yes

If the CLI is not installed globally, replace familiaros with npx -y @familiaros/cli@latest.

  1. Ask the user to restart Claude Code.
  2. Verify from Claude with the MCP tool familiaros_status.

Hooks

Claude hooks are optional. Do not install or modify hooks unless the user asks for automatic reactions/status behavior.

If hooks are requested, prefer the official FamiliarOS configure flow or FamiliarOS Claude tooling instead of manual edits.