h1ddenpr0cess20

Tater — Development skill for Claude Code

Development community

A voice agent rendered as a potato — rude, russet, and driven by a live OpenAI Realtime call.

How to install Tater

This entry records only its repository, not the path inside it, so there is no exact command to give. Open h1ddenpr0cess20/tater and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Tater does

A voice agent rendered as a potato — rude, russet, and driven by a live OpenAI Realtime call. Remembers what you tell it, and hands work to Claude Code, Codex, OpenCode or Grok Build.

Alternatives in Development

  • Happy — Mobile and Web client for Claude Code, with realtime voice, encryption and fully featured 16.3k ★
  • Dario — A local OpenAI- and Anthropic-compatible proxy that brings your Claude Pro/Max subscription to Cursor, Cline 485 ★
  • Convex Realtime 354 ★

README

Tater

A voice agent rendered as a potato. Tater is russet and lumpy, and rude about it: he stands on his end and rocks where he is, walks a short way out and back while he talks, lies down and spins while he thinks, and squashes in time with whoever is making sound — all of it driven by a live OpenAI Realtime call. He remembers what you tell him to, between calls, and hands work off to a coding agent.

![Tater in a desktop browser](docs/screenshots/desktop.png)

Tater on a phone

Run

git clone https://github.com/h1ddenpr0cess20/tater
cd tater
npm install
cp .env.example .env      # add your OPENAI_API_KEY
npm run dev               # → http://localhost:5173

Click the mic, allow the browser's microphone prompt, and start talking.

Tapping the mic is the microphone switch: turning it off stops what you send and leaves the answer playing, and the conversation is still there when you turn it back on. It also switches itself off after a minute of silence, and the call survives that too. Holding the mic down is the hang-up — a ring closes around it while you hold, and the call ends when it lands.

`menu`, in the top corner, is where the panels live: `tools`, `connectors`, `memory` and the log, one row each. Picking a row closes the menu behind it, and work still running says so on the button while the menu is shut.

`tools` is where the per-call switches will be. It is empty today — memory has its own switch, and the connectors answer for the whole server rather than for one browser — but the panel and the storage behind it are wired, so a tool the session learns to declare shows up there with a switch of its own.

`connectors` is where you hand Tater a coding agent. Switch on Claude Code, Codex, OpenCode, Grok Build or Muse Code, point it at a repo, and say what you want built: Tater reads the task back, dispatches it on a yes, and tells you when it lands. The agent runs