Sensact FAQs

Question 1

How does Sensact ensure secure device capability invocation?

Accepted Answer

Sensact integrates a robust security model utilizing Supabase Auth to provide an OAuth 2.1 authorization flow. This ensures that all device capability invocations are properly authenticated, authorized, and managed securely.

Question 2

What is Sensact and how does it connect LLMs to devices?

Accepted Answer

Sensact is a Supabase-hosted platform designed to allow Large Language Models (LLMs) like Codex or Claude to securely discover and invoke capabilities on user-owned devices. It does this through a standard remote Model Context Protocol (MCP) server, providing a structured way for AI clients to interact with device functions.

Question 3

Is Sensact currently available, and what are its future plans?

Accepted Answer

Sensact is available as a remote-only public preview and is prepared for the official MCP Registry. While the current focus (v1) is on one-shot capability invocation, future phases (v2, v3) plan to introduce WebRTC media sessions for real-time audio/video and advanced actions with real-time inference orchestration.

Question 4

What types of device capabilities can LLMs access through Sensact?

Accepted Answer

Currently, Sensact allows LLMs to list visible devices, inspect their capabilities, and invoke simple actions via jobs. Examples include `vision.camera_capture`, `contacts.find_contact`, and `vision.screen_capture`. It returns structured results or artifact references from these operations.

Question 5

What role does Supabase play in the Sensact architecture?

Accepted Answer

Supabase forms the core infrastructure for Sensact. It provides the OAuth 2.1 authorization server, a remote MCP gateway via Edge Functions, and the control plane using Postgres, Realtime, and Storage services for managing registry, capabilities, executions, and artifacts.

Sensact

Sensact

주요 기능

사용 사례

주요 기능

사용 사례