CONFIGURE · CONNECT · BUILD ON
Extend

Select Features Available Within Cephable:

  • BASIC
  • PLUS
  • PRO
  • SDK

One agent. Every surface.

Extend is the layer you control. Decide what Cephable can reach, what’s allowed to reach Cephable, and which model does the thinking. Same on-device core, shaped to how you work.
FOR THE POWER USER Explore extensions
FOR DEVELOPERS Build with Cephable
SCROLL TO SEE THE CATALOG

THE EXTENSION CATALOG

Everything that let’s you do more.

Some sharpen Control, Create, or Automate. Some do all three. Switch on what fits how you work.

Extend what it can do AI Workflows · Pro
  • Skills

    Teach it how you work

    A skill is a folder with a SKILL.md — plain markdown plus any scripts and reference files. Write one, import one, or have Cephable draft one from a run it just finished. Call it with / or @ in the composer.

  • Connectors

    Bring your own tools

    Connect any MCP server over stdio, HTTP or SSE, with API-key, header or OAuth auth. Tools are discovered automatically and namespaced so they can't collide. Every server can require approve / edit / reject before a tool runs — and that's the default.

  • Local API · Professional

    Build on the agent itself

    Cephable opens a loopback HTTP server on your machine that runs the real assistant. It speaks the OpenAI chat-completions shape, so existing code points at it by changing a base URL — and it can call your functions back mid-run.

Extend your setup All plans

  • Extensions hub

    One place to switch capabilities on, connect companion apps, and see what's installed.


  • Extension marketplace

    Browse featured and community skills and connectors, rate them, and install in a click. Public submissions go through a moderated review before they're listed.


  • Mobile companion

    Turn a phone into a second input surface for a paired computer — controls and quick actions in your pocket.

Roll it out to your team Pro
  • Teams & orgs portal

    Invite members, assign roles, and manage access across an organization.

  • Extension governance

    Decide whether people may add their own skills and connectors, or use the public marketplace at all. The strictest org setting wins.

  • Share skills & connectors internally

    Publish a skill or a connector to your organization only — immediately, with no public review.

  • Organization profile sharing

    Publish curated app-control sets to everyone in the org.

  • Automation rules (governance)

    Set org-wide guardrails on where Cephable may automate — allow or block specific apps and domains.

  • Assistant instructions

    Inject standing organizational instructions into every automation run — policies, required checks, safe ways of working.

  • License key management

    Issue, activate, and track license keys across seats.

  • Usage metrics

    Organization-level adoption and usage reporting, including which connectors are actually being used.

  • SSO / OAuth

    Sign in through your existing identity provider.

  • SCIM provisioning

    Automatic user provisioning and deprovisioning from your directory.

Build on the platform SDK

  • Cephable API

    Manage profiles, devices, controls, and real-time events programmatically, with scoped API keys.


  • SDKs & samples

    Embeddable SDKs for offline voice, face, head, and quick-action input on Windows and macOS — plus open-source samples for the local agent API.


  • Developer portal

    Create and manage projects, auth clients, API keys, and integrations in one console.


  • Custom device types

    Register your own hardware or software as a Cephable device type with its own control set.


  • Real-time device events

    Stream control events straight into your app or game over the device hub — the same channel the Cephable clients use.

Proven at AAA scale

If it holds up here, it holds up anywhere.

The team behind Call of Duty: Black Ops 7 wired Cephable's control layer into the game, so players drive their in-game character straight from the Cephable app using whatever input works for them. That's the most demanding real-time environment there is. Zero tolerance for lag, no room for a control surface that buckles under load. It held. If Cephable's on-device input layer performs there, it performs behind whatever you're building.

Live at AAA scale Real-time input, no lag On-device control layer
Call of Duty: Black Ops 7 controlled from the Cephable app

From one layer to the whole platform

Black Ops 7 needed one piece of Cephable, the input layer. You're not limited to one piece. The same on-device engine is yours to build on, whichever way your product needs it.

Here's what you can build.

Came here thinking Cephable was a desktop app? This is where it's a platform. Two integration paths, both powered by the Cephable assistant running privately on the user's own device.

Web SDK

Embed it in web apps

Drop the on-device assistant into any JavaScript or Electron app. Voice, dictation, face and head input, all running locally in the browser. No audio or video leaves the device.

.NET SDK

Embed it in Windows apps

The same private assistant for C# and WPF desktop apps. On-device by default, one NuGet package away. Users drive your app hands-free through their own Cephable profile.

Game integrations

The path Black Ops 7 took

Let players drive your game with their choice of input, voice, face, head movement or switches, mapped to any action. Unity package or Virtual Controller for any engine.

Build with Cephable