FAQ and limitations

Honesty is product behavior in Stella Loop — no silent fallbacks, no sample data presented as live, no claims ahead of reality. This page holds itself to the same bar.

Does Stella Loop replace my issue tracker?

Yes — that is the intent. Stella Loop is the system of record for product work. It does not replace the rest of your stack: spec tools, analyzers, model providers, coding agents, and version control remain pluggable. See the comparison for an honest look at where Linear-shaped trackers excel.

Can I import my existing backlog?

No, deliberately. Bulk import from Linear, Jira, or GitHub Issues is a non-goal: imported tickets would bypass the discovery half of the loop — the analysis and evidence that make commitments justified. Newly arriving GitHub issues flow in as signals from the moment you link a repository; your existing backlog stays where it is while you transition.

Do I have to hand control to agents?

No. Out of the box the loop is gated at exactly the points that matter — promotion (where money starts being spent) and merge (the irreversibility point) require a human’s approval, and spec approval and review sign-off give you an objection window. The autonomy dial is a dial: run fully supervised on day one, loosen per gate as trust grows.

Can agents do everything a human can?

Yes — that parity is enforced, not promised. One capability map generates the API, the CLI, and the MCP tools, and CI fails when any surface is missing a capability. Agents still work under your gates, roles, rate limits, and budgets. See Agents.

What does “quantify quality” actually mean?

Analyzers score the codebase 0–100 — overall, per area, per North Star document. Every score permanently records the analyzer version, rubric version, and model that produced it; deltas are only drawn against same-rubric predecessors; agentic scores that move a number must explain themselves, and sampled scores are audited by independent re-scoring. A score you cannot trust is decoration; these are built to be trusted. See Analysis.

What model providers and tools can I use?

Model routing is configured per stage through tiers (frontier / standard / economy) mapped to concrete models in project settings. Spec tools sit behind an adapter (OpenSpec ships as the default). Analyzers are pluggable — agentic or deterministic. Version control is git by default with Jujutsu supported per repository.

Current limitations

Stated plainly:

Desktop is macOS-only for now. Windows and Linux support exists in source and tests, but packaged, signed distribution is deferred — we do not claim availability we have not proven. Web and CLI cover every platform in the meantime.
Dark theme only. The token architecture supports a light theme, but none is designed yet; the switcher stays hidden until one is.
Desktop-class web only. The web app targets desktop-class viewports; there is no phone-width layout or mobile app.
No tracker import. See above — a stance, not a gap.
No third-party developer platform. API keys are first-party credentials for your organization’s people and agents; there is no OAuth app marketplace.
GitHub is the forge. Repository integration is built on a GitHub App; other forges are not yet supported. Version control is git or Jujutsu (colocated on git).

Where do I get help?

The getting started guide covers the first loop end to end. For anything else, contact us — including corrections to these docs.