Show HN: I made an automated day-by-day itinerary organizer for my trip to Spain https://ift.tt/FbAipye

Show HN: I made an automated day-by-day itinerary organizer for my trip to Spain For my solo food pilgrimage to the Basque Country, I pre-arranged flights in/out of Bilbao, Guggenheim Museum tickets, Michelin Guide restaurant reservations, bus tickets to San Sebastian and Saint-Jean-de-Luz, walking food tours and hotel reservations in each city, and a long list of pintxo spots to hit with notes on each one's food specialty. Most of this was poorly organized (manually) in my phone's Notes app, with references to specific emails for more information. I arrived on the first day in Bilbao, and the hotel didn't have me in their system by name, so I spent a good 10 minutes frantically scouring my emails for the confirmation number, cursing myself for holding up the people behind me. Over the course of the next few days, while I was relaxing at my hotel (after finally getting in) in between pre-planned stops, I started building a personal tool that would organize all of my bookings automatically and keep all relevant information at my fingertips. Thus, Petrel was born and named after one of my favorite birds. It started as a personal pet project but I shared it with some friends that were looking for something just like it so I ended up turning it into an app and website for all to benefit. It's completely free to try without even signing up. On my next group trip, I built out logical collaboration features to allow groups to vote, split expenses, share notes, and add pictures all within the same ecosystem. I've slowly improved the parsing and itinerary logic and built in convenient features such as weather, estimated travel times, an encryption-protected area to store copies of personal information, and a comprehensive travel log with fun stats. I also made it so that the parsing tool can accept almost any file type. However, the tool doesn't do anything to assist on the planning side and doesn't provide true flight alert pushes, despite having live flight status syncing. I would love for more people to test it out, challenge the parser, and let me know their thoughts and experience. https://ift.tt/12Gm0xy September 14, 2026 at 04:47AM

Show HN: VibeWorld – a shared terminal world for developers and scientists https://ift.tt/Z0hxksF

Show HN: VibeWorld – a shared terminal world for developers and scientists Vibeworld is a persistent cyberpunk shared world that runs in your terminal, where you can meet other developers and scientists to have company at 2 AM while screaming at your LLM :) you can connect with other scientist, chat, and includes also use vocal chat if you want to use it. There is a world and a moon, and they are completely 3D rendered and animated. In the moon there is the "complaint crater": a place where you can scream an insult against your claude or codex session and everybody from the space can see it. You can create your pixel avatar! There is also the "stargazing ledge": a place where you can see the stars and whatever happens in the sky. You can chat in the meantime if someone else is there too, or just watch our Earth. Sometimes you can see galactic wars, and there is a plant that grows but dies if nobody waters it. You can leave it on the second monitor while working (it does not use a lot of RAM): watch the sky when you want, and sometimes you may chat with some other scientist in your same situation. In the world, continents are scientific macroareas, and cities are specializations: you can create your corners where you can speak and help others (but for now it is quite empty). You can install in one command and by just typing "vibeworld" in your terminal, you are inside the world. There are some games inside and a sort of Doom where enemies says to you "Retracted" or "dedline tomorrow" when shooting you :). There is also an awkward reason why I am posting the work here. I have just discovered that another product Vibeworld.build uses the same name and the same concept (shared multiplayer world for developers). I don't know how independently it was developed. It is not a TUI, but it is a full, paid application developed by a company after my project was released. To be honest luckly I find my project more funny. I do care about preserving the chronology, my VibeWorld was released before, and there are verifiable timestamps in the GitHub. I just don't want the original public record to disappear if a much larger implementation of a very similar concept gets more attention later. I would like to hear what people think about it! :)) https://ift.tt/uW6Zh8D September 14, 2026 at 03:00AM

Show HN: Kibble – a reader for AI news, tutorials, code and models https://ift.tt/CyYu7Ic

Show HN: Kibble – a reader for AI news, tutorials, code and models https://ift.tt/IXLPi76 September 14, 2026 at 02:39AM

Show HN: Simpleboot and Easyboot https://ift.tt/TlUR4G0

Show HN: Simpleboot and Easyboot These are FLOSS boot loaders and disk utilities which follow the suckless philosophy ( https://ift.tt/Jgfikas ). Despite being totally dependency-free, they come with a fully featured single command to create bootable disk images out of a directory (utility is available on Windows, Linux and other POSIX systems). Usage is as simple as it gets. There are two repositories, depending on the desired use case: Simpleboot is the little brother, an embeddable boot loader: https://ift.tt/NRFmngY - multiplatform (BIOS, UEFI, RPi, coreboot) - very small (less than 64k), single binary - also flashable into ROM (option ROM, expansion ROM, coreboot payload, etc.) - easy to configure (single config file, checked for validity by the disk creator utility) - one backup boot option - capable to boot Linux and simplified Multiboot2 kernels (see below) Easyboot is the big brother, an interactive boot manager: https://ift.tt/MV0vFib - multiplatform (BIOS, UEFI, RPi) - interactive boot menu for dual booting multiple OSes - easy to configure (similar syntax as GRUB's, but much simpler) - up to 9 boot options - transparent payload decompression - on-the-fly, transparent DSDT and DTB patching - plugin system to support multiple file systems and boot protocols - supports FAT12/16/32, exFAT, NTFS (v3, v3.1), ext2/3/4, XFS (SGI), UFS (v2, v4.4), mfs (Minix3), BeFS (Haiku), plus any root file system (zfs, btrfs, etc.) provided the kernel is on the ESP - supports booting Linux, Windows, OpenBSD, FreeBSD, FreeDOS, ReactOS, MenuetOS, KolibriOS, SerenityOS, Haiku, Multiboot1, Multiboot2 (in PE/COFF, ELF, a.out, etc. formats) - comes with a (very minimal but useful) kernel debugger that works on real machines too Full disclosure: forking Simpleboot into Easyboot was sponsored by The Free Software Foundation Hungary ( https://fsf.hu/nevjegy ), created in appliance of FSF.hu's Free Software Tender 2023. Their default "simplified Multiboot2 protocol" is an easier to use superset of the GRUB's Multiboot2 protocol. This protocol handles native 64 bit kernels (no 32-bit trampoline code), programming language and ABI agnostic (works with native C, C++, Rust, Go, Ada, Pascal, etc. kernels, no Assembly preambule needed), supports transparent higher-half mapping, not tied to x86, and has SMP support too (running the kernel on all CPU cores), passes EDID and kernel segmentation information (not in GRUB), etc. etc. etc. An example kernel is provided in the repo: https://ift.tt/CXP94fc If needed, there's an Easyboot plugin to support the old-fashioned, x86-only, GRUB-compatible Multiboot2 protocol (embedded tags, 32-bit entry point, no higher-half, GRUB ABI). Documentation and detailed specification is available in German, English, Spanish, French, Hungarian, Italian, Japanese, Dutch, Polish, Portuguese, Russian and Chinese (some machine translated, sorry). I would really love to hear your opinion and constructive criticism. Simpleboot is feature complete (only bugfix allowed), but Easyboot is expandable with new features via plugins. https://ift.tt/MV0vFib September 13, 2026 at 10:48PM

Show HN: Dry Diving Club – A darkly comic browser game https://ift.tt/oklzuHF

Show HN: Dry Diving Club – A darkly comic browser game https://drydiving.club/ September 12, 2026 at 10:48PM

Show HN: Bodily Oddities https://ift.tt/Kxhk08L

Show HN: Bodily Oddities When I was about 11 years old, my best friend and I were playing during recess at school, and I was carrying him around on my back, presumably pretending to be a multipart attack robot. All of a sudden, my heart started hurting, and I collapsed to my knees, and the robot was no more. Every time I inhaled, it would feel like a spike was being driven into my heart, and my breathing got completely shallow. I was sure I was done for, when all of a sudden, after an exhale, it disappeared. It wasn't until I was in my twenties that I learned this was called Precordial catch syndrome and it happens to most everyone. Every friend I've told about it was surprised, and also most knew the feeling. I collected a growing list of strange things bodies do ever since. And now finally I made it into a little page for others to see: https://ift.tt/qplfbaU It includes a form to tell me about new things, if you think they belong on the page. Feedback welcome! https://ift.tt/qplfbaU September 11, 2026 at 03:33AM

Show HN: Raggy – A lightweight CLI tool for RAG over local documents https://ift.tt/dr2HbLt

Show HN: Raggy – A lightweight CLI tool for RAG over local documents https://ift.tt/2ImnVXB September 11, 2026 at 11:01PM

Show HN: I built an AI 'Fog of War' for life goals https://ift.tt/mId5FMc

Show HN: I built an AI 'Fog of War' for life goals https://ift.tt/TrXCNQD September 10, 2026 at 11:19PM

Show HN: Pascal's Pager – Webhooks In. Push Notifications Out https://ift.tt/c6uj1WS

Show HN: Pascal's Pager – Webhooks In. Push Notifications Out Sometimes it just takes too long to parse a webhook from one service to another just so you can get a push notification on your iPhone. Pascal's Pager turns any JSON webhook data into a human readable push notification on your iPhone using AI. It includes notification grouping and data redaction so you can select to exclude specific values from ever going to the AI. https://ift.tt/74q3eX6 September 10, 2026 at 11:03PM

Show HN: Mushrooms – A personal MCP server for 2,500 apps, so your AI can act https://ift.tt/3iewaYd

Show HN: Mushrooms – A personal MCP server for 2,500 apps, so your AI can act https://ift.tt/1xyMBgz September 9, 2026 at 11:13PM

Show HN: Moral.games, a 1v1 ethics game with an AI judge https://ift.tt/mKN0J8p

Show HN: Moral.games, a 1v1 ethics game with an AI judge https://moral.games September 9, 2026 at 11:08PM

Show HN: Locksmith: Store Maven Secrets in the macOS Keychain (Or a Unix Socket) https://ift.tt/o4kWQDf

Show HN: Locksmith: Store Maven Secrets in the macOS Keychain (Or a Unix Socket) Hello HN, In the age of LLMs sucking in random secrets, sandbox escapes, and RCE orbital bombardment, I thought it'd be a good idea to create a Maven Extension that defers to the MacOS keychain for resolving secrets. In general, it's a good idea to not have any secrets (passwords, tokens, etc) stored in plaintext files. Also, this allows your machines to be FIPS-140 complaint, if thats a thing for your job. Locksmith is a Maven Core Extension that defers to the MacOS Keychain. The entry format in settings.xml looks like: `{[type=locksmith]nexus.superbiz.example.com/username}` This was a fun project and I used the Project Panama FFM with jextract for the first time. The FFM is a great iteration on JNI (which still has it's place) and was pretty much brainless to use. Setup is quick and easy and I tried to make the readme as friendly as possible. As an aside, I've also architected the core Library indecently from the Maven bits, so if you do need to read from the MacOS keychain in a project, you could pull the core Library in without dragging in Maven. Being 2026, of course Claude was used to assist in the creation of the project, however Locksmith is not vibecoded top-to-bottom. I personally loathe AI slop. I use LLMs as a tool, not a crutch. Enjoy! https://ift.tt/f6kuCai September 9, 2026 at 11:01PM

Show HN: Give your AI agent on-screen guides that show users where to click https://ift.tt/Ld1VEYm

Show HN: Give your AI agent on-screen guides that show users where to click Hey HN. I'm Christian, one of the founders of Frigade (YC W23). I've noticed that a lot of in-app AI agents struggle to actually understand the products they exist in. For instance, let's say a user asks an agent how to do something in a given SaaS product. In an ideal case, maybe that agent replies saying it has a tool to do the task and just automates that work entirely for the user. That's a great outcome. But often that's not the case. Maybe there is no tool call for that exact task, or maybe the user's question is best solved by a specific UI workflow or interface. In these cases, many agents tend to fall back on basic RAG on their help center, or sometimes even searching the internet for an understanding of their own product. This can be a very slow process and most of the time help center articles are outdated as products evolve faster than them today. Even worse, no one likes reading a long list of bullets and mapping that back to a UI. My tool (Assist API) solves this gap with a single tool call defined like this: const frigade_guide_tool = { description: 'Call this tool to answer product questions or guide the user through a task.', parameters: { query: { type: 'string', description: 'What the user is asking or wants to do', }, }, run: ({ query }) => frigade.assist({ query }), } Here's a demo I recorded on how to set it up with the Vercel AI SDK: https://www.youtube.com/watch?v=9WQ0UbLjC6I When called, the tool will do the following: 1) Gather context on what the user is seeing on screen, their permissions, feature flags, and more. Then one of the following: 2a) If solvable: Generate an on screen guide for how to fix a given problem 2b) If conceptual: Return text describing to the parent agent how to solve the problem 2c) Reject (i.e. unable to help) How does the tool know what to do? The tool learns a given application UI by using a browser-based agent. You provide a test account to your software (i.e. staging og preview), and a browser agent logs in and works its way through the entire product. It then builds its own map of how the application works which can the be queried about any product-related question or how to get from A to B in the UI. It also writes its own documentation from this map. The agent re-runs on a schedule or can be triggered through CI/CD. Docs and more details: https://ift.tt/RIfnbZg September 9, 2026 at 10:09PM