Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

OrcaRouter provider support for ShellSage

Aperta
  • Qualcosa non va?
#103 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
shell
Ambito
api, cli

Direzione di ricerca

Inizia tracciando la risoluzione del provider fastllm e il flusso esistente di base_url/api_key verso AsyncChat, quindi confronta i prefissi dei vendor attuali e le opzioni dei modelli CLI. Il lavoro è completato quando è integrato un provider opzionale compatibile con OrcaRouter senza modificare i provider esistenti, e il comportamento del provider è coperto dai check esistenti del progetto.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

ShellSage's tmux integration is what makes it click: because it reads your pane history (or a named pane via --pid) and accepts piped input, a line like journalctl --since "1 hour ago" | ssage explain this error turns a stack trace into a plain-language diagnosis without leaving the terminal. The ssage_clear binding is a thoughtful design choice too — Ctrl-L gains real clear semantics for the assistant while your own scrollback stays intact.

That matters because people who live in a shell want answers where they already are, and model choice is part of that. ShellSage already resolves models through fastllm and accepts a custom base_url/api_key, so OrcaRouter would slot in as one more optional provider alongside Claude, GPT, and Ollama.

Proposal

I'd like to propose adding OrcaRouter as an optional provider. It would not replace or change any existing provider — Claude, GPT, Gemini, Ollama, OpenRouter, and the rest would keep working exactly as they do today.

I'm an engineer on the OrcaRouter team, so I'll be upfront about my angle here.

What this would give ShellSage users
  • One endpoint, many models — chat, reasoning, image, and video models behind a single OpenAI-compatible API, so --model can point at a much wider catalog.
  • Automatic routing and provider failover — if a provider degrades mid-session, a request routes to a healthy equivalent instead of dropping your question.
  • Prompt caching — especially relevant here, since history_lines = -1 ships the whole terminal history on every call; caching makes that repeated context cheaper and faster.
  • Usage tracking and budgets — visibility into what a long-running shell session actually costs.
Integration

OrcaRouter exposes an OpenAI-compatible API and uses standard API-key authentication. Concretely, this fits the abstraction you already have: an orcarouter-style prefix resolved by fastllm next to the current vendor prefixes, or simply the existing base_url / api_key config and CLI options, both of which already flow through to AsyncChat. To be clear, I haven't written or tested any code for this — it's a proposal for your consideration.

OrcaRouter is already part of the open-source ecosystem, with integrations such as goose, promptfoo, and models.dev / OpenCode.

One disclosure: we run an optional open-source partner program where approved OSS projects can receive a 5% revenue share from OrcaRouter usage attributed to their integration. Taking part is not a prerequisite for the integration, and I'm glad to follow whatever disclosure or governance rules you'd prefer.

Details: https://www.orcarouter.ai/built-with

Would you be open to this? If so, I'd be happy to prepare an implementation PR once you've had a chance to weigh in.

Lingua principale
Jupyter Notebook
Stelle
409
Fork
44
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di AnswerDotAI/shell_sage

Tutte le issue di AnswerDotAI/shell_sage

Issue simili

Altre issue su Backend & API Design

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.