tokenrhythm/opensquilla

OpenSquilla — Token-Efficient AI Agent with same budget, higher intelligence density

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 53 minutes ago
Added to GitGenius on September 1st, 2026
Created on May 6th, 2026
Open Issues & Pull Requests: 322 (+0)
GitHub issues: Enabled
Number of forks: 558
Total Stargazers: 6,987 (+0)
Total Subscribers: 137 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 6.8 hours
Mean response time: 26.4 hours
90th percentile: 3.1 days
Tracked items: 5

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 7
New in 7 days: 5
Closed in 7 days: 2
Avg open age: 13 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 4
Closed in 7 days: 2
Comments in 7 days: 1
Events in 7 days: 11

Top labels

  • bug (7)
  • has-linked-pr (3)
  • needs-design (1)
  • source:github (1)

Detailed Description

OpenSquilla is a token-efficient microkernel AI agent that routes tasks to the most cost-effective language model for each request.

The tool addresses the challenge of running capable AI agents within constrained token budgets. It uses a local model router to direct each turn to the cheapest model capable of handling it, paired with persistent memory, a layered sandbox, built-in web search, and on-device embeddings. All entry points—Web UI, CLI, and chat channels—flow through the same core loop, ensuring consistent tool dispatch, retries, and decision logging across interfaces. The agent supports multiple LLM providers including TokenRhythm, OpenRouter, OpenAI, Anthropic, Ollama, DeepSeek, Gemini, Qwen/DashScope, and over twenty others through a pluggable provider layer that requires no code or configuration schema changes.

Developers should choose this tool if they need an AI agent that maximizes capability within a fixed token budget and want consistent behavior across CLI, web, and chat interfaces. It suits projects where cost efficiency matters alongside agent performance, and where the ability to swap between multiple LLM providers without code changes is valuable. The tool's microkernel architecture and unified turn loop distinguish it from agents that handle different interfaces separately.

The project maintains active development with continuous integration checks passing. A technical report on agentic routing and multi-model ensemble routing is available, documenting how the router's approach surpasses certain baseline models. Documentation spans product guides, API references, and implementation details across multiple languages.