Connected activity is designed, currently paused

Orbit has a per-user integration model for Strava, Hevy, GitHub, Plex, Komga, Saveslot, and Steam. An integration can authenticate a provider, store a user-specific script, poll or run it, validate a connection, and map matching external activity into a habit entry.

Disabled Integration routes and implementation are retained, but integrations are deliberately disabled globally in the current product. They currently return unavailable responses, and the corresponding MCP data tool is not registered. This page describes the platform shape, not a currently available user feature.

Intended lifecycle

1. A person authorizes a provider.
2. Orbit stores the provider connection and optional integration script.
3. A mapping links a qualifying external event to a habit.
4. A run, poll, webhook, or external entry creates a deduplicated entry.
5. The entry contributes to the appropriate goal and balance period.

Platform capabilities

Capability	Intended use
Provider authorization	Per-provider OAuth or token setup.
Script management	Store, read, update, and delete provider scripts.
Verification	Validate provider connectivity before use.
Mappings	Connect provider events to habits using match rules.
External entries	Accept deduplicated external activity by external ID.

Re-enabling integrations requires product readiness work, not simply exposing the existing routes. See Roadmap.