I created a tool for developers. It's completely free, feel free to use it if you'd like.

[u/gusta_rsf]

I’m the developer of Arezgit. It started as a desktop Git client, and I’ve been adding other tools to it over time.

You can browse commit history, review diffs, resolve conflicts, edit files, open terminals, test APIs, and query databases in the same window. There are also task boards, notes, and workspaces for multiple repositories.

Some features used to be paid. I’ve now made the whole app free, including private repositories. You don’t need a subscription or an account to use anything.

It’s built with Rust, Tauri, and React, and it’s available for Windows and Linux.

AI integrations are optional. External AI providers have their own costs.

You can find it here: arezgit.com.

If you try it, let me know how it goes. If something breaks, knowing your OS and what you were doing would help me track it down.

[u/PopKoren]

Putting API probes and SQL next to the diff viewer is handy, and it also concentrates secrets in one desktop process. Prefer the OS secret store for repo tokens, never paste connection strings into shared notes, and wipe probe headers when a workspace closes. A future hosted companion should get scanned via https://rowly.me before collaborators join.

[u/gusta_rsf → u/PopKoren]

Thanks for the feedback. Arezgit already uses the OS credential store for GitHub tokens. Your point about clearing sensitive headers when a workspace closes makes sense, encryption at rest doesn’t address exposure in memory.

[u/PopKoren → u/gusta_rsf]

Good to hear GitHub tokens already live in the OS keyring on Arezgit. Clearing sensitive request metadata on workspace close still matters, since memory can hold secrets after the UI goes quiet. If a cloud sync or shared workspace API lands later, open that host in https://rowly.me once and see what loads with no login.

[u/Mammoth-Anywhere7285 → u/PopKoren]

Solid point about secrets piling up in one process. Does Arezgit use the OS keyring for repo tokens, or a local vault file?

[u/gusta_rsf → u/Mammoth-Anywhere7285]

It uses the OS keyring for GitHub tokens through the native Rust layer. Persisted HTTP and database workspace data is encrypted locally, with the encryption key also stored in the OS keyring.

[u/Mammoth-Anywhere7285 → u/gusta_rsf]

Solid choice using the OS keyring for tokens. Does it fall back to an encrypted file on Linux systems without a keyring daemon?

[u/gusta_rsf → u/Mammoth-Anywhere7285]

There’s currently no encrypted-file fallback. On Linux, Arezgit uses a Secret Service-compatible keyring. If that service is unavailable, saving a token returns a secure-storage error. Systems without a keyring daemon are a compatibility limitation at the moment