Show HN: Stoke Money – Personal finance app built around a cash flow forecast https://ift.tt/F6KCl1Y

Show HN: Stoke Money – Personal finance app built around a cash flow forecast Hi HN, I've been through many finance tracking apps, starting with Personal Capital, then Monarch, and most recently Copilot. None of them have worked perfectly for my needs. All of these apps tend to model “cash flow” as the net sum of your transactions during a month, yet while credit card charges are reported immediately, they are typically deducted from checking (cash) accounts the following month when the bill is due. As a result, I've always had to maintain a separate spreadsheet to track my actual cash flow. These apps also have a huge focus on managing budgets, which has never been for me. My spending is rarely consistent month-to-month, so every month I'm comparing my fully justified spending against my budget, and tweaking my budget until I “pass”. So I built yet another finance tracking app. It has the usual components - accounts, transactions, categories - but the core is a cash flow projection engine, and everything else is built around it. Budgets are gone. Instead, each income/spending category is projected forward from your historical activity, but not as a flat monthly number. They land in whatever account you historically use (e.g. checking account for paychecks/rent/bills, credit/debit cards for daily spending). Credit card payments are modeled automatically based on your projected credit card balance. You can set up your own recurring transfers between accounts as well, to model savings, for example. The end result is that the app can forecast how your cash moves, and you can see in advance when any account might run low. If all of your accounts look good for the next 12 months, maybe you don't have a budgeting problem. What’s made the biggest difference for me has been the MCP integration, which I have connected to Claude (but can be connected to any AI agent of your choice). I have asked it to import historical transactions by uploading PDF account statements, categorize/tag all transactions that took place while I was on vacation, and plan transfers across my accounts to cover expected payments. I hope some people that share my frustrations will find this app useful. https://stoke.money October 17, 2026 at 12:24AM

Show HN: 2026 Midterms Tracker blends polls and Kalshi/Poymarket odds https://ift.tt/VBFpRGq

Show HN: 2026 Midterms Tracker blends polls and Kalshi/Poymarket odds https://ift.tt/o5sbQZy October 16, 2026 at 11:49PM

Show HN: Endo – A Higher-Order Harness https://ift.tt/A5XWZoN

Show HN: Endo – A Higher-Order Harness Endo is a Higher-Order Harness (HOH). From the easiest concept to understand to the more complex ones, Endo gives you: * A single, simple UI to use any agent provider with your existing subscriptions, and hot-swap agents right in the middle of a session. * An orchestration layer, which I call HOH, allowing arbitrary composition of agents to achieve any workflow. A fun case I tried was asking Fable and Astra to mock a presidential debate. * An agent protocol that abstracts any agent. The key insight here is that every LLM is an agent—instead of treating the LLM as just one node inside an external ReAct loop. Endo was a concept formed while I was building OpenChart ( https://ift.tt/PalBSW8 ). To power trading workflows, I needed to support scenarios where strict determinism is required, while still keeping the flexibility of an agent's inference-time decision-making capability. A new form factor was needed between rigid n8n-style workflows and open-ended ReAct loop agents. Thus the creation of Endo. Endo is short for Endomorphism, a term rooted in category theory and functional programming. An endomorphism is a function that transforms an object into another object of the same type. Similarly, Endo itself is built purely on functional programming principles, relying heavily on Effect ( https://ift.tt/sGZtuPA ). ..And if you have patience to speak technical jargons, Endo is: * An agent orchestration layer—Higher-Order Harness (HOH)—where an entire agent is treated the same as a single LLM call, enabling arbitrary composition of extremely complex workflows. * A way to abstract any harness into a standardized protocol, where raw models and agents behave the exact same way, in a KV-cache-friendly manner. * A workflow engine that enables arbitrary composition of agents with a single workflow language. It's completely open source, and if you think this idea is cool, let's build together. Just for the fun of it. https://ift.tt/tWGORIP October 16, 2026 at 03:02AM

Show HN: Forwarder.cc – Static-site forms sent to your inbox, pay per message https://ift.tt/LKd1fzT

Show HN: Forwarder.cc – Static-site forms sent to your inbox, pay per message TL;DR: 12 years ago I built a service that forwards simple HTML forms to an email address. I've been procrastinating on finishing it ever since, until today. You point your form at it and every submission lands in your inbox. It runs on credits, 1 credit = 1 message, no subscription. Perfect for static websites. — Hey folks, back around 2014, alongside my job as a software engineer, I was building a lot of static websites for my own clients, mostly small businesses that just wanted a simple site. To avoid headaches, I went fully static, often hosted on GitHub Pages and similar. But most clients also wanted a contact form, and a form needs a server running somewhere. I had my own weekend-hacked service for this, which literally just forwarded the form to the client's email. I didn't invent anything here: one service I particularly remember was FormKeep by thoughtbot, that I really liked. So I started building my own, mostly because I loved losing myself in side projects like this, and also because I was a cheap ass and thought I could do something similar for less, and without a subscription. By 2016 I had done about 90% of what I'm showing you today. I called it "The Great Forwarder". Everything was ready: backend, frontend, hosting, Stripe, landing page. I even had a designer friend help with the design (sorry, Valentin, if I've botched it since). Then I started another project, which took off right away and took all my attention for a while. Fun fact: that project has been using this service ever since, and almost every message ever sent through it came from there. So for years, I kept Forwarder.cc up to date, upgrading libraries and trying new ones: axios, got, Redux, Zustand, create-react-app, webpack, Vite… It became my laboratory for everything I wanted to explore, while always staying up and maintained (again, for my own use only). The only thing that ever held me back from launching it was a missing help center, and, more honestly, the fear of putting it in front of people. So today's the day: after 12 years of procrastination, I finally finished the help center. I know there are a ton of similar services nowadays, but anyway, what do you think of that help center? https://forwarder.cc October 16, 2026 at 12:17AM

Show HN: RDST – A local agent that watches Postgres/MySQL for query regressions https://ift.tt/JgoQ2wL

Show HN: RDST – A local agent that watches Postgres/MySQL for query regressions We noticed during the course of many many years of DBA related work that fixes to database issues and queries are always reactive. An entire database can fall over extremely quickly when an unbounded query grows without warning. Traditionally, DBAs hear complaints of slowness and follow a methodical process: - manually browse pg_stats or other database related performance internal tables - see which queries are slowest - figure out what indexes are missing - figure out which indexes are actually bad and slowing down writes - painstakingly implement a fix In the age of cheap intelligence, we decided that there is no reason we can’t have an always-on agent that is designed to do this job for you. Databases need something or someone that is always watching with a massive amount of contextual understanding to be able to take quick actions. We’ve watched the alternative play out repeatedly. One of our users’s checkout page went from loading instantly to taking 11 seconds in a single night with no code change. How? Well somehow their order table grew by 40M rows because BI team had injected historical data and suddenly postgres started doing full table scans. Sometimes routine operations have unintended results and can easily destroy your database. We wanted to catch these kinds of regressions instantly. So we built RDST. RDST is a desktop agent that runs on your PC and connects to PostgreSQL / MYSQL (read only) and compares every query against its own performance every minute. Every expensive query is automatically EXPLAIN ANALYZED, stripped of PII and sent to U.S. based frontier or open model providers to analyze which indexes are missing, how the query could be rewritten, and provides the fix. We then run a classifier model (JEV) to decide if you should be notified (is this standard behavior for this particular query?), and the full history of the query performance is kept for years. RDST also keeps track of your entire database health in general, and recommends more fixes than simply bad queries. Since it runs locally we can keep the database credentials stored in your OS Keychain (RDST never keeps them in its own storage layer), and the connection goes straight to your database (using a jump host or SSH tunnel for private connections). You can read more about how we handle data especially as it pertains to LLM use here. https://ift.tt/kCFrxKR We really want feedback from the community from people running Postgres and MySQL in production. We are giving inference away completely for free. Just as a reminder, RDST will NOT run any updates or indexes against your database at this time. We are considering a fully autonomous auto-pilot mode in the future, but for now we are leaving the actual fixes in your hands. Let us know what you think! https://ift.tt/dKXJQW7 October 15, 2026 at 11:39PM

Show HN: I think Apple should have built this a long time ago https://ift.tt/4DwL0oK

Show HN: I think Apple should have built this a long time ago Built this little tool a while ago and shared it with a few friends. The feedback I got was great that I decided to release it publicly. It's not just another 'clipboard'... Honestly, would love you guys to try it out! This is my first public release of a product with a price tag! I have 0 expectations for it... but I genuinely love using it myself. https://ift.tt/lfEUR8L October 15, 2026 at 05:48AM

Show HN: Ask a technical question, get an animated explainer you can interrupt https://ift.tt/go7x9W0

Show HN: Ask a technical question, get an animated explainer you can interrupt https://ift.tt/zlX69wn October 15, 2026 at 04:10AM