Real problems people complain about online, pulled every morning and scored out of 100. Build, validate, or skip. How scoring works
I wrote this after the case of a Washington Post reporter, Hannah Natanson, was compelled to unlock her computer with her fingerprint. This resulted in access to her Desktop Signal on her computer, revealing sources and their conversations.https://www.yahoo.com/news/articles/washington-post-raid-pro...Edit: I've a lot more details about the legality and precedence on the apps landing page https://paniclock.github.io/
Hacker News5mo agoToolAI
https://www.phoronix.com/news/AMD-Ryzen-AI-Open-Source-Demo AMD Has Open-Source Ryzen AI Demo Code - But Only For Windows
GitHub3y agoToolAI
Two weeks ago, I quit my job at a robotics company. I was working with high-end hardware (Boston Dynamics, Unitree), but I found out they were planning to mount teleoperated weapons on the robotic platforms for a demo. I’m not willing to go there, so I resigned without another offer.I’ve decided this is the right time to go back to entrepreneurship. We're at an incredible moment for embodied intelligence, but I feel the tools and workflows we use to interact, monitor, and control these platforms are still lagging behind.I'm currently exploring a couple of projects around how we build, test, and interact with robots. As part of my customer discovery phase, I'm trying to gather raw data on how roboticists and developers actually work day to day and what their main pain points are regarding control interfaces.I put together a very short survey (3 mins) to validate some ideas. If you work in robotics, embedded systems, or just tinker with hardware, your input would be incredibly valuable:Survey link: https://forms.gle/3Nm76wkeT5CMt23c8I'm also open to discussing the ethical lines in modern robotics or anything related to ROS2 / HRI in the thread. Thanks for reading!
Hacker News5mo agoToolAI
Users want an AI chat app equivalent to Chai for roleplay/conversations but excluding Character.ai's limitations or censorship.
X5mo agoToolAI
AI agents like Claude Cowork incur high token costs, hit subscription limits, and run slowly for repetitive tasks, leading users to complete them manually instead.
X5mo agoToolAI
Curated comparison platform for free/open-source AI chat tools with features, limits, speed tests, and use-case recommendations to help users find best fit. [Google Search suggestion]
Google Trends5mo agoToolAIUS
I have a proposal that addresses long-term memory problems for LLMs when new data arrives continuously (cheaply!). The program involves no code, but two Markdown files.For retrieval, there is a semantic filesystem that makes it easy for LLMs to search using shell commands.It is currently a scrappy v1, but it works better than anything I have tried.Curious for any feedback!
Hacker News5mo agoToolAI
Hey HN,In this age of agentic coding I've found myself spending a lot of time reviewing markdown files. Whether it's plans or documentation that I've asked my agent to generate for me, it seems that I spend more time reading markdown than code.I've tried a few different solutions to make it easier to read such as Obsidian however I've found their Vault system to be quite limiting for this use case and I've found TUI solutions to not quite be as friendly to read as I've wanted so I made Marky.Marky is a lightweight desktop application that makes it incredibly easy to read and track your markdown files. It also has a helpful cli so you can just run marky FILENAME and have the app open to the md file that you pointed it at. I've been using the daily over the past week and I really enjoy it so I figured I'd share it.Here's a video if you want to check out a demo: https://www.youtube.com/watch?v=nGBxt8uOVjc.I have plans to add more features such as incorporating agentic tools such as claude code and codex into the UI as well as developing a local git diff reviewer to allow me to do local code review before pushing up to git.I'd love to hear your thoughts and any feature suggestions you may have :)
Hacker News5mo agoToolAI
Developers are seeking a robust Named Entity Recognition (NER) model that outperforms spaCy, runs locally, and provides accurate span boundaries for entity extraction.
X5mo agoToolAI
Non-technical teams struggle to automate repetitive processes (data entry, email routing, report generation). An AI-assisted tool that watches user actions and suggests automations could reduce manual work by 30%+. [Google Search suggestion]
Google Trends5mo agoToolAIUS
It's been a year now since I made Claude Code my daily driver, but I feel exhausted by all the context switching from managing 2-3 agents at a time. I know some people advocate for letting agents run wild, but in my experience that leads to subtle bugs that compound and reviews become 100x more painful.What have you done to retain some semblance of flow, stay organized, and limit spinner staring?
Hacker News5mo agoToolAI
Hi HN!I’ve always found it hard to explore the Mahābhārata and Rāmāyaṇa online. Most content is either long-form or scattered, and understanding a character like Karna or Bhishma usually means opening multiple tabs.I built https://www.ithihasas.in/ to solve that. It is a simple character explorer that lets you navigate the epics through people and their relationships instead of reading everything linearly.This was also an experiment with Claude CLI. I was able to put together the first version in a couple of hours. It helped a lot with generating structured content and speeding up development, but UX and data consistency still needed manual work.Would love feedback on the UX and whether this way of exploring mythology works for you.
Hacker News5mo agoToolAI
Heavy AI users suffer constant distraction and inability to focus deeply due to managing multiple Claude sessions, numerous terminal/browser tabs, and rapid AI news cycles causing excessive task-switching.
X5mo agoToolAI
Users want a notes app where they input thoughts or ideas, and AI automatically starts developing or implementing them in the background without manual setup.
X8mo agoToolAI
Built this after realizing I was spending ~$1400/week on Claude Code with almost no visibility into what was actually consuming tokens.Tools like ccusage give a cost breakdown per model and per day, but I wanted to understand usage at the task level.CodeBurn reads the JSONL session transcripts that Claude Code stores locally (~/.claude/projects/) and classifies each turn into 13 categories based on tool usage patterns (no LLM calls involved).One surprising result: about 56% of my spend was on conversation turns with no tool usage. Actual coding (edits/writes) was only ~21%.The interface is an interactive terminal UI built with Ink (React for terminals), with gradient bar charts, responsive panels, and keyboard navigation. There’s also a SwiftBar menu bar integration for macOS.Happy to hear feedback or ideas.
Hacker News5mo agoToolAI
Hi HN, I’d like to introduce you to SmallDocs (https://sdocs.dev). SDocs is a CLI + webapp to instantly and 100% privately elegantly preview and share markdown files. (Code: https://github.com/espressoplease/SDocs)The more we work with command line based agents the more `.md` files are part of our daily lives. Their output is great for agents to produce, but a little bit frustrating for humans: Markdown files are slightly annoying to read/preview and fiddly to share/receive. SDocs was built to resolve these pain points.If you `sdoc path/to/file.md` (after `npm i -g sdocs-dev`) it instantly opens in the browser for you to preview (with our hopefully-nice-to-look-at default styling) and you can immediately share the url.The `.md` files our agents produce contain some of the most sensitive information we have (about codebases, unresolved bugs, production logs, etc.). For this reason 100% privacy is an essential component of SDocs.To achieve this SDoc urls contain your markdown document's content in compressed base64 in the url fragment (the bit after the `#`):https://sdocs.dev/#md=GzcFAMT...(this is the contents of your document)...The cool thing about the url fragment is that it is never sent to the server (see https://developer.mozilla.org/en-US/docs/Web/URI/Reference/F...: "The fragment is not sent to the server when the URI is requested; it is processed by the client").The sdocs.dev webapp is purely a client side decoding and rendering engine for the content stored in the url fragment. This means the contents of your document stays with you and those you choose to share it with, the SDocs server doesn't access it. (Feel free to inspect/get your agent to inspect our code to confirm this!)Because `.md` files might play a big role in the future of work, SDocs wants to push the boundaries of styling and rendering interesting content in markd
Hacker News5mo agoToolAI
Hacker News5mo agoToolAI
Hey! I am Alex and together with my co-founder Tarun built Kampala (https://www.zatanna.ai/kampala). It’s a man-in-the-middle (MITM) style proxy that allows you to agentically reverse engineer existing workflows without brittle browser automation or computer use agents. It works for websites, mobile apps, desktop apps.Demo: https://www.youtube.com/watch?v=z_PeostC-b4. Many people spend hours per day in legacy dashboards and on-prem solutions reconciling data across platforms. Current attempts at automation use browser automations or computer use agents which are brittle, slow, and nondeterministic. I come from a web reverse engineering background and spent the last 7-8 years building integrations by hand for sneaker/ticket releases, sportsbooks logins, and everything in\ between. During that time I consulted for several companies and brought them off of browser based infrastructure into the requests layer.When we started Zatanna (that’s our company name) we worked in dental tech, which meant we had to deal with tons of insurance payer dashboards and legacy dental-practice solutions. Our superpower (as a fairly undifferentiated voice agent/front desk assistant company) was that we could integrate with nearly any system requested. During this time we built extensive tooling (including what we’re now calling Kampala) to allow us to spin up these integrations quickly. Existing MITM proxies and tooling didn’t work for a few reasons: (1) They manipulated the TLS and HTTP2 fingerprint over the wire which was detected by strict anti-bots. (2) They had bad MCPs which did not adequately expose necessary features like scripts/replay. (3) They did not allow for building workflows or actions given a sample or sequence of requests.As the tools we built got more powerful, we began to use them internally to scrape conference attendees, connect to external PMS systems, and interact with slack apps. I even sent it to my property manager
Hacker News5mo agoToolAI
Some technical context on what we ran into building this.MCP tools don't really work for financial data at scale. One tool call for five years of daily prices dumps tens of thousands of tokens into the context window. And data vendors pack dozens of tools into a single MCP server, schemas alone can eat 50k+ tokens before the agent does anything useful. So we auto-generate typed Python modules from the MCP schemas at workspace init and upload them into the sandbox. The agent just imports them like a normal library. Only a one-line summary per server stays in the prompt. We have around 80 tools across our servers and the prompt cost is the same whether a server has 3 tools or 30. This part isn't finance-specific, it works with any MCP server.The other big thing was making research actually persist across sessions. Most agents treat a single deliverable (a PDF, a spreadsheet) as the end goal. In investing that's day one. You update the model when earnings drop, re-run comps when a competitor reports, keep layering new analysis on old. But try doing that across agent sessions, files don't carry over, you re-paste context every time. So we built everything around workspaces. Each one maps to a persistent sandbox, one per research goal. The agent maintains its own memory file with findings and a file index that gets re-read before every LLM call. Come back a week later, start a new thread, it picks up where it left off.We also wanted the agent to have real domain context the way Claude Code has codebase context. Portfolio, watchlist, risk tolerance, financial data sources, all injected into every call. Existing AI investing platforms have some of that but nothing close to what a proper agent harness can do. We wanted both and couldn't find it, so we built it and open-sourced the whole thing.
Hacker News5mo agoToolAI
I have been running a SaaS for ~10 years used heavily by people 65+ and a lot of them are tired and frustrated about remembering the domain/path to login screen and then which email/password they used, having to go through the whole forgot-password-flow, etc. I have tried simplifying this as much as i can but I feel like there must be better options. Google sigin in is confusing for them because they get thrown into Googles horrible UX flow where they might have multiple accounts and they don't like when the website suddenly changes.In general, what is the best way to simplify the auth UX for this group of users? Is there any UI libraries out there targeting this group more specifically? Any good web examples you know of?thx
Hacker News5mo agoToolAI