Skip to content

Bibliography

Purpose

Provenance for the external sources cited in the Research/ rounds. This is an evidence ledger, not a knowledge record: a URL listed here is a lead to assess, not a verified project fact.

Verification status uses the convention from Knowledge-Base.md:

  • Unassessed — cited by a research round; not yet examined locally.
  • Partially assessed — some content retrieved or quoted by the researcher, but not verified locally.
  • Verified locally — checked against the local environment.
  • Not applicable — no verification expected (e.g., reference material only).

Unless noted, all entries were accessed 2026-08-01 and are Unassessed.

Official Claude Code documentation

Claude Code statusline documentation (EN)

  • URL: https://code.claude.com/docs/en/statusline
  • Used by: Research/2026-08-01 - Perplexity Research Round 01 - Initial Investigation.md, Research/2026-08-01 - Perplexity Research Round 02 - OmniRoute Metadata.md
  • Relevance: Primary source for the statusline input contract — script-driven over stdin, with documented fields model.id, model.display_name, workspace.current_dir, context-window, rate-limit, and cost data.
  • Verification status: Partially assessed — authoritative doc reviewed (2026-08-02); schema confirmed against the local session transcript and statusline payload (no resolved-provider field exists).

Claude Code statusline documentation (ES)

  • URL: https://code.claude.com/docs/es/statusline
  • Used by: Research/2026-08-01 - Perplexity Research Round 01 - Initial Investigation.md
  • Relevance: Localized copy cited for the claim that the statusline is an external command whose printed output becomes the bottom bar, and that no confirmed mechanism exposes the hidden routed provider.
  • Verification status: Unassessed

Claude Code statusline documentation (IT)

  • URL: https://code.claude.com/docs/it/statusline
  • Used by: Research/2026-08-01 - Perplexity Research Round 01 - Initial Investigation.md, Research/2026-08-01 - Perplexity Research Round 02 - OmniRoute Metadata.md
  • Relevance: Localized copy cited for the documented statusline input fields and for the absence of a documented resolved-provider field for dynamic routing.
  • Verification status: Unassessed

Claude Code statusline documentation (JA)

  • URL: https://code.claude.com/docs/ja/statusline
  • Used by: Research/2026-08-01 - Perplexity Research Round 01 - Initial Investigation.md
  • Relevance: Localized copy cited for the documented model.id / model.display_name fields available to a custom statusline.
  • Verification status: Unassessed

Claude Code statusline documentation (ZH-TW)

  • URL: https://code.claude.com/docs/zh-TW/statusline
  • Used by: Research/2026-08-01 - Perplexity Research Round 02 - OmniRoute Metadata.md
  • Relevance: Localized copy cited for the claim that Claude Code documents built-in statusline fields but no arbitrary passthrough/custom-metadata mechanism.
  • Verification status: Unassessed

OmniRoute official documentation and source

OmniRoute user guide

  • URL: https://github.com/diegosouzapw/OmniRoute/blob/main/docs/guides/USER_GUIDE.md
  • Used by: Research/2026-08-01 - Perplexity Research Round 01 - Initial Investigation.md, Research/2026-08-01 - Perplexity Research Round 02 - OmniRoute Metadata.md
  • Relevance: Source for OmniRoute's OpenAI-compatible routing, provider-native model IDs, and model mapping; cited for what the gateway can know about the resolved model versus what it forwards to Claude Code.
  • Verification status: Unassessed

OmniRoute API reference

  • URL: https://github.com/diegosouzapw/OmniRoute/wiki/API-Reference
  • Used by: all four Research/ rounds
  • Relevance: Central reference for candidate observability endpoints and response headers (X-OmniRoute-Session-Id, X-OmniRoute-Cache, /api/usage/request-logs, /api/usage/logs, /api/sessions, /api/analytics/auto-routing, /api/cloud/model/resolve, /v1/models).
  • Verification status: Partially assessed — the researcher retrieved only partial schema content; several endpoint schemas remain unverified.

OmniRoute CLI tools

  • URL: https://github.com/diegosouzapw/OmniRoute/wiki/CLI-Tools
  • Used by: Research/2026-08-01 - Perplexity Research Round 01 - Initial Investigation.md
  • Relevance: Cited for the claim that the frontend interacts with an OpenAI-compatible endpoint and may only see the alias it requested, not the final provider-native model.
  • Verification status: Unassessed

OmniRoute CLI integrations

  • URL: https://github.com/diegosouzapw/OmniRoute/wiki/CLI-Integrations
  • Used by: Research/2026-08-01 - Perplexity Research Round 02 - OmniRoute Metadata.md
  • Relevance: Cited for the recommendation that a wrapper statusline script prefer OmniRoute-derived metadata and fall back to model.display_name.
  • Verification status: Unassessed

OmniRoute Auto-Combo wiki page

  • URL: https://github.com/diegosouzapw/OmniRoute/wiki/Auto-Combo
  • Used by: Research/2026-08-01 - Perplexity Research Round 03 - Source Code Investigation.md
  • Relevance: Strongest implementation evidence for how auto-routing resolves a request to a concrete provider/model (virtual combo in open-sse/services/autoCombo/virtualFactory.ts, scoring in scoring.ts, engine.ts, autoPrefix.ts); states the virtual combo is in-memory and never persisted to DB.
  • Verification status: Partially assessed — file names and flow quoted from the wiki; exact in-memory storage of the resolved route unverified.

OmniRoute CHANGELOG

  • URL: https://github.com/diegosouzapw/OmniRoute/blob/main/CHANGELOG.md
  • Used by: Research/2026-08-01 - Perplexity Research Round 04 - Endpoint Investigation.md
  • Relevance: Cited for the note that /v1beta/models returns only public metadata (name, strategy, model ids, providerId, description) with internal routing details stripped.
  • Verification status: Unassessed

OmniRoute community activity

OmniRoute issue #3368 — auto-routing with web-session / no-auth flows

  • URL: https://github.com/diegosouzapw/OmniRoute/issues/3368
  • Used by: Research/2026-08-01 - Perplexity Research Round 03 - Source Code Investigation.md
  • Relevance: Related community discussion about routing behavior and credentials discovery; not evidence of a resolved-model passthrough feature request.
  • Verification status: Unassessed

OmniRoute discussion #7487 — consolidating elements into a single window

  • URL: https://github.com/diegosouzapw/OmniRoute/discussions/7487
  • Used by: Research/2026-08-01 - Perplexity Research Round 03 - Source Code Investigation.md
  • Relevance: Community thread; could not be verified as requesting resolved-model passthrough for statuslines.
  • Verification status: Unassessed

Community statusline projects

ClaudeCodeStatusLine (daniel3303)

  • URL: https://github.com/daniel3303/ClaudeCodeStatusLine
  • Used by: Research/2026-08-01 - Perplexity Research Round 01 - Initial Investigation.md, Research/2026-08-01 - Perplexity Research Round 02 - OmniRoute Metadata.md
  • Relevance: Most-aligned community project: compact single-line display of model, cwd/branch, tokens, effort, and rate limits; cited as a layout reference and a wrapper-script starting point.
  • Verification status: Unassessed

claude-code-statusline (ohugonnot)

  • URL: https://github.com/ohugonnot/claude-code-statusline
  • Used by: Research/2026-08-01 - Perplexity Research Round 01 - Initial Investigation.md
  • Relevance: Community statusline focused on live quota/reset tracking with a simple shell-script install path; cited for cost/rate-limit display and for avoiding aggressive polling.
  • Verification status: Unassessed

ccstatusline (sirmalloc)

  • URL: https://github.com/sirmalloc/ccstatusline
  • Used by: Research/2026-08-01 - Perplexity Research Round 01 - Initial Investigation.md
  • Relevance: Community statusline positioned as a highly customizable formatter; cited for the recommendation to use a custom script rather than Claude Code's auto-generated default.
  • Verification status: Unassessed

Community blog posts

Customize Claude Code Status Line (alexop.dev)

  • URL: https://alexop.dev/posts/customize_claude_code_status_line/
  • Used by: Research/2026-08-01 - Perplexity Research Round 02 - OmniRoute Metadata.md
  • Relevance: Cited for the claim that scripts parsing .model.display_name will show auto whenever Claude Code emits it, because the script is not resolving the backend itself.
  • Verification status: Unassessed

Claude Code statusline walkthrough (andynu.github.io)

  • URL: https://andynu.github.io/claude-code/2026/04/02/claude-code-statusline.html
  • Used by: Research/2026-08-01 - Perplexity Research Round 02 - OmniRoute Metadata.md
  • Relevance: Cited for the claim that the statusline consumer is limited to the payload Claude Code already sends, with no confirmed mechanism for rendering arbitrary gateway metadata.
  • Verification status: Unassessed

Claude Code custom statusline (didof.dev)

  • URL: https://didof.dev/blog/claude-code-custom-statusline/
  • Used by: Research/2026-08-01 - Perplexity Research Round 02 - OmniRoute Metadata.md
  • Relevance: Cited for the compact model · branch · ctx% · quota layout matching the strongest community patterns.
  • Verification status: Unassessed

Claude statusline notes (felipeelias.github.io)

  • URL: https://felipeelias.github.io/2026/03/17/claude-statusline.html
  • Used by: Research/2026-08-01 - Perplexity Research Round 01 - Initial Investigation.md
  • Relevance: Cited for the recommendation to drop time as clutter and keep a compact model/branch/context/cost bar.
  • Verification status: Unassessed

Claude Code statusline note (note.com)

  • URL: https://note.com/st_dev0/n/n775d3d560ddc?hl=en
  • Used by: Research/2026-08-01 - Perplexity Research Round 01 - Initial Investigation.md
  • Relevance: Community example cited for building the script on documented fields such as workspace.current_dir, git branch, and context-window usage rather than hardcoded values.
  • Verification status: Unassessed

Third-party reference

DeepWiki — OmniRoute logs and audit (section 9.4)

  • URL: https://deepwiki.com/diegosouzapw/OmniRoute/9.4-logs-and-audit
  • Used by: Research/2026-08-01 - Perplexity Research Round 04 - Endpoint Investigation.md
  • Relevance: Source for the logging architecture: request logs stored in SQLite call_logs, detailed logs captured as JSON artifacts in a ring buffer; basis for ranking /api/usage/request-logs as the strongest candidate for resolved-provider data.
  • Verification status: Partially assessed — the call_logs claim was confirmed locally (2026-08-02): the table exists in the Docker volume and stores resolved model + provider per request. The /api/usage/request-logs HTTP endpoint itself is not reachable without a management token (403 AUTH_001).

Sources referenced but without a retrievable URL

  • The original Perplexity thread URLs for Research Rounds 01–04 were not preserved; the response source/export notes in each round record this. The ChatGPT conversation used to develop the Round 01 prompt is referenced by provenance note but not archived in this repository.