The new bottleneck

The speed of building now depends on how many agents you can handle.

The models are fast enough. The limit is you: how many agents you can keep moving in parallel without losing track of any of them.

Output has outrun review

More code, faster, than anyone can read. Skimming is hoping.

Your attention is single-threaded

Five agents, one pair of eyes. While you read one, the other four wait for you.

The wrong instruction runs

"Delete the test file" / "delete the rest of the file." A misheard word executes.

What's inside

One harness for every agent, every project, every language.

Talk to it, hear it talk back, and let it run the rest, on any model, with git built in.

Hands-free voice
Talk to your agents. Hear them talk back.

Real-time talkback while you pace, sketch or make coffee. Ask for a change, hear what happened, answer the next question, without going back to the keyboard.

You talkIt talks backNo keyboard needed
A developer stands by the window with a coffee and headphones, away from the laptop, while SKI reads back the result
Multilingual
Speak the language you think in.

Give instructions in your own language, or mix two. SKI works out what you meant and hands the agent a precise instruction.

Voice · auto-detect
हिन्दी"login वाले tests फिर से चलाओ"
Español"vuelve a correr los tests de login"
日本語"ログインのテストをもう一度実行して"
AgentRerun the login test suite
Project orchestration
One agent that knows what is happening across all your projects.

An intelligent orchestration layer keeps the context of every project, branch and chat. Ask where things stand and get one spoken answer, then let it hand each job to the right agent.

Project contextCross-project statusHands work to the right agent
SKI Hub
"Where do things stand?"
SKI across 3 projects
ski2 agents running aurora-webneeds you · hero copy ledger-apidone · tests green
Neutral harness
Not tied to any model company.

Bring the accounts you already pay for and pick the engine per task. When the leaderboard changes, your workflow stays.

Multiple agents
Run many agents under one hood.

Claude Code, Codex, Antigravity and OpenCode side by side, each on its own task. You hear the moment any one of them needs you.

4 agents · 1 needs you
CC
Claude CodeFix notch hover
running
CX
CodexHero motion timings
needs you
AG
AntigravityExtract strings for i18n
running
OC
OpenCodeLighthouse score fixes
done
Total git integration
Git built in, from branch to pull request.

Every chat gets its own branch and worktree, so agents never step on each other. Watch the diff as it happens, then say "open the PR".

Branch per chatIsolated worktreesLive diffsPRs by voice
vegavega/notch-hoverCreate PR
Msrc-tauri/src/panel.rs+38−2
Msrc/lib/NotchBar.svelte+61−19
Msrc/routes/+page.svelte+12−4
Asrc-tauri/src/notch.rs+24−0
4 files · 2 commits ahead of main"Open the PR."✓ PR #142 opened
You listen instead of reading

You find out what your agents did by listening, not reading.

Results, summaries, the moment something needs you, spoken while you keep working.

FileEdit
9:41 AM
ski · vega
auth-refactorClaude Codespeaking

"Docs fix is merged. Three of the four failing tests pass now. The last one needs a fixture. Want me to add it?"

aurora-webCodexqueued

"Hero copy is ready. Short version or long one?"

Chain

One voice command. A chain of agents.

Say who does what. One agent plans, SKI hands its work to the next, and you hear when the whole chain is done.

One command, two agents
  1. 01
    Claude plans

    Claude Code on Opus 5.5 reads the code and writes the plan, step by step.

  2. 02
    Codex builds

    SKI hands the plan to Codex, which picks it up and builds it.

  3. 03
    You hear it's done

    SKI tells you when the last agent in the chain finishes.

Safe by construction

What you meant is what runs. Anything irreversible asks first.

SKI rebuilds the instruction from your project, shows you the interpretation, and gates anything irreversible.

SKI review window: the instruction rebuilt for the agent, with what it includes, answerable by voice: say approve, cancel, or a change
Intent reconstruction

From project context, not raw transcription.

Review before send

You correct it before the agent ever sees it.

Risk-scoped confirmation

Routine work runs. Destructive work asks.

SKI settings, Agents: Claude Code, Codex, Antigravity, OpenCode, Cursor and pi side by side, with model, effort, CLI and API sign-in, and every account in one list
Any model, any agent

Run every engine you already pay for, and send each job to the right one.

Hard reasoning to the expensive engine, bulk work to a cheap open-weight one. Spend follows the job, not the vendor.

No model vendor will ever route work to a rival's engine. Only a neutral harness can.
Why this cannot be bolted on

A harness built for typing assumes you are watching the screen.

Acknowledgement is separate from the answer

A reply is expected in ~200 ms; an agent turn runs ~45 s. A fast layer holds the conversation while the slow work runs.

The prompt is missing

You type composed prompts. You speak messy ones. The harness works out the intent and asks instead of guessing.

It assumes it will be misheard

Repair is designed in from the start, not bolted on after a bad transcription.

None of this can be retrofitted with a microphone.

Security

Your code stays on your Mac.

Your projects, code and chats stay on your Mac, and your agents run on your own accounts. Your voice goes through the cloud to be understood and answered. It isn't stored.

Code stays on your Mac Your own agent accounts Voice not stored Irreversible steps ask first
SKI settings, Voice: microphone and speaker, the languages you speak, speaker echo cancelling set to Auto, how long SKI waits for your pauses, and review before send switched on
✦Controlled by voice

Every agent, every state, on one canvas.

Leads, workers, and what each one is doing right now. You hear the moment any of them needs you.

SKI Hub: every project and agent chat in the sidebar with live status, an agent mid-task in the centre, and its changed files on the right
Pricing

A neutral harness, free forever. You only pay for voice.

SKI is not tied to any model company, and it stays free. Every plan runs every agent with the full voice loop; plans only differ in how much you talk. Pro lets you talk to more agents at once, and Enterprise brings the whole team.

On every plan

Text is free. Forever.

Everything you can do by typing is unlimited on the Free plan: every agent, every project, git built in. No subscription, no credits, no time limit. Credits only pay for real-time voice, because fast, secure voice costs us to run.

  • ∞text chats
  • 0credits used
  • $0for life
Free
$0/ month

The full harness on your Mac. Good enough to keep, not a crippled trial.

2 voice sessions at once
300 voice credits / month
  • Unlimited text chats with every agent, free forever
  • Every agent you already use: Claude Code, Codex, Cursor, OpenCode, Antigravity and pi
  • Talk to your agents and hear them talk back
  • The Hub: every project and agent chat in one place
ProCancel any time
$20/ month

For days when you run a whole team of agents and talk to them all.

12 voice sessions at once
2000 voice credits / month
  • Everything in Free
  • Top up any time; top-up credits last 12 months
  • Upgrade or cancel in SKI, under Settings, Account
Enterprise
Custom

For teams that want SKI on every Mac, at better rates.

For teams
Better rates
  • Everything in Pro
  • Better rates for the whole team
  • Talk to us about what your team needs

Prices in US dollars, plus tax where it applies.See full pricing and FAQ →

FAQ
Is SKI really free?

Yes. Typing to your agents is free for life: unlimited text chats with every agent, on the Free plan, with no subscription and no credits. Credits and session limits only apply to real-time voice. Pro is for when you want to talk to more agents at once.

Is this dictation?

No. Dictation hands text to somebody else's harness. SKI is the harness: the whole loop runs on voice.

Isn't talking slower than typing?

Often, yes. The win is not the input. It is that you stop reading output and hear the moment an agent is blocked.

How is this different from an orchestrator?

They orchestrate by clicking. Ask any of them: how do you steer an agent when you are not looking at the screen?

Which agents and models does it work with?

Whichever ones you already run. Neutrality is the point.

What happens if it mishears me?

You see the interpretation before it runs, and anything irreversible asks first.

Do I have to talk to a salesperson?

No. Get SKI, install, start.

Get SKI

Pick your platform.

Available
macOS

The full harness, notch and voice included.

Waiting list
Windows & Linux

Not out yet. Leave your email and we'll write when it is.

The coding harness you talk to. Run every agent you already use, and hear them, instead of reading them.

Product Hunt#1 Product of the Day
Resources
© 2026 Pattern AI Labs. All rights reserved.
Terms Privacy Refunds Cookies justski.it