security / curated defaults

Curated Defaults And Supply Chain Safety

Ambient deliberately curates default plugins and capabilities instead of pushing users into an unfiltered plugin ecosystem.

Developer Previewllms.txtSource evidence
Curated Default Capability Chain Default capabilities are selected, described, pinned, sandboxed, and validated before they become easy install paths. Curated Default Capability Chain Default capabilities are selected, described, pinned, sandboxed, and validated before they become easy install paths. selectswrapstestsexposes Trusted capability path curatesandboxdiagnose 1 Select Reputable upstreamsOfficial CLIsNarrow use cases 2 Wrap DescriptorPinned runtimeToolHive policy 3 Validate Install smokeSchema checksPermission tests 4 Expose Default catalogUser approvalDiagnostics
Default capabilities are selected, described, pinned, sandboxed, and validated before they become easy install paths.
Product screenshots

Plugin Manager

Plugin Manager presents curated defaults, install state, and capability trust boundaries.

Ambient Desktop plugin manager.

Opinionated Defaults

Ambient makes reputable core capabilities easy to install: official Google CLI based integration, Scrapling for extraction, Exa for search, Context7 for docs lookup, and first-party browser surfaces where appropriate.

Why Curation Is Security

Uncurated plugin markets can expose users to malware, credential theft, local file access, and unsafe browser automation. Ambient does not ask users to gamble on unknown packages for basic tasks.

Scrapling Example

Scrapling is useful because agents need web extraction. Ambient wraps it as a reviewed default capability and isolates it with ToolHive because autonomous browsing and scraping can encounter hostile pages.