Kratyx

Integrations

Connections are capabilities, not blanket access.

See what each Kratyx integration surface does, whether it is currently usable, and which approval or release boundary still applies.

Local runtime

Internal preview

Desktop

Starts, stops, and reports the supervised local mission runtime from the desktop host.

Execution remains policy-bound and exposes an emergency stop.

Code Studio

Internal preview

Desktop

Provides a bounded workspace tree, Monaco editor, manual save, project search, Git branch inspection, and localhost preview.

Text files are limited in size, paths must remain inside the selected canonical workspace, and arbitrary terminal execution is not enabled.

Developer tools

Internal preview

Desktop and runtime

Registers exact build, lint, type-check, test, and format-check commands with pinned configuration hashes.

Every executable developer command requires a fresh one-time approval; the public release keeps execution disabled until that approval path is fully exposed.

Git

Internal preview

Code Studio

Reads the selected repository branch without starting an external process.

Commit, pull, push, branch creation, merge, and force operations are not silently performed.

Chrome bridge

Planned

Chrome extension and native host

A Manifest V3 extension contract supports active-tab observation and per-origin permission requests.

The authenticated packaged native host is not a public release; click, input, navigation, and scrolling require exact approval.

Desktop control

Planned

Windows native automation

A target-bound automation policy and evidence contract exist for visible native interactions.

Unrestricted autonomous PC control is not enabled. Mutations require a fresh target-bound approval.

MCP connections

Planned

Plugin boundary

The product catalog reserves a governed connection surface for compatible MCP servers and tools.

Each server still needs a verified schema, identity, data classification, and per-tool authorization.

Model providers

Internal preview

Settings and mission runtime

Kratyx can represent accepted local and cloud model profiles.

Live use depends on credentials, provider acceptance, network access, quota, retention terms, and model availability.