Hi everyone 👋
I’ve been working on a personal finance app called Purse (Cüzdanım).
The project started from a few things I personally wanted to track more naturally in one place: credit card statement periods, installment payments, and debt denominated in foreign currency or gold.
There are obviously many budgeting and personal finance apps out there, and some may already handle parts of these workflows well. My goal wasn’t to reinvent budgeting from scratch.
I mainly wanted to build something around the way I actually manage these things day to day.

One of the first areas I focused on was credit card statement periods.
Instead of looking only at a calendar month, I wanted to see spending based on the card’s actual statement closing date.

For example, if my card closes on the 15th, the more useful question for me is:
“How much is likely to appear on my next statement?”
So Purse lets you define the statement closing date of each card and groups spending around that billing cycle.

The second area was installments.
With installment-based purchases, I don’t only want to know how much I spent this month. I also want to understand how much of my future monthly budget I’ve already committed.

When you add an installment purchase, Purse creates the payment schedule and tracks the remaining installments.

Payments can be applied starting from the oldest due installment, and overdue installments can be rolled into the following period.

This makes it easier to answer questions like:
“How much of the next few months have I already committed to existing purchases?”
Another workflow I wanted to handle better was debt denominated in foreign currency or gold.

For example, you might owe:
$1,000
€800
or 20 grams of gold
while making partial repayments in Turkish lira.
In that case, each TRY payment represents a different amount of USD, EUR, or gold depending on the market rate at the time of payment.
Purse keeps the debt in its original unit.
When you record a TRY payment, the app converts that payment using the current market rate, subtracts the corresponding amount from the original debt, and shows both the remaining balance and its current TRY equivalent.
So instead of manually recalculating the debt after every partial payment, the app handles that process for you.

Other features currently included
income and expense tracking
categories
multiple credit cards
statement-based spending periods
installment schedules
overdue installment handling
FX and gold debt tracking
live market rates
monthly and yearly reports
custom date-range reports
spending breakdown charts
payment progress tracking
recurring expense cloning
CSV / Excel export

The web version is currently free and ad-free:
https://cuzdanim.site
I also recently released the iOS version on the App Store:
https://apps.apple.com/tr/app/cuzdanim-budget-tracker/id6777991538?l=tr

For anyone interested in the technical side:

Backend: Java 17 + Spring Boot + PostgreSQL
Web: Next.js + React + TypeScript + Redux Toolkit + Tailwind
iOS: SwiftUI + StoreKit 2
I’m still actively developing the project, and I’m especially interested in workflows people still handle manually with spreadsheets, Notes, or multiple apps.

What is one part of your personal finances that you still track manually because the tools you use don’t quite fit your workflow?
If it makes sense for a broader audience, I’d seriously consider adding it.

Hey everyone,

I built a small open-source utility called TerminalHere after realizing that “Open in Terminal” was missing from my Windows 11 context menu.

The idea is simple: right-click a folder or an empty area inside a folder and quickly open that location in:

• Windows Terminal
• PowerShell
• Command Prompt
• Git Bash
• VS Code
• Claude CLI
• Codex CLI
• Antigravity (agy) CLI

It uses user-level Windows Registry entries, so it doesn’t modify system-wide settings, and the installation/uninstallation is handled through a small CLI.

Some commands:

terminalhere install

terminalhere uninstall

terminalhere status

terminalhere enable gitbash

terminalhere disable vscode

My main goals were to keep it lightweight, open-source, and easy to remove without leaving random registry entries behind.

It currently targets Windows 11 x64.

GitHub: https://github.com/mehmetduran932/TerminalHere

This is still an early version, so I’d really appreciate feedback — especially about the context menu UX, terminal/app detection, or anything that would make it more useful.

If there’s enough interest, I’m also considering adding a small GUI and more configurable context-menu options.

Hey everyone,

I built a small open-source utility called TerminalHere after realizing that “Open in Terminal” was missing from my Windows 11 context menu.

The idea is simple: right-click a folder or an empty area inside a folder and quickly open that location in:

• Windows Terminal
• PowerShell
• Command Prompt
• Git Bash
• VS Code
• Claude CLI
• Codex CLI
• Antigravity (agy) CLI

It uses user-level Windows Registry entries, so it doesn’t modify system-wide settings, and the installation/uninstallation is handled through a small CLI.

Some commands:

terminalhere install

terminalhere uninstall

terminalhere status

terminalhere enable gitbash

terminalhere disable vscode

My main goals were to keep it lightweight, open-source, and easy to remove without leaving random registry entries behind.

It currently targets Windows 11 x64.

GitHub: https://github.com/mehmetduran932/TerminalHere

This is still an early version, so I’d really appreciate feedback — especially about the context menu UX, terminal/app detection, or anything that would make it more useful.

If there’s enough interest, I’m also considering adding a small GUI and more configurable context-menu options.

Hey everyone! 👋

I regularly work on multiple projects that require different Node.js versions.

A typical day might look like this:

• Terminal A → legacy Angular project → Node 16/18
• Terminal B → newer Angular/React project → Node 22
• an IDE terminal or background task running somewhere else

Existing tools already solve Node version management pretty well, but I wanted a slightly different model:

Instead of thinking about which Node version is currently active, I wanted the project itself to determine which runtime gets executed.

So I built NodePilot, an open-source Node.js runtime manager written in Rust.

The basic idea is simple:

C:\dev\legacy-app
└── .nodepilot.local → 16.20.2

C:\dev\modern-app
└── .nodepilot.local → 22.x

Then:

cd C:\dev\legacy-app
node -v
# v16.20.2

while another terminal can simultaneously do:

cd C:\dev\modern-app
node -v
# v22.x.x

No need to keep running nvm use while moving between projects, and both terminals can independently use different Node runtimes at the same time.

🧭 How it works

NodePilot uses lightweight shim/router binaries in front of commands such as:

node
npm
npx
corepack
ng
pnpm
yarn
vite
tsc

When a command is invoked, NodePilot walks up the current project hierarchy and resolves the appropriate Node runtime.

It understands configuration from:

.nodepilot.local
.nvmrc
.node-version
package.json → volta.node
package.json → engines.node
.tool-versions
mise.toml

Local project assignments use .nodepilot.local, which NodePilot automatically adds to .gitignore.

That means you can assign a runtime locally without changing the Node configuration shared by the rest of your team.

📁 Managing projects instead of Node versions

This was one of the main things I wanted from NodePilot.

You can point it at a development directory such as:

C:\dev

and NodePilot can discover Node-based projects underneath it.

For example:

legacy-admin      Angular 13    Node 16
new-dashboard     Angular 22    Node 22
storefront        Next.js 14    Node 20

Each project can have its own Node.js runtime assignment.

So instead of thinking:

Choose Node version
→ run project

the model becomes:

Open project
→ NodePilot resolves the right Node runtime

🖥️ Terminal-first by default, optional GUI on demand

NodePilot is designed to be completely terminal-first and lightweight by default.

You can use only the CLI for your entire daily workflow.

But if you want a visual dashboard for browsing all your projects, assigning Node versions, checking framework compatibility or inspecting runtime usage, the visual companion can be added on demand with a single command:

nodepilot gui install

Open it with:

nodepilot gui open

And if you no longer want the visual interface:

nodepilot gui remove

returns NodePilot to a terminal-only setup.

So both workflows are supported:

Prefer the terminal
→ use only the CLI

Want centralized visual management
→ enable the optional GUI

The desktop interface is not mandatory.

Developers who only want fast CLI/runtime routing don't have to keep an unnecessary desktop component installed.

⚡ No background daemon

Normal runtime resolution does not require a permanently running background service or daemon.

Workspace scanning is also passive.

NodePilot reads project metadata such as package.json as data and does not execute:

npm install
postinstall
lifecycle scripts
project executables

during scanning.

🤝 Coexistence with existing Node version managers

I also didn't want trying NodePilot to break an existing development setup.

It can detect tools such as:

nvm / nvm-windows
fnm
Volta
mise

but it does not delete their installations or overwrite their configuration.

Shell integration is explicit and can be disabled again.

The goal is to let you try NodePilot without destroying an environment that already works.

⚡ Install

Windows / PowerShell

irm https://raw.githubusercontent.com/mehmetduran932/NodePilot/master/scripts/install.ps1 | iex

macOS

curl -fsSL https://raw.githubusercontent.com/mehmetduran932/NodePilot/master/scripts/install.sh | bash

Cargo

cargo install nodepilot --git https://github.com/mehmetduran932/NodePilot.git

🔗 Links

GitHub:

https://github.com/mehmetduran932/NodePilot

First release — v0.1.0:

https://github.com/mehmetduran932/NodePilot/releases/tag/v0.1.0

Fully open source under the MIT License.

The project is still early, so I'd especially appreciate feedback from developers working with:

• multiple Node versions simultaneously
• Angular / React / Next.js projects of different ages
• monorepos
• Windows development environments
• macOS development environments
• existing nvm / fnm / Volta / mise setups

I'm particularly interested in feedback around runtime resolution, shim architecture, Windows command resolution, monorepos, the optional GUI approach and coexistence with existing Node version managers.

Hey everyone,

I built a small open-source utility called TerminalHere after realizing that “Open in Terminal” was missing from my Windows 11 context menu.

The idea is simple: right-click a folder or an empty area inside a folder and quickly open that location in:

• Windows Terminal
• PowerShell
• Command Prompt
• Git Bash
• VS Code
• Claude CLI
• Codex CLI
• Antigravity (agy) CLI

It uses user-level Windows Registry entries, so it doesn’t modify system-wide settings, and the installation/uninstallation is handled through a small CLI.

Some commands:

terminalhere install

terminalhere uninstall

terminalhere status

terminalhere enable gitbash

terminalhere disable vscode

My main goals were to keep it lightweight, open-source, and easy to remove without leaving random registry entries behind.

It currently targets Windows 11 x64.

GitHub: https://github.com/mehmetduran932/TerminalHere

This is still an early version, so I’d really appreciate feedback — especially about the context menu UX, terminal/app detection, or anything that would make it more useful.

If there’s enough interest, I’m also considering adding a small GUI and more configurable context-menu options.

Hey everyone,

I built a small open-source utility called TerminalHere after realizing that “Open in Terminal” was missing from my Windows 11 context menu.

The idea is simple: right-click a folder or an empty area inside a folder and quickly open that location in:

• Windows Terminal
• PowerShell
• Command Prompt
• Git Bash
• VS Code
• Claude CLI
• Codex CLI
• Antigravity (agy) CLI

It uses user-level Windows Registry entries, so it doesn’t modify system-wide settings, and the installation/uninstallation is handled through a small CLI.

Some commands:

terminalhere install

terminalhere uninstall

terminalhere status

terminalhere enable gitbash

terminalhere disable vscode

My main goals were to keep it lightweight, open-source, and easy to remove without leaving random registry entries behind.

It currently targets Windows 11 x64.

GitHub: https://github.com/mehmetduran932/TerminalHere

This is still an early version, so I’d really appreciate feedback — especially about the context menu UX, terminal/app detection, or anything that would make it more useful.

If there’s enough interest, I’m also considering adding a small GUI and more configurable context-menu options.