Celeste CLI MCP sunucusu
Commit 13 Kas 2026Zengin bir TUI kullanarak kod incelemeleri, semantik aramalar ve otonom geliştirme görevleri gerçekleştiren agentic bir terminal yapay zeka asistanı.
Ayrıca bilinen adı whykusanagi/celeste-cli
- Yıldızlar
- 1
- Araçlar
- 10
- İndirmeler, 30 gün
- —
- En son sürüm
- —
- Son commit
- 13 Kas 2026
- Lisans
- MIT
Celeste CLI MCP nedir?
Celeste CLI bir MCP sunucusudur. Zengin bir TUI kullanarak kod incelemeleri, semantik aramalar ve otonom geliştirme görevleri gerçekleştiren agentic bir terminal yapay zeka asistanı. 10 araç sunar; örneğin goal, type, workspace.
Özet, projenin README dosyasından oluşturuldu
Celeste CLI MCP sunucusu hakkında
Celeste CLI, etkileşimli ve terminal tabanlı bir yapay zeka asistanı isteyen geliştiriciler için tasarlanmış, bağımsız bir agentic geliştirme aracıdır. Benzersiz bir estetiğe sahip özel bir TUI sunar ve dosya I/O, shell yürütme, git yönetimi ve web aramaları gibi görevler için 48 yerleşik araç sağlar. Sistem; TypeScript, Python, Rust ve C/C++ gibi dillerdeki karmaşık kod tabanlarını anlamak için tree-sitter ayrıştırması ile desteklenen bir kod grafiği ve semantik arama kullanır.
Kullanıcılar aracı üç farklı modda çalıştırabilir: etkileşimli sohbet, uzun süreli görevler için otonom agent veya çıktıları eleştirmek için ikinci bir model kullanan bir orkestratör. Sakana AI, OpenAI, Anthropic, Gemini ve Grok gibi geniş bir yapay zeka sağlayıcısı yelpazesinin yanı sıra yerel OpenAI uyumlu sunucuları da destekler. Modern editörleri kullananlar için Zed veya JetBrains IDE'leri için bir Agent Client Protocol agent'ı olarak işlev görebilir. Araç erişimini yönetmek için bir izin sistemi ve dosya değişikliklerini geri almak veya geri döndürmek için bir checkpoint sistemi içerir.
Neler yapabilirsiniz
- 1Yapısal kod analiziGraf tabanlı analiz kullanarak hata yutma veya sabit değer kullanımı gibi sorunları tespit etmek için derinlemesine kod incelemeleri gerçekleştirin.
- 2Semantik kod tabanı navigasyonuTemel kod yapısını anlayan semantik sorgular kullanarak büyük depolar içinde arama yapın.
Projenin README dosyasından alınmıştır. Her kullanım durumu, oradaki bir alıntı ile kontrol edilir.
Celeste CLI MCP araçları 10
README dosyasından algılandıgoaltypeworkspacetask_iddepends_onmax_turnsisolate_worktreebackground_afterpersonamessage
| goal | — | |
| type | — | |
| workspace | — | |
| task_id | — | |
| depends_on | — | |
| max_turns | — | |
| isolate_worktree | — | |
| background_after | — | |
| persona | — | |
| message | — |
Yapılandırma
CELESTE_API_ENDPOINTCELESTE_API_KEYGROK_API_KEYOPENAI_API_KEYTAROT_AUTH_TOKENVENICE_API_KEY
| Ad | Açıklama | Sunucu |
|---|---|---|
| CELESTE_API_ENDPOINT | — | |
| CELESTE_API_KEY | — | |
| GROK_API_KEY | — | |
| OPENAI_API_KEY | — | |
| TAROT_AUTH_TOKEN | — | |
| VENICE_API_KEY | — |
Otomatik kontroller
Çalıştırıldı 14 Kas 2026Tam rapor →Henüz doğrulanmadı. Bir sunucunun 80 puana, ciddi bir bulgu olmamasına ve kontrol edebilmemiz için yeterli veriye ihtiyacı vardır. Kontroller nasıl çalışır · Daha fazla puan için nelerin düzeltileceği
- Kaynak deposu bağlantılı ve erişilebilirwhykusanagi/celeste-cli is public and reachablegithub.com/whykusanagi/celeste-cli ↗Geçti
- Paket, bu depoyu kaynağı olarak gösteriyorKontrol edilmedi
- Derleme kökeni (Sigstore onayı)Kontrol edilmedi
- Açık kaynak lisansı (OSI)MITspdx.org/licenses/MIT.html ↗Geçti
- Son bir yıl içinde commit veya sürüm mevcutLast commit or release 2026-11-06github.com/whykusanagi/celeste-cli ↗Geçti
- OpenSSF ScorecardKontrol edilmedi
- Paket adı popüler bir pakete yakın değilKontrol edilmedi
- Pakette veya bağımlılıklarında kritik uyarı yokKontrol edilmedi
- Modele yönelik gizli talimat yok10 tool descriptions and the README read; no override phrases, credential paths or hidden charactersGeçti
- Yıkıcı araçlar etiketlenmişNo tool named like delete, drop or execGeçti
- Uzak uç nokta MCP el sıkışmasına yanıt veriyorKontrol edilmedi
Character artwork by いかわさ (ikawasa23)
👁️ Celeste CLI - Interactive AI Assistant
A premium, corruption-aesthetic command-line interface for CelesteAI
Built with Charm's Bubble Tea for flicker-free, modern terminal experiences
✨ What is Celeste CLI?
Celeste CLI is a full standalone agentic development tool with her own persona, featuring:
- 🎨 Premium TUI - Flicker-free rendering with corrupted-theme aesthetics
- 🔮 48 Built-in Tools - File I/O, shell, web search, code graph, code review, collections search, git, crypto, subagent orchestration, and more
- 📖
.grimoireProject Context - Persona-themed project config files with auto-discovery;AGENTS.md/CLAUDE.mdare read too - 🧠 Code Graph + Semantic Search - MinHash + BM25 fused ranking with LSH band table for sub-linear queries, structural rerank; tree-sitter parsing (TypeScript, PHP, Python, Rust, Java, C/C++ and Ruby) for accurate call-graph edges in release binaries (a
CGO_ENABLED=0source build falls back to regex parsers); embedded celeste-stopwords v1.0.0 noise filter - 🔍 Graph-Based Code Review - Structural analysis detecting stubs, lazy redirects, placeholders, error swallowing, and hardcoded values
- 🔌 Direct Codegraph MCP Tools -
celeste_index,celeste_code_search,celeste_code_review,celeste_code_graph,celeste_code_symbolsserved verbatim from the cached graph (no chat-LLM round-trip, nomax_tokensceiling, streaming progress notifications) - 🔒 Permission System - Multi-layer allow/deny/ask rules with pattern matching
- 💾 Session Persistence - JSONL auto-save, resume, file checkpointing with stale detection and revert
- 🌐 Multi-Provider - Sakana AI (default), Grok/xAI, OpenAI, Anthropic (native SDK), Gemini, Venice.ai, Vertex AI, OpenRouter, local OpenAI-compatible servers
- 💰 Cost Tracking - Per-model pricing with live session cost display
- 🪝 Hooks - Commands that run around tool calls, prompts and sessions (
hooks.json, or a grimoire## Hookssection); a repository's hooks run only after you approve them (celeste hooks list,celeste hooks trust). See docs/HOOKS.md - 🧱 Sandbox (opt-in) -
bashcan run under the OS sandbox (seatbelt on macOS, bubblewrap on Linux), writing only to the workspace, temp directories and build caches, with the network optionally cut. See docs/SANDBOX.md - ↩️ Checkpoints - Every file change is checkpointed per session:
/undo,/diffand/rewindin the chat,celeste revert <file>from the shell - 🧠 Extended Thinking - Leverage reasoning tokens (Claude, Gemini, Grok) with
/effortcontrol - 🖼️ Image Input - Multimodal support for vision-capable models
- 🎭 Celeste persona - The full persona in official releases (encrypted, all rights reserved); a public persona in source builds. See Persona and docs/PERSONALITY.md
- 🔗 Blockchain Tools - IPFS, Alchemy, wallet security monitoring
Three Ways to Run
| Mode | Command | What it does |
|---|---|---|
| Chat | celeste chat (default) |
Interactive chat with auto-looping tool calls (25-turn safety cap). |
| Agent | /agent <goal> (in TUI) or celeste agent --goal "..." |
Fully autonomous multi-turn agent with planning, file I/O, checkpointing, and resume. For long-running tasks. |
| Orchestrator | /orchestrate <goal> (in TUI) |
Agent run with a second reviewer model that critiques and debates the output. For high-quality deliverables. |
Chat vs Agent: Chat is interactive with tool auto-looping — you guide the conversation while Celeste calls tools as needed. Agent is autonomous, with a planning phase, a checkpoint store and workspace awareness. Both run on the same tool loop, with the same caps, guards, permissions and hooks. The orchestrator adds a reviewer model on top of the agent. Editors that speak the Agent Client Protocol (Zed, JetBrains) can run Celeste as their agent with
celeste acp.
In your editor: celeste acp runs celeste as an Agent Client Protocol agent for Zed and the JetBrains IDEs: the editor's agent panel drives the chat, with tool calls, plans and permission prompts shown in the editor. See docs/ACP.md for the setup.
🚀 Quick Start
Quick Install (Recommended)
Upgrading from 1.x? Read MIGRATING-2.0.md first: it lists every 2.0 change that can affect an existing setup (install path, persona, hooks, config keys, environment variables, custom tools, the permission prompt) and what to do about each.
If you have Go 1.26+ installed:
go install github.com/whykusanagi/celeste-cli/v2/cmd/celeste@latest
go install needs the Go module proxy (the default, proxy.golang.org). With GOPROXY=direct it
can fail on a dependency whose upstream tag was moved after the proxy cached it (for example
github.com/charmbracelet/glamour v1.0.0 reports a checksum mismatch); the signed release
binaries below avoid this.
The celeste binary is installed to $GOPATH/bin (or ~/go/bin by default). The first time
you run a command with it (celeste chat, say; help, version, update and persona don't
count), it downloads the official signed release binary of the same version from
Releases, checks its GPG signature and
checksums against the release key built into celeste, replaces itself and carries on, so you
get the full persona from the first run (stderr says
celeste: installing the official vX.Y.Z build ...). If the download fails
(offline, say), that run uses the public persona and celeste tries again in an hour.
celeste update moves to a newer release; celeste update --check only reports one. Set
CELESTE_NO_AUTO_UPGRADE=1 to keep the binary go install built.
Requirements:
- Go 1.26.0 or higher
$GOPATH/bin(or~/go/bin) in your PATH
No Go toolchain? Download a pre-built, signed binary for your platform from the Releases page and verify it (see Security & Verification below).
To add to PATH:
export PATH="$PATH:$(go env GOPATH)/bin"
Build from source
# Clone the repository
git clone https://github.com/whykusanagi/celeste-cli.git
cd celeste-cli
# Build + install to ~/.local/bin (handles macOS code-signing for you)
make install
The code graph's tree-sitter parsers are C, so a source build compiles them with CGo and
needs a C compiler (Xcode's command line tools, gcc, or MinGW-w64 on Windows). With
CGO_ENABLED=0, celeste still builds and the code graph falls back to regex parsers, with
less accurate call edges. So does a build with CGO_ENABLED and CC both unset on a machine
whose default C compiler is missing, since Go then turns CGo off by itself; an explicit
CGO_ENABLED=1, or a CC naming a compiler that is missing, fails the build instead.
A cross-compile (GOOS or GOARCH not the host's) with CGO_ENABLED unset also builds
without CGo. Release binaries always include tree-sitter.
A build from a checkout never downloads anything. It runs Celeste's public persona (a
one-line identity, the honesty rule and the voice boundary rule) and says so at startup: the
full persona ships only in official release binaries, which go install and the Releases page
give you.
macOS note: don't
cpthe binary over an existing~/.local/bin/celeste— on Apple Silicon that invalidates its ad-hoc code signature and the kernel will SIGKILL it at launch (zsh: killed celeste).make installbuilds straight to the destination and re-signs. If you install by hand, build directly to the target and re-sign:go build -o ~/.local/bin/celeste ./cmd/celeste codesign --force --sign - ~/.local/bin/celeste # macOS only
Persona
Official release binaries, and go install builds once they have upgraded themselves, run
Celeste's full persona. Builds from a checkout run the public persona. To check a binary, run
celeste persona verify: it prints official persona: ... and exits 0 on an official build,
and exits 1 with the reason otherwise. It never downloads, so after a fresh go install run
celeste update first (it installs the official binary), then celeste persona verify. A local model with a small context window gets a smaller
persona profile; set context_limit in your config to the server's real window. How the
persona is built and chosen: docs/PERSONALITY.md. How to verify a
download: VERIFY.md.
First Run
Sakana/Fugu (the shipped default): a fresh install already points at
https://api.sakana.ai/v1 with model fugu, so you only need a key.
celeste config --set-key YOUR_SAKANA_KEY
celeste chat
xAI/Grok: not the default any more, so set the URL too or your key goes to
Sakana and you get a confusing 401.
celeste config --set-url https://api.x.ai/v1
celeste config --set-key YOUR_XAI_KEY
celeste chat
With Collections (RAG):
celeste config --set-key YOUR_XAI_KEY
celeste config --set-management-key YOUR_XAI_MANAGEMENT_KEY
celeste collections list # see available collections
celeste collections enable <id> # enable for chat
celeste chat
OpenAI:
celeste config --init openai
celeste -config openai config --set-key YOUR_OPENAI_KEY
celeste -config openai chat
Sakana (Fugu):
celeste config --init sakana
celeste -config sakana config --set-url https://api.sakana.ai/v1 --set-key YOUR_SAKANA_KEY --set-model fugu
celeste -config sakana chat
Get a key from the Fugu install (curl -fsSL https://sakana.ai/fugu/install | bash)
or your Sakana account. Use --set-model fugu-ultra for the heavier multi-agent variant.
Other providers: celeste config --init <name> where name is: openai, grok, elevenlabs, venice, sakana, digitalocean
Project Setup
Celeste reads a project's .grimoire and its AGENTS.md / CLAUDE.md (from the
workspace up to the git root) into every session. It writes nothing into your
project on its own; create the files when you want them:
cd your-project
celeste init # create .grimoire
celeste init --agents # also create AGENTS.md (build and test commands)
celeste index # build code graph
celeste index status # check graph stats
In the chat, /init and /init agents do the same. An existing file is never overwritten.
🔒 Security & Verification
All Celeste CLI releases are cryptographically signed with GPG to ensure authenticity and integrity.
Quick Verification
Before using a downloaded binary, verify its authenticity:
# Download verification script
curl -O https://raw.githubusercontent.com/whykusanagi/celeste-cli/main/scripts/verify.sh
chmod +x verify.sh
# Verify your download
./verify.sh celeste-linux-amd64.tar.gz
Manual Verification
For manual verification or more details, see the complete Verification Guide.
Release Signing:
- All commits are GPG-signed
- All releases include GPG signatures
- Checksums are signed with GPG
- Complete manifest with build metadata
PGP Key Information:
- Key ID:
875849AB1D541C55 - Fingerprint:
9404 90EF 09DA 3132 2BF7 FD83 8758 49AB 1D54 1C55 - Keybase: @whykusanagi
- GitHub: whykusanagi.gpg
Import Key — use the repository copy; it carries the signing subkey the releases are signed with:
# From this repository (recommended — complete key with signing subkey)
curl -O https://raw.githubusercontent.com/whykusanagi/celeste-cli/main/whykusanagi.asc
gpg --import whykusanagi.asc
# Cross-check the primary fingerprint against the key GitHub serves:
gpg --fingerprint 940490EF09DA31322BF7FD83875849AB1D541C55
# → 9404 90EF 09DA 3132 2BF7 FD83 8758 49AB 1D54 1C55
For security issues, see our Security Policy or contact security@whykusanagi.xyz.
📚 Table of Contents
- Installation
- Security & Verification
- Features
- Tool System (48 Tools)
- Claude Code Integration
- Comparison
- LLM Provider Compatibility
- Function Calling Flow
- Configuration
- Usage
- Architecture
- Documentation
- Contributing
🎯 Features
Interactive TUI Mode
- Flicker-Free Rendering - Double-buffered Bubble Tea rendering (no screen tearing)
- Scrollable Chat - PgUp/PgDown navigation through conversation history
- Input History - Arrow keys to browse previous messages (like bash history)
- Skills Panel - Real-time skill execution status with demonic eye animation
- Corrupted Theme - Lip Gloss styling with pink/purple abyss aesthetic
- Real Streaming + Corruption Animation - Token-by-token streaming with corrupted glitch phrases at the typing cursor
- Markdown Rendering - glamour-powered markdown with corrupted theme (code blocks, tables, headers, bold)
Tool System
48 built-in tools powered by AI function calling. 41 are always on. A further 6 code-graph tools appear once you index a project, plus collections search when you configure collections:
- Dev Tools (bash, read/write/patch files, search, list files)
- Code Graph (semantic search with MinHash+BM25 fusion, code review, symbol analysis, tree-sitter parsing)
- Direct Codegraph MCP Tools (
celeste_index,celeste_code_search,celeste_code_review,celeste_code_graph,celeste_code_symbols— verbatim, no chat-LLM round-trip) - Git (status, log)
- Web (search, fetch)
- Information Services (Weather, Currency, Twitch, YouTube)
- Utilities (Conversions, Encoding, Generators, QR codes)
- Productivity (Reminders, Notes, Todo tracking)
- Blockchain (IPFS, Alchemy, wallet security)
- Subagent Orchestration (
spawn_agent,post_message)
Chat offers all 48, plus spawn_agent and post_message, which the chat registers
itself. Agent runs offer 24 of them: the dev, git, web and code-graph tools, save_memory,
todo, ask, find_tools, audio_render and collections search. celeste message
sends none. Tools from MCP servers and custom skills come on top, in both modes.
Collections Support (xAI RAG)
- Upload Custom Documents - Create knowledge bases with your own documentation
- Semantic Search - Celeste automatically searches collections when answering questions
- Interactive TUI - Manage collections with
/collectionscommand in chat - CLI Management - Create, upload, enable/disable collections from command line
- Multiple Collections - Organize by topic, enable only what's relevant
See Collections Guide for setup and usage.
Tool System (v1.7)
- MCP (Model Context Protocol) support for external tool servers
- Permission system with configurable allow/deny rules
- Streaming tool execution with concurrent dispatch
- Automatic context window management
Session Management
- Conversation Persistence - Auto-save and resume sessions seamlessly
- File Revert -
celeste revert <file> [--session id] [--force]restores a file from the latest session that changed it - Message History - Full conversation logging with timestamps
- Session Listing - Browse and load previous sessions by ID
- Session Clearing - Bulk delete sessions when needed
Multi-Provider Support (9 Chat Providers)
celeste uses the model the provider serves now. At startup it reads the provider's model list (cached for a day under ~/.celeste/cache/models); if your configured model has been retired, it falls back to the provider's current default and says so. A model is replaced only when celeste is sure it's gone: a model missing from the list is first checked with the provider where it can answer (Anthropic, OpenAI, xAI), so aliases keep working, and presets (@...), fine-tunes (ft:...) are never touched. Your config file is not changed. To turn this off, set "pin_model": true in the config or CELESTE_PIN_MODEL=1; in the chat, /set-model <name> --force pins that model until you switch endpoints. Gemini, Vertex, DigitalOcean and local servers publish no list, so their configured model is used as is. The model names below are offline fallbacks.
- ✅ Grok/xAI (grok-4.20-0309-non-reasoning) - reliable tool calling, no reasoning-token burn, never routes to the cost-prohibitive grok-4.3 • Token tracking ✓
- ✅ OpenAI (gpt-4.1-mini, gpt-4.1) - Full function calling with streaming • Token tracking ✓
- ✅ Anthropic Claude (claude-sonnet-4-5) - Native SDK with prompt caching and extended thinking • Token tracking ✓
- ✅ Google Gemini AI (gemini-flash-latest) - Simple API keys, free tier, full streaming • Token tracking ✓
- ⚠️ Google Vertex AI (gemini-2.0-flash, unverified) - Enterprise, requires GCP project + billing. The default has not been checked against Vertex's own model lifecycle • Token tracking ✓
- ⚠️ Venice.ai (Venice's own default, currently venice-uncensored-1-2) - NSFW mode, image generation/upscaling. Tool calling depends on the model (checked against the live Venice catalog) • Token tracking ✓
- ✅ OpenRouter (multi-provider) - Parallel function calling support • Token tracking ✓
- ✅ Sakana AI (fugu, fugu-ultra) - DEFAULT - 1M context, OpenAI-compatible chat completions, deep reasoning • Token tracking ✓
- ✅ Local (mlx-vlm, Ollama, LM Studio, llama.cpp) - any OpenAI-compatible server on this machine or the local network, any port; tools supported. No
api_keyneeded at all • Cost tracked as $0
Nine chat providers: eight with tool calling, and Venice, whose tool calling depends on the selected model.
celeste providers lists 11: these nine plus DigitalOcean (its tools run in its own
cloud) and ElevenLabs (voice).
Dynamic Model Selection - Auto-selects best tool-calling model per provider Capability Indicators - Visual feedback (✓ skills / ⚠️ no skills) in header
Configuration
- JSON-based Config - Modern
~/.celeste/config.jsonformat - Named Configs - Multi-profile support (openai, grok, venice, etc.)
- Skills Config - Separate
skills.jsonfor skill-specific API keys - Secrets Handling - Separate
secrets.jsonfor backward compatibility - Persona - Always on in chat and agent runs, sized to the model's context window (
context_limit); tune it with/personasliders - Environment Override - Env vars override file config
🔮 Tool System (48 Tools)
Celeste CLI uses OpenAI-compatible function calling to power its tools. You don't invoke tools directly — you chat naturally, and the AI decides when to call them.
Dev Tools (10 Tools)
| Tool | Description |
|---|---|
| bash | Execute shell commands in the workspace |
| read_file | Read files with checkpointing |
| write_file | Write files with snapshot backup |
| patch_file | Apply targeted edits to files |
| splice_file | Move a region between files by anchors/line-ranges (deterministic, no model-routed bytes) |
| list_files | List directory contents with glob patterns |
| search | Search file contents with regex |
| git_status | Show working tree status |
| git_log | Show commit history |
| recall_tool_result | Restore a tool result that context compaction pruned from the conversation |
Code Graph Tools (6 Tools)
| Tool | Description |
|---|---|
| code_search | MinHash semantic search across all indexed symbols |
| code_review | Graph-based code review (6 categories: stubs, lazy redirects, placeholders, TODOs, error swallowing, hardcoded values) |
| code_graph | Query symbol relationships and call chains |
| code_symbols | List symbols in a file or package |
| code_impact | Blast-radius analysis: which callers are affected by a changed symbol |
| code_snapshot | Save and diff graph state to track what changed between sessions |
v1.10 accuracy improvements: STUB detection now skips dunder methods (
__init__,__lt__, …),@abstractmethod-decorated methods, and methods onProtocol/ABC/ABCMetaclasses — eliminating the largest classes of false positives. Decorator@syntaxcalls and@property.setterassignments are now captured as call edges, producing more accurate impact/caller counts.
Celeste CLI MCP soruları
Celeste CLI MCP hangi araçları sunar?
10 araç sunar; bunlar arasında goal, type, workspace, task_id, depends_on yer alır.
Celeste farklı LLM sağlayıcılarını destekliyor mu?
Evet; Sakana AI, Grok/xAI, OpenAI, Anthropic, Gemini, Venice.ai, Vertex AI, OpenRouter ve yerel OpenAI uyumlu sunucular dahil olmak üzere birden fazla sağlayıcıyı destekler.
Celeste kod analizini nasıl gerçekleştiriyor?
MinHash ve BM25 aracılığıyla semantik arama yapan bir kod grafiği ve desteklenen dillerde doğru çağrı grafiği (call-graph) kenarları için tree-sitter ayrıştırması kullanır.
Celeste'i bir sandbox içinde çalıştırabilir miyim?
Evet; dosya yazma ve ağ erişimini kısıtlamak için bash komutlarının işletim sistemi sandbox'ı (macOS'ta seatbelt, Linux'ta bubblewrap) altında çalıştığı bir sandbox seçeneğini kullanabilirsiniz.