KRATONStart building

Kraton Companion for macOS

Your software.In view.
In your control.

Your builds, reusable functions, connected assistants, and execution activity — in one local app.

View Kraton source

Public installer link coming soon. No signup needed.

  • No AI model inside
  • No account
  • macOS 13+
Kraton CompanionOn this Mac
HomeEngine running

Your work, on this Mac.

An assistant can help. You stay in charge.

Start with a real task Verified function

Find a time slot

Calculate from the intervals you supply. No calendar connection needed.

Copy this into your connected assistant. Nothing is sent for you.

My Builds

Friday slots.kraton

A flow you reviewed and saved

Last activity

Find open 15-minute slots

Completed · typed-scheduler

Home · interface preview with illustrative dataA local app. Not another AI chat window.

Connect.
Ask. Answer.

From opening the app to your first useful result. Your assistant does the asking. Companion makes the work and the decisions visible.

Illustrative sequence based on current screens. Select any step. Playback stops at the permission decision.

Kraton CompanionOn this Mac
HomeEngine running

Your work, on this Mac.

An assistant can help. You stay in charge.

Start with a real task Verified function

Find a time slot

Calculate from the intervals you supply. No calendar connection needed.

Copy this into your connected assistant. Nothing is sent for you.

My Builds

Friday slots.kraton

A flow you reviewed and saved

Last activity

Find open 15-minute slots

Completed · typed-scheduler

Engine starts automatically. It stops when Companion quits.

Open Companion. The bundled Engine starts on your Mac. No terminal setup needed.

A place for
every part.

Start a task, keep a build, inspect an outcome, or change who can connect. Explore the actual jobs of each screen.

Kraton CompanionOn this Mac
HomeEngine running

Your work, on this Mac.

An assistant can help. You stay in charge.

Start with a real task Verified function

Find a time slot

Calculate from the intervals you supply. No calendar connection needed.

Copy this into your connected assistant. Nothing is sent for you.

My Builds

Friday slots.kraton

A flow you reviewed and saved

Last activity

Find open 15-minute slots

Completed · typed-scheduler

A useful place to start.

See what needs your attention, return to a build, or copy a verified starter prompt.

Interactive preview with illustrative data. These controls do not change your Mac.

Here to help.
Not take over.

Functions work on your files here. Your assistant receives the results you allow. Local execution and a cloud-based assistant are different boundaries.

This Mac

  • Local function execution
  • Saved builds and their internal plans
  • Your permission decisions and Activity journal
  • Engine token in macOS Keychain
Tool requestResult

Your assistant

Your conversation stays with the assistant you chose. Kraton receives the tool request, not the chat history.

The assistant receives the result and aggregate measurements — not the build’s internal plan.

A local tool can still return sensitive information. What the assistant receives may be processed by its provider. Review the task and the result you permit.

One pause for every connected assistant.

Blocks new Kraton MCP requests. It does not promise to cancel work already running.

Friday slots.kraton

This exact build is shared with Claude Desktop.

Interactive example only. New requests allowed. Example build shared. Nothing changes on your Mac.

Chosen folders. Explicit reach.

Spaces · integration in progress

Spaces already let you select folders and a read or read/write mode in the app. Connecting those folder boundaries to every live MCP call is still in development.

ReadRead + write

These settings are not presented here as shipped, end-to-end file-access enforcement. Network access is a separate host permission.

What you can
use today.

The interface is grounded in the current app. The public macOS package is being prepared; some features are still in development.

Full project status

In the current build

  • Automatic local Engine startup and shutdown
  • Verified starter prompts and local function inspection
  • Connections for all nine supported assistants
  • Permission decisions and a local Activity journal
  • Explicitly reviewed, saved, and shared .kraton flows

Still being built

  • Running a function directly from the interface
  • Scheduled automations and publishing personal flows
  • Remote Registry discovery and installation
  • End-to-end Spaces folder boundaries for MCP calls
System requirements & release details

The development build targets macOS 13+. These are provisional release fields, not a claim that a signed public installer is available.

Processors
To be confirmed
Installer
DMG planned
Signing / notarization
To be confirmed
Download size
To be confirmed
What gets installed & how to remove it

Companion bundles the local Engine and Kraton CLI. While the app runs, its Engine listens on 127.0.0.1:50051. Quitting Companion stops that bundled Engine. Its API token stays in macOS Keychain; it is not embedded in assistant configuration.

To remove it: disconnect assistants in Companion, quit the app, then move Kraton from Applications to Trash. This preserves your saved builds and local history. If you also want to erase local data, review ~/Library/Application Support/Kraton and the Kraton Engine token in Keychain separately. Companion’s settings show the active data and log locations.

Prefer
the terminal?

The same local tools, without the window. Check the host, connect an assistant, or inspect the catalog.

How the local Engine works
kraton host statusCheck the local engine.
kraton connect <agent>Review and configure an assistant connection. Replace <agent> with its ID.
kraton catalogList available functions and their contracts.

Before
you start.

Is Companion another AI assistant?

No. There is no AI model inside Companion, and it is not a chat app. It connects the assistant you already use to local Kraton tools and shows the activity and access decisions.

Do I need an account or subscription?

No Kraton account is needed for this local workflow. Companion is free for the current release. Your AI assistant’s pricing and provider terms remain separate.

Which assistants are supported?

Claude Code, Claude Desktop, Codex, Gemini CLI, Antigravity, Cursor, OpenCode, Hermes, Kiro. Companion reviews the local configuration change before connecting. Some assistants need a restart to pick it up.

What can leave my Mac?

Functions execute locally, but their permitted results return to your assistant. If that assistant uses a cloud model, its provider may receive those results. A function can also use an external service when the host grants that connection. “Local” is not a promise that every result stays private.

Can I use it without an assistant?

You can inspect local functions, builds, and Activity in Companion. Direct function execution from its interface is still in development. For terminal-based operation, use Kraton CLI.

Where is the source?

The Companion repository will be public at release. Explore the Kraton project source

Your assistant.
Your software.
Your say.

One local place to see the work, keep the useful parts, and decide what gets access.

Find your first use case

Public installer link coming soon. No account required.