· CH-D / WORKFLOWS · 0.12s LATENCY

Voice in.
Drafts, tasks, files out.

Start with something you said. Send it to the app, file, command, or model that should handle it. Most of the time that means your Mac and your tools. When it does not, you choose the outside service.

DOWNLOAD FOR MAC →macOS 26+ · Workflow EditorClaude CLI · Shell Steps

· 01 / STARTING POINTS

Start with simple workflows.

Small on purpose. Pick one, swap a path, make it yours.

Dictate → Claude

Say the prompt out loud. Talkie cleans it up and leaves it ready to send.

PASTE-READY

Dictate → Email

Talk through the reply in your own words. Open a polished draft in Mail.

DRAFT IN MAIL

Voice memo → Obsidian

Record the messy thought. Save the useful version as Markdown in your vault.

NOTE FILED

Iterate on a memo → Talkie Compose

Keep the raw take. Make a tighter version next to it, without losing the first one.

BOTH DRAFTS KEPT

Quick idea → Claude + @talkie/cli

Capture the spark, pull it from the CLI, and hand it to Claude when it needs a second pass.

READY FOR CLAUDE

Bug note → GitHub issue

Describe the bug while it is fresh. Turn it into a title, body, and issue command.

ISSUE OPENED

· 02 / STEP LIBRARY

Eight step types. Stack them in any order.

Every step is composable. Chain an LLM into a shell command into a save. Branch the router by keyword. Tee the same transcript into a journal and a webhook in one pass.

LLM

Summaries, extraction, restructuring

Shell

Run CLI tools — claude, gh, jq

Save to File

Write results to disk with aliases

Webhook

POST JSON or text to any endpoint

Send results via Mail.app

Calendar

Create events from a transcript

Clipboard

Copy results to system clipboard

Notification

Native macOS alerts

· MODELS

ClaudeOpenAIGeminiGroqLocal MLX

Bring your own keys. Local MLX runs without leaving the device.

· VARIABLES

Substitute anywhere — prompt bodies, shell args, file paths, request bodies.

· 03 / SHELL STEP

Your terminal, on the end of a sentence.

Shell steps run real binaries on your machine. There is an executable allowlist and a respectful PATH merge — brew, node, bun, Claude CLI all resolve the way they do in your terminal.

· WHAT IT GETS YOU

Executable allowlist for predictable, reviewable runs
Native Claude CLI integration via MCP
Multi-line script templates with variable substitution
Respectful PATH merge — brew, node, bun, claude
Stdout captured back into the workflow as the next variable

step · shell · gh issue create

READY

# template: file an issue from a dictated bug report
gh issue create \
  --repo  "arach/talkie" \
  --title "{{TITLE}}" \
  --body  "{{TRANSCRIPT}}" \
  --label "voice-memo"

# stdout becomes {{LAST_OUTPUT}} for the next step
# https://github.com/arach/talkie/issues/421

EXIT 0·412ms·audit:wf-01 dry-run available

· 04 / FILE SINKS

Land it exactly where you want it.

· PATH ALIASES

Shortcuts for the directories you actually use.

@Notes→~/Documents/Obsidian/Vault
@Projects→~/Dev/Current
@Inbox→~/Documents/Talkie/Inbox
@Journal→~/Documents/Journal

· SMART OUTPUT

Filenames that compose themselves.

Template filenames with date and time tokens
Auto-create missing directories
Append-mode for logs and rolling journals
Per-workflow custom output paths

@Notes/{{DATE}}-{{TITLE}}.md

· 05 / TOOL CHOICE

Your tools first. Outside tools when you ask.

Talkie does not need to turn every workflow into a cloud diagram. Keep it local when that is enough. Bring in Claude, OpenAI, Linear, Slack, or a webhook only when the workflow actually needs it.

Start