Feature Requests

Dark mode
Imported from GitHub feature requests. Source issues: - #200 Support Dark Mode Theme for Accessibility and Usability — https://github.com/refactoringhq/tolaria/issues/200 - #213 Is there no dark mode? — https://github.com/refactoringhq/tolaria/issues/213 - #249 Black Theme + Opencode — https://github.com/refactoringhq/tolaria/issues/249 Original context from GitHub: ### Feature Request: Dark Mode Support Tolaria currently supports only a light theme, as per ADR-0013 . As a user, I would appreciate a dark mode option for the following reasons: Accessibility: Dark mode can reduce eye strain, especially for users working in low-light environments. User Preference: Many users prefer dark UI themes for productivity and comfort. Consistency: Other productivity apps often provide both light and dark mode options. Request: Consider implementing a dark mode or providing a theme toggle between light and dark modes. If full theming is too costly, even just a hardcoded dark mode alternative would be valuable. #### References: ADR-0013 – Removal of theming system and light-only decision Thank you for considering this feature! Additional mentions: - #213: A pure white background is very difficult to use at night. - #249: Please add true dark theme - Comment on #200 by @niteshmanav: +1 for Dark Mode. Also, not sure why it couldn't detect Claude Code CLI or Desktop App installed on my mac. It could only detect Codex App. Is it because we are unofficial OpenAI compatible endpoint, but not the Claude susbcription?
2
·
complete
Open vaults without forcing Git
Imported from GitHub feature request. Source issue: #225 [Feature Request] Allow opening existing vaults without forcing Git repo creation — https://github.com/refactoringhq/tolaria/issues/225 Original context from GitHub: Right now Tolaria requires creating a new Git repository when opening an existing vault or otherwise refuses to open it. This prevents users from adopting Tolaria with existing notes they created with other tools like Obsidian, and feels like an opinionated constraint that blocks common workflows. Consider allowing users to open an existing vault directory that does not contain a Git repository. Git integration should be optional in that case. Tolaria can detect whether a vault is already a Git repo and enable Git features, but if not, it should still open the vault normally and offer an explicit, user-initiated option to initialize Git later (or import/pair an existing repo). The default behavior when opening a non-Git vault should be non-intrusive and clearly communicate that Git features are disabled until the user enables them. This lowers friction for users migrating from other tools or using plain Markdown folders, while preserving existing workflows and files without forcing version control decisions. It would keep the Git integration available for users who want it, while making it an opt-in enhancement rather than a hard requirement. Additional mention: Comment by @IntoTheBlueAt: +1 for this one, many users (e.g. coming from Obsidian) might not use git at all, maybe it should be optional for new vaults as well?
4
·
complete
Load More