# Remote CAS configuration.
#
# Loaded via 3-tier resolution (system → user → project).
# Projects override with their own .ai/config/remotes/remotes.yaml.
# Deep merge: project can add remotes without restating defaults.
category: "cas"
version: "1.0.0"

defaults:
  timeout: 300  # request timeout in seconds, applied to all remotes

# project_name: my-project   # stable identifier for push refs + webhooks
#                             # Falls back to directory basename if unset.

# Named remotes (like git remotes).
# Each entry: name → {url, key_env, roles}.
# "default" is used when no remote name is specified.
# key_env references an env var name (never store keys in config).
# roles: optional list marking special-purpose remotes (e.g., [registry])
#
# remotes:
#   default:
#     url: https://ryeos-node--mcp-server.modal.run
#     key_env: RYE_REMOTE_API_KEY
#   gpu:
#     url: https://ryeos-gpu--mcp-server.modal.run
#     key_env: RYE_GPU_API_KEY
#   registry:
#     url: https://ryeos-registry.example.com
#     key_env: RYE_REGISTRY_KEY
#     roles: [registry]
#
# Cluster example — routing tools query /status on each node to discover
# capabilities automatically. No need to declare capabilities in config.
#
# remotes:
#   default:
#     url: https://cpu-node.example.com
#     key_env: RYE_REMOTE_API_KEY
#   gpu-a100:
#     url: https://gpu-a100.example.com
#     key_env: RYE_GPU_API_KEY
#   gpu-small:
#     url: https://gpu-small.example.com
#     key_env: RYE_GPU_SMALL_API_KEY
