cAppDeveloper docsStart with the capability you need
Sidecars add selected capabilities to one application's package. Start with the smallest useful composition, then follow its reference for configuration, API ownership and prerequisites. Browse the components below, integrate an existing Sidecar, or create a shell Sidecar.
The directory is a public reference, not your installed Library. Searching or changing a filter here does not install a package, change an app or contact a provider. Use Library in cApp to make selections.
Choose a starting point
| What you want to build | Start here | Important boundary |
|---|---|---|
| Help, tours and declared tasks | Guide | Authored help does not require Local AI |
| Local inference or contextual assistance | Local AI and MCP Context | A selected engine is not a loaded model or a grant to every tool |
| In-app documentation and saved links | Links | A requested tab does not prove the destination loaded |
| Tests and runtime diagnostics | Test Runner, Debug, Service Inspector | App-surface automation is not desktop control; check each target |
| Prices and charts | Market Pulse | A quote does not authorise a trade |
| Solana reads, payments or simulation | Solana composition | Choose the provider mode first; simulation, live RPC and wallet handoff are different |
Read the labels before selecting
Alpha capability means a component has a declared runtime in this reference. The target labels come from its runtime-ready manifest declarations, not certification of every device or configuration. Windows and Android are the main build targets documented here; Linux/macOS labels are declarations, not additional qualification evidence.
Core capability is configured through its owning build feature rather than ordinary optional selection. The Android authentication coordinator is one example. Planned entries have no callable runtime to integrate; the four planned components remain visible in the unfiltered directory but are excluded when you choose a runtime target.
On a component page, distinguish build settings for the next package, application APIs exposed to its running owner, and Agent tools registered and authorised separately. A package ID is not necessarily an SDK capability name. Dependencies can also change with provider mode: read the component's composition instructions rather than enabling everything nearby.
Use the search, Target and Kind filters together. Search matches names, descriptions and package IDs. Clear filters when nothing matches; no result is not a runtime error. Each reference links to its brief component changelog. Continue with Build with Sidecars for a complete first integration.