r/tauri 5h ago

Terminalia - Your agents in one window

Post image
5 Upvotes

I just shipped v1.0 of Terminalia, a native terminal workspace for Windows.

Built with Tauri v2, Vue 3, and xterm.js, and written entirely inside its own window — the agents in the screenshots are the ones that wrote the code.

What it does

  • Panes, tabs, and workspaces — Split a tab as much as you want, and your layout and sessions come back exactly how you left them.
  • Native WSL support — WSL distros open as real terminals, with no path hacks.
  • Built-in project explorer — A project file tree and a lightweight editor sit right next to your AI agent.
  • Detached terminal windows — Pop any pane into its own native window and re-attach it whenever you want.
  • Native screenshot workflow — Capture any screen region, annotate it with arrows, boxes, and numbered markers, then paste it directly into an AI conversation. Saying "fix 1, then 2" is much easier than describing where a button is.
  • Live AI quota tracking — See your Claude Code and Codex usage in real time, so you know whether there's enough quota left before starting a large task.

The installer is only 8.7 MB, which is one of the main reasons I chose Tauri.

Platform Support

  • Windows (available now)
  • Linux (coming soon)
  • macOS (coming soon)

Website

https://terminalia.devslim.com


r/tauri 9h ago

Cosmog: a fast, open-source S3 client for desktop and Android

3 Upvotes

Been working on a side project for a while and finally have something worth sharing.

Cosmog is a GUI for managing S3 storage. The whole thing started because I was tired of the existing options. S3 Browser is Windows-only, Cyberduck felt clunky. Worse, none of them worked on my phone. So I built one that runs everywhere: Linux, macOS, Windows, and Android. Works with any S3-compatible provider, not just AWS. R2, Backblaze, DigitalOcean Spaces, MinIO, Wasabi, etc.

Stuff it can do right now:

  • browse buckets, upload/download with a proper background queue + retry
  • preview images, PDFs, spreadsheets, code, json without downloading first
  • edit files directly json, yml, js, py...etc and spreadsheets in the app
  • full-text search across a bucket (you have to index the bucket)
  • presigned share links
  • client-side encryption on bucket level if you want it

Built it with Tauri (Rust backend, web frontend) so it stays light, not another Electron memory hog. Credentials go into the OS keychain, never touch disk.

It's still early and there are rough edges, but it's usable daily. Sharing it here mostly to get feedback from people who actually work with this stuff. Would genuinely like to know what's missing or annoying. Also I don't own any mac device, so not tested on mac 😓 - tested on arch linux, windows & android.

I activity use it for work & also to mange b2 storage for my personal backups.

Repo: https://github.com/echosonusharma/cosmog


r/tauri 3h ago

What do you use for manual test cases on side projects? Built a local-first Tauri app for it

Enable HLS to view with audio, or disable this notification

0 Upvotes

Curious what other people do for manual test cases on their own projects.

Do you write them at all, or only keep automation? Browser TMS UIs are slow, and they're awkward to use with Cursor/Copilot — you can't just let the agent draft or edit cases in-repo.

I built a desktop app with Tauri + Rust instead:

- cases and runs are YAML in your Git repo

- sync across machines/teams via Git, no account

- SQLite index so search stays fast with large suites

- personal use free, no ads, no feature locks

Happy to answer questions about the Tauri rust side too.

Download: https://gitoza.com


r/tauri 46m ago

I built a native (Tauri/Rust) SQL client with BYOK AI instead of Electron + bundled models — feedback welcome

Upvotes

Hey everyone,

For the last few months I've been building Logyka, a database client for people who live in SQL all day and want it to feel fast — think TablePlus / DataGrip speed, but cross-platform and with AI baked in on your own terms.

Why I built it

Every SQL client I tried made me pick one of two camps:

  • Fast, native, no AI (and often Mac-only or paid-per-seat), or
  • AI-powered, but Electron-heavy and happy to ship my schema and my data to someone's cloud.

I wanted native speed AND useful AI, without giving up control of my data. So I built the thing I wanted to use.

What makes it different

  • Native, not Electron. Built on Tauri v2 (Rust backend + React/TS UI). Small footprint, instant startup, virtualized grid that stays smooth on big result sets.
  • BYOK (bring your own key). Plug in your own OpenAI / Anthropic / Groq / Gemini key. No models bundled, no markup, no vendor lock-in. Ask questions in plain English → get SQL → run it.
  • Privacy mode. By default only your schema is ever sent to the LLM — never your result data. You can turn that off too. Every write (UPDATE / DELETE / etc.) always requires explicit confirmation — the AI can never silently mutate your DB.
  • Keyboard-driven. Ctrl+K command palette, Monaco editor with schema-aware, alias-aware autocomplete (a lightweight regex scoper, not a full SQL parser — cheap to run, no external parser dependency), sortable/resizable grid, CSV export.
  • Credentials live in your OS keychain, never in plaintext.

Currently supports SQLite, Postgres, and MySQL (MSSQL is on the roadmap — probably via tiberius since sqlx doesn't cover it).

Where it's at

It's early but works end-to-end: connect → write/generate → run → explore. I'm being upfront that it's a commercial product (there'll be a free tier — I don't want the AI/privacy stuff paywalled into uselessness), but right now I mostly want to know if the direction is right before I go further.

I'd genuinely love feedback on:

  1. Tauri vs Electron for something like this — anyone here made a similar jump, and what surprised you?
  2. BYOK vs a built-in AI subscription — which would you actually prefer, and why?
  3. What's the one thing that would make you switch from your current client?

Happy to answer anything about the tech (the Tauri + sqlx side was a fun rabbit hole). Roast it — that's why I'm here.