clui-cc-claude-overlay▌
aradotso/trending-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Skill by ara.so — Daily 2026 Skills collection.
Clui CC — Claude Code Desktop Overlay
Skill by ara.so — Daily 2026 Skills collection.
Clui CC wraps the Claude Code CLI in a transparent, floating macOS overlay with multi-tab sessions, a permission approval UI (PreToolUse HTTP hooks), voice input via Whisper, conversation history, and a skills marketplace. It requires an authenticated claude CLI and runs entirely local — no telemetry or cloud dependency.
Prerequisites
| Requirement | Minimum | Notes |
|---|---|---|
| macOS | 13+ | Overlay is macOS-only |
| Node.js | 18+ | LTS 20 or 22 recommended |
| Python | 3.10+ | Needs setuptools on 3.12+ |
| Claude Code CLI | any | Must be authenticated |
| Whisper CLI | any | For voice input |
# 1. Xcode CLI tools (native module compilation)
xcode-select --install
# 2. Node.js via Homebrew
brew install node
node --version # confirm ≥18
# 3. Python setuptools (required on Python 3.12+)
python3 -m pip install --upgrade pip setuptools
# 4. Claude Code CLI
npm install -g @anthropic-ai/claude-code
# 5. Authenticate Claude Code
claude
# 6. Whisper for voice input
brew install whisper-cli
Installation
Recommended: App installer (non-developer)
git clone https://github.com/lcoutodemos/clui-cc.git
# Then open the clui-cc folder in Finder and double-click install-app.command
On first launch macOS may block the unsigned app — go to System Settings → Privacy & Security → Open Anyway.
Developer workflow
git clone https://github.com/lcoutodemos/clui-cc.git
cd clui-cc
npm install
npm run dev # Hot-reloads renderer; restart for main-process changes
Command scripts
./commands/setup.command # Environment check + install deps
./commands/start.command # Build and launch from source
./commands/stop.command # Stop all Clui CC processes
npm run build # Production build (no packaging)
npm run dist # Package as macOS .app → release/
npm run doctor # Environment diagnostic
Key Shortcuts
| Shortcut | Action |
|---|---|
⌥ + Space |
Show / hide the overlay |
Cmd + Shift + K |
Fallback toggle (if ⌥+Space is claimed) |
Architecture
UI prompt → Main process spawns claude -p → NDJSON stream → live render
→ tool call? → permission UI → approve/deny
Process flow
- Each tab spawns
claude -p --output-format stream-jsonas a subprocess. RunManagerparses NDJSON;EventNormalizernormalizes events.ControlPlanemanages tab lifecycle:connecting → idle → running → completed/failed/dead.- Tool permission requests arrive via HTTP hooks to
PermissionServer(localhost only). - Renderer polls backend health every 1.5 s and reconciles tab state.
- Sessions resume with
--resume <session-id>.
Project structure
src/
├── main/
│ ├── claude/ # ControlPlane, RunManager, EventNormalizer
│ ├── hooks/ # PermissionServer (PreToolUse HTTP hooks)
│ ├── marketplace/ # Plugin catalog fetch + install
│ ├── skills/ # Skill auto-installer
│ └── index.ts # Window creation, IPC handlers, tray
├── renderer/
│ ├── components/ # TabStrip, ConversationView, InputBar, …
│ ├── stores/ # Zustand session store
│ ├── hooks/ # Event listeners, health reconciliation
│ └── theme.ts # Dual palette + CSS custom properties
├── preload/ # Secure IPC bridge (window.clui API)
└── shared/ # Canonical types, IPC channel definitions
IPC API (window.clui)
The preload bridge exposes window.clui in the renderer. Key methods:
// Send a prompt to the active tab's claude process
window.clui.sendPrompt(tabId: string, text: string): Promise<void>
// Approve or deny a pending tool-use permission
window.clui.resolvePermission(requestId: string, approved: boolean): Promise<void>
// Create a new tab (spawns a new claude -p process)
window.clui.createTab(): Promise<{ tabId: string }>
// Resume a past session by id
window.clui.resumeSession(tabId: string, sessionId: string): Promise<void>
// Subscribe to normalized events from a tab
window.clui.onTabEvent(tabId: string, callback: (event: NormalizedEvent) => void): () => void
// Get conversation history list
window.clui.getHistory(): Promise<SessionMeta[]>
Working with Tabs and Sessions
Creating a tab and sending a prompt (renderer)
import { useEffect, useState } from 'react'
export function useClaudeTab() {
const [tabId, setTabId] = useState<string | null>(null)
const [messages, setMessages] = useState<NormalizedEvent[]>([])
useEffect(() => {
window.clui.createTab().then(({ tabId }) => {
setTabId(tabId)
const unsubscribe = window.clui.onTabEvent(tabId, (event) => {
setMessages((prev) => [...prev, event])
})
return unsubscribe
})
}, [])
const send = (text: string) => {
if (!tabId) return
window.clui.sendPrompt(tabId, text)
}
return { messages, send }
}
Resuming a past session
async function resumeLastSession() {
const history = await window.clui.getHistory()
if (history.length === 0) return
const { tabId } = await window.clui.createTab()
const lastSession = history[0] // most recent first
await window.clui.resumeSession(tabId, lastSession.sessionId)
}
Permission Approval UI
Tool calls are intercepted by PermissionServer via PreToolUse HTTP hooks before execution. The renderer receives a permission_request event and must resolve it.
// Renderer: listen for permission requests
window.clui.onTabEvent(tabId, async (event) => {
if (event.type !== 'permission_request') return
const { requestId, toolName, toolInput } = event
// Show your approval UI, then:
const approved = await showApprovalDialog({ toolName, toolInput })
await window.clui.resolvePermission(requestId, approved)
})
// Main process: PermissionServer registers a hook with claude -p
How to use clui-cc-claude-overlay on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add clui-cc-claude-overlay
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches clui-cc-claude-overlay from GitHub repository aradotso/trending-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate clui-cc-claude-overlay. Access the skill through slash commands (e.g., /clui-cc-claude-overlay) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★63 reviews- ★★★★★Diego Huang· Dec 28, 2024
Registry listing for clui-cc-claude-overlay matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Pratham Ware· Dec 24, 2024
clui-cc-claude-overlay is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Anika Liu· Dec 8, 2024
I recommend clui-cc-claude-overlay for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Carlos Yang· Dec 4, 2024
clui-cc-claude-overlay reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Valentina Thomas· Dec 4, 2024
Solid pick for teams standardizing on skills: clui-cc-claude-overlay is focused, and the summary matches what you get after install.
- ★★★★★Hiroshi Liu· Nov 27, 2024
Keeps context tight: clui-cc-claude-overlay is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Noah Agarwal· Nov 27, 2024
Keeps context tight: clui-cc-claude-overlay is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Carlos Johnson· Nov 23, 2024
Registry listing for clui-cc-claude-overlay matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Ren Ndlovu· Nov 23, 2024
clui-cc-claude-overlay has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Omar Jain· Nov 19, 2024
clui-cc-claude-overlay reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 63