Project
Where Subroutine stands, where the code lives, and how to follow or help.
Current state
This is an editorial overview, not live system health or an availability monitor.
| Area | Current state |
|---|---|
| Desktop app | Alpha, in active development. Timeline, Upcoming, Focus, routines and saved items are implemented. |
| Public downloads | Not released. Source is public; build information is on the Download page. |
| Website account | Hosted profile and security settings. Website sign-in is separate from permission to access task data through an API. |
| External API | No stable, supported third-party interface yet. See API. |
The Guide explains the current desktop concepts. Short demos are planned; there is no publication date to announce.
Follow development
The source repository is subroutine-app/subroutine-lite. The -lite in its
name is historical. It is not a separate edition, tier or fork; there is one
product, Subroutine. Its desktop UI depends on GPUI Box.
The blog covers design decisions as well as implemented behavior; future-facing ideas should not be read as available features. Subscribe through the Atom feed for new posts.
Feedback for development
GitHub issue forms ask for the details below: report a bug or describe a hard workflow. If you want to contribute code, read CONTRIBUTING.md first.
For a bug report, include:
- What you were trying to do and the steps that reproduce the problem.
- What you expected, and what actually happened.
- Your operating system and architecture, plus the build version or source commit if known.
Screenshots are optional. Redact private task content and account details first, and do not post email addresses, tokens, credentials or other secrets in public issues. A small example using invented task names is usually more useful than a copy of your workspace.
For a feature suggestion, describe the workflow and the point where it becomes difficult. That gives more context than a requested control or screen alone.