Skip to main content

Feature coverage reference

Use this map to find the technical contract for each reviewed feature family. It is a documentation coverage map, not a functionality PASS table. Host, provider, platform and release conditions still apply.

Messaging and conversation operations​

FeatureTechnical referenceKey boundary
Native SendSendExplicit authored message; caller finishes after tool result
Fire-and-forget admissionSendAdmission is separate from delivery
Cache-miss discoveryIdentitySelection at discovery completion, then pinned
Same-name selectionIdentityScoped most-recent use; sender never inferred from recency
Executing sender identityIdentityNative provider/account/surface/session
Durable deduplicationSend, storageNo replay of uncertainty
Optional earlier-Send statusInterfacesObservation only; installed host may omit it
List and discovery refreshRegistryReal native sessions, not delivery proof
Imported peer registryRegistry, SSHRouting metadata and exact remote ownership
Conversation CreateConversation managementActual new native identity, supported surface
Conversation Rename/aliasConversation managementNative title versus local alias; retain target identity
Session views/System MapConversation managementProjection of observed state
Native MCP tool integrationProtocolsHost metadata and advertised schema
CLI administrationInterfacesOS/version-specific help, not MCP arguments

Providers and components​

FeatureTechnical referenceKey boundary
All 13 reviewed provider entriesCatalogDesktop/CLI/Remote distinction
Claude surfacesClaudeDesktop Code versus Code CLI
Codex surfacesCodexDesktop plugin, CLI and provider Remote
Cursor surfaces/CLI managerCursorEditor bridge versus CLI topology/configuration
OpenCode v1/v2OpenCodeExisting native service and automatic migration
VS Code Copilot AgentCopilotNot every ordinary Copilot Chat surface
Standalone Copilot CLICopilotSeparate worker/configuration/native sessions
Antigravity surfacesAntigravityProvider sign-in and desktop/CLI scope
Detection and enablementCatalog, configurationRequested versus installed/active
Integration install/repair/uninstallInstallationExplicit owned scopes and warning completion
Independent provider builds/publicationSupply chainProducer/source/protocol and signing identity
Availability/download buttonHot updatesExplicit network action, signed channel
Close provider before updateHot updatesExact process identity and verified exit
Automatic owned migrationHot updatesTransaction before activation, no separate routine repair
Full application/runtime upgradeSupply chainSeparate signed component versions
Installer completion/warningsInstallationIncomplete integration is not verified success

Accounts, connections and network controls​

FeatureTechnical referenceKey boundary
Browser account sign-inAccountWebsite PKCE flow, not provider login
Account configuration/profileConfiguration, interfacesEffective endpoints/overrides
Connect my devicesAccountExplicit consent separate from sign-in
First-device bootstrap and later approvalsAccountActual membership/approval state
Approve/reject/rename/revoke devicePairingExact native identity and grant type
Account security history/website managementAccount, interfacesBounded account observations and browser identity
Sign-out and revocation recoveryCredentials, recoveryLocal sign-out versus confirmed server revocation
Independent manual pairingPairingSeparate trust from account membership
Relay enable/disableDefaults, RelayPersisted opt-in, not a global network kill switch
Account-change hints/fallbackAccount, RelayInvalidations, HTTPS authority, source-only rollout
Account-only freshnessPairingFive-minute limit for new work
SSH node configuration/removalSSHSelected OS user/host key and independent route
SSH refresh/dispatchSSHNative remote identity; no uncertain replay
Remote SSH inspection/deploymentSSHExplicit mutation and remote result
A2A client/card importA2AActual endpoint authentication/task contract
A2A server/exposureA2A, network inventoryExplicit service/bind/authentication
Temporary login callback/local IPCProtocols, network inventoryLocal owner authentication
Passive network-status viewObservabilityMetadata coverage is not a packet ledger

Connected host and client facilities​

FeatureTechnical referenceKey boundary
Connected phone/SDKClient stackSeparate iPhone/Android build families
Agents/timelines/subscriptionsConnected workspacesAdvertised host and subscribed session
Projects/workspacesConnected workspacesAuthoritative host context
Files/uploads/downloadsConnected workspacesCurrent authorization and token scope
Terminals/scrollbackConnected workspacesOS-user command execution
Browser-host commandsConnected workspacesActual active capability; requested setting is insufficient
Change/source-control viewsConnected workspacesHost/workspace capability
Dictation/audioConnected workspacesPermission and backend/data destination
Push notificationsClient stack, network inventoryExpo/OS subscription and permission
Themes/fonts/language/displayAccessibility/localizationClient-specific controls, not platform-wide parity

Cross-cutting considerations​

ConsiderationTechnical reference
Activation/offline entitlementActivation and formatting
Body Builder/provenanceActivation and formatting, Send
Security and prompt/tool permissionsSecurity model
Local/server/provider dataData lifecycle, storage
Credentials and protected helpersCredential storage
Default install/start/network stateNetwork defaults
Ingress/egress destinationsNetwork inventory
Performance/concurrency/timeoutsReliability
Logs and support evidenceObservability
Backup, removal, outage recoveryRecovery
Signing/update/third-party reviewSupply chain
OS/provider/protocol supportCompatibility
Windows/Mac/Linux stacksWindows, Mac, Linux
Shared runtime, web and tooling stacksRuntime, web, tooling
Source-only versus released behaviorSource status

Out of scope: other AxiOwl products' independent on-device-agent, IDE and usage-meter implementations; internal signing secrets/infrastructure; a stable exhaustive low-level wire schema; audited/compliance or all-pairs functionality claims. Those omissions are boundaries, not implied capabilities.