by AKamaly
Always-on AI Gods that work inside Claude Code, and you can talk to them. Proactive workers, computer use (browser, terminal & files), real-time voice like Jarvis, workers on a call in their own voice, Slack, and Spaces for your projects.
# Add to your Claude Code skills
git clone https://github.com/AKamaly/CludeGodsGuides for using ai agents skills like CludeGods.
See how CludeGods compares with popular alternatives.
CludeGods is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by AKamaly. Always-on AI Gods that work inside Claude Code, and you can talk to them. Proactive workers, computer use (browser, terminal & files), real-time voice like Jarvis, workers on a call in their own voice, Slack, and Spaces for your projects. It has 50 GitHub stars.
CludeGods's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/AKamaly/CludeGods" and add it to your Claude Code skills directory (see the Installation section above).
CludeGods is primarily written in TypeScript. It is open-source under AKamaly on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh CludeGods against similar tools.
No comments yet. Be the first to share your thoughts!
Available after the catalog security scan passes.
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
Always-on AI Gods that work inside Claude Code.
Always-on proactive workers · Computer use: browser, terminal & files · Real-time voice, like Jarvis (RIP Iron Man) · Put any worker on a call, in its own voice · Bring workers into Slack · Spaces and Pages for projects
Built on Claude Code and VoiceMode. · Get started · How to use it · Overview · Architecture · Features · Safety · Changelog · Contributing
Watch the full launch film (67 s) · Latest release
The app scene, a call with a barge-in, a permission approved with a click, and a scheduled worker checking in with drafts. A 14-second cut of the silent launch film; the film is an animated mockup of the real parts, not a screen capture.
CludeGods is a small set of parts that sit on top of Claude Code and
VoiceMode. You type /gods, a small call
card with the colleague god appears in the corner, and you talk to your Claude Code session the way you would to
someone sitting next to you. Over on the right, a Workers pane shows your standing worker
chats, each with a task box.
A toolkit, not a hosted product. Everything runs on your Mac. The only state is plain
files under ~/.voicemode/call/. Speech to text and text to speech run locally; the
transcript of what you say goes to Claude, the same as anything you type into the session.
Press play, then click the speaker icon: GitHub starts every video muted, and this one talks.
https://github.com/user-attachments/assets/f384d329-f26c-4d89-b912-9ed2e24fbf38
CludeGods in 54 seconds: a voice call with Claude, every step said out loud, a click to approve, a task for an always-on worker, and a worker on the call.
The parts:
gods skill: a live voice call with your Claude Code session. An
always-on mic streams your words in, Claude answers out loud without blocking its own
work, and you can cut in at any time.narrate says each step out loud as it happens; permit can route permission
prompts to the pill (off by default: the app's own dialog handles them).pages: Markdown spaces and pages that you and your workers
share. Workers save pages in the spaces you let them write, or leave drafts for your
Approve if you prefer; Memory always waits for your Approve.guard hook: holds each worker to the tools you gave it: full by default, or read
only, drafts only, or a list of tools.cludegods: sets up voice, checks every part and fixes what is off, updates and
uninstalls.You type /gods. Claude says "I'm here. What's first?" You ask "Can you check why the
build broke this morning?" Claude says "Hmm, let me look," and while it reads logs you hear
"Reading the CI log." and "Searching the code." between your own questions. Halfway through
its answer you say "wait, not that one," and it stops talking and listens.
Long jobs go to helper agents that report milestones in a sentence. Anything outward, like an email or a post, lands in the chat as a draft. Claude reads it back in one sentence, and nothing goes out until you say a clear yes (or type it, if you set it that way).
In the Workers pane, Research is working and Scribe has been idle for ten minutes. You type a task into Scribe's box and press Enter.
/gods starts the ears (always-on capture with Silero VAD and Whisper), the mouth (a
non-blocking speech queue), and CallPill. The god on the call card moves through Listening, You, Thinking,
and talking, with the line being spoken as its caption. Talk over Claude and it stops: each partial transcript is checked while a line
plays, and if it is you, the speech is cut and your words go straight to the session.
The call card. Real-time voice, and you can cut in at any time.
The narrate hook turns each tool call into a short spoken line ("Reading config.py.",
"Now I'm going to run the tests.") at most once every 6 seconds, only during a live call and
only in the call's own session. You hear what Claude is doing without watching the screen.
Each worker is its own Claude Code chat with a name, a role, a god, a voice and its own hours. The Workers pane lists them as cards: the god animates while the worker is Working, a badge counts the drafts waiting for your yes, and Activity shows its last steps read from the transcript. Type a task into a card and press Enter to send it to that chat; Open jumps to it.
Workers connect to you through the pane: send a task, run on a schedule, collect drafts in an outbox, approve with a click.
Settings on every card: a name, one of six gods, a voice (Kokoro: af_heart, am_michael,
bf_emma and more), working hours, a tools preset, pause, and the Spaces it may write
to. It all lands in ~/.voicemode/call/workers.json, and each worker speaks its heads-ups
in its own voice.
Their names. Their voices. Their hours.
The mic hears the whole room, so voice never answers a permission prompt. By default the
prompt is the app's own dialog, exactly as without CludeGods. Set
approvals.permission_prompts to "pill" and, during a live call, CallPill shows the
request beside the call card with Deny and Allow, and a mouse click is the only thing that
answers it. A spoken "yes, go ahead" is ignored.
Outward actions, like sending an email, work differently: Claude writes the exact action in
the chat and reads it back in one sentence, and a clear spoken yes to that read-back counts.
Set approvals.outward to "typed" to require a typed yes. See the
Safety model.
A permission request on CallPill, with permission_prompts set to "pill". Only the click counts.
Give a worker a schedule, and the pane wakes it at that time: to run its charter if it
has one, or to check in on its role if not. It does its run, writes drafts and notes to an
outbox, and the card shows a 2 drafts badge. Each item that needs a yes gets Approve,
Change and Decline on the card: Approve tells the worker to go ahead with exactly that
draft, Change sends it back with your note, Decline tells it to drop it. Nothing from a
scheduled run goes out before you approve it. Details in Proactive workers.
Scribe runs Monday to Friday at 9:00 and leaves two drafts that need your yes.
A Space is a folder of Markdown pages under ~/.voicemode/call/spaces/. The Spaces pane
lists them with search and nested subpages, shows a page, and has Ask a worker about this
page (send a question about it to any worker) and Open in editor. Workers read pages and save
them directly in the spaces you let them write. Set approvals.worker_publish to
"approve" and they save through pages draft instead: the draft shows up in their outbox
as "needs your yes", and only your Approve publishes it, with a revision check so a stale
draft never overwrites newer edits. A built-in Memory