Show HN: VoidDB –A transactional key-value DB written in Go for 64-bit Macintosh https://ift.tt/BexbKwS

Show HN: VoidDB –A transactional key-value DB written in Go for 64-bit Macintosh https://ift.tt/LjMTy8A February 1, 2025 at 10:03AM

Show HN: Simple to build MCP servers that easily connect with custom LLM calls https://ift.tt/uKhFBP2

Show HN: Simple to build MCP servers that easily connect with custom LLM calls Hi! After learning about MCP, I'm really excited about the future of provider-agnostic, re-usable tooling. Unfortunately I've found that while it's easy to implement an MCP server for use with tools that support it (such as Claude Desktop), it's not as easy to implement your own support (such as integrating an MCP server into your own LLM application). We implemented a thin MCP wrapper that easily integrates with Mirascope calls so that you can hook up an MCP server and client super easily to any supported LLM provider. Excited to see what people build with this! https://ift.tt/hDjzy5F February 1, 2025 at 06:20AM

Show HN: Lua-libuv – A Lua with libuv experiments https://ift.tt/D3NGTu2

Show HN: Lua-libuv – A Lua with libuv experiments https://ift.tt/S45wLjU January 28, 2025 at 05:59AM

Show HN: Ros2_utils_tool, a powerful GUI toolset for ROS2-based utilities https://ift.tt/ONmeUl7

Show HN: Ros2_utils_tool, a powerful GUI toolset for ROS2-based utilities Hi Hackernews, over the past few weeks, I've been tirelessly working on a GUI toolset for all sorts of ROS2-based utilites to simplify my tasks with ROS at work. Now I want to present to you the ros2_utils_tool. This tool can do many ROS2-based utilites, for example editing a ROS bag file to remove, rename or crop topics, extracting a video or image sequence out of a ROS bag, creating dummy bag files or just publishing a video as a ROS topic. While being developed to be as simple and lightweight as possible, the toolset supports many advanced options, for example different video and image formats, custom fps values, switching colorspaces and more. I've also heavily optimized the tool to support multithreading or in some cases even hardware-acceleration to run as fast as possible. The tool offers full graphical user interface support for all features, while I've also added additional command line interface support for most of them. As of now, the ros2_utils_tool supports ROS2 humble and jazzy. The application is still in an alpha phase, which means I want to add many more features in the future, for example GUI-based ROS bag merging or republishing of topics under different names, or some more advanced options such as selecting messages for video or image generation. The ros2_utils_tool requires an installed ROS2 distribution, as well as Qt6 or Qt5 for the user interface, the cv_bridge for transforming images to ROS and vice versa, and finally catch2_ROS for unit testing. You can install all dependencies (except for the ROS2 distribution itself) with the following command: sudo apt install libopencv-dev ros-humble-cv-bridge qt6-base-dev ros-humble-catch-ros2 For ROS2 Jazzy: sudo apt install libopencv-dev ros-jazzy-cv-bridge qt6-base-dev ros-jazzy-catch- Install the UI with the following steps: cd path/to/your/workspace/src git clone https://ift.tt/Te1PMAo cd path/to/your/workspace/ colcon build Then run it with the following commands: source install/setup.bash ros2 run ros2_utils_tool tool_ui The ros2_utils_tool uses the EUPLv1.2 as license. More information, for example regarding the command line interface tools are shown under [0]. [0] https://ift.tt/EzLQPN3 https://ift.tt/EzLQPN3 January 31, 2025 at 09:13PM

Show HN: Workflow86 - An AI business analyst and automation engineer https://ift.tt/KkF4wNT

Show HN: Workflow86 - An AI business analyst and automation engineer Hey HN, We built Workflow86 to help teams build and automate their internal business processes and workflows using drag and drop components like forms, tasks, tables and nodes for business logic, API requests, running custom code etc. It works as a standalone process/workflow automation tool, or as a workflow customization layer on top of existing apps and systems like HRIS, CRM and ERP. One common problem we hear from users is that no-code still has a significant learning curve, and it can take some time to understand how to properly build something. Users also needed help with knowing what to build in the first place, or what a process might or should look like. To solve this, we've integrated an AI that acts as a business analyst/consultant and workflow automation engineer. This AI is powered by a combination of Large Language Models and lots of prompt engineering, RAG and prompt chaining techniques we developed along the way. See a demo of it in action here: https://ift.tt/lv7LjD0?... In business analyst/consultant mode, the AI helps users brainstorm ideas, identify and discover processes and draft what a process should look like. Like a business analyst/consultant, the AI works to pull and extract information and details from the user by asking the right questions rather than rely on the user's instructions alone. Once the required information has been gathered, the AI goes into engineer mode: it will plan and then build the entire workflow by selecting the right nodes, connecting them together and then fully configuring every single node individually as well. This includes writing custom code and API requests using stored credentials when required. Once a workflow is built, edits can be done manually or by asking the AI to adjust the workflow at any time (e.g., “Add a compensation band check before final approval”). The AI has full context of the current state of the workflow, so it can “patch” in any changes like adding new nodes, rewriting existing nodes and so on. Some use cases we’ve seen from customers include building: - automated compliance checks for new CRM leads - custom international contractor onboarding workflows on top of a HRIS - automated vendor risk assessment before ERP updates Try it out and let us know how the AI performs and any other feedback you have! Full docs can be found at https://ift.tt/A2y8kW6 https://ift.tt/fzOWPq9 January 30, 2025 at 10:35PM

Show HN: Audiocube – A 3D DAW for Spatial Audio https://ift.tt/h4rAivc

Show HN: Audiocube – A 3D DAW for Spatial Audio I’ve recently released my solo project Audiocube I wanted to make a 3D DAW, where spatial audio, physics, and virtual acoustics are all directly integrated into the engine. This makes it easy to create music in 3D, and experiment with new techniques which aren’t possible in traditional DAWs and plugins. I’d love to get any feedback on this software (Mac/Windows) to make it better. You can download it for free through the website. Thanks, Noah https://ift.tt/QjA9ocJ January 30, 2025 at 06:42PM

Show HN: Iterm-Mcp – AI Terminal/REPL Control for iTerm2 https://ift.tt/dgsZ7pj

Show HN: Iterm-Mcp – AI Terminal/REPL Control for iTerm2 Hi HN! Ever wish you could just point your AI assistant at your terminal and say 'what's wrong with this output?' That's why I built iterm-mcp. It lets MCP clients like Claude Desktop directly interact with your iTerm2 terminal - reading logs, running commands, using REPLs, and helping debug issues. Want to explore data or debug using a REPL? The AI can start the REPL, run commands, and help interpret the results. This is an MCP server that integrates with Claude Desktop, LibreChat, and other Model Context Protocol compatible clients. https://ift.tt/8KLXDrf Note: Independent project, not officially affiliated with iTerm2 ## Features *Efficient Token Use:* iterm-mcp gives the model the ability to inspect only the output that the model is interested in. The model typically only wants to see the last few lines of output even for long running commands. *Natural Integration:* You share iTerm with the model. You can ask questions about what's on the screen, or delegate a task to the model and watch as it performs each step. *Full Terminal Control and REPL support:* The model can start and interact with REPL's as well as send control characters like ctrl-c, ctrl-z, etc. *Easy on the Dependencies:* iterm-mcp is built with minimal dependencies and is runnable via npx. It's designed to be easy to add to Claude Desktop and other MCP clients. It should just work. ## Real-World Example: Debugging Sidekiq Jobs I needed to debug a Sidekiq job with complex arguments. The arguments were partially obfuscated in the logs. I asked Claude: "open rails console, show me arguments for the latest XYZ job". The model: 1. Launched Rails console 2. Retrieved job details 3. Displayed the arguments that I was looking for ## Architectural Journey This project had a couple interesting constraints around command execution: ### 1. Token Efficiency Challenge I wanted to constrain tokens as much as possible. I didn't want to send the entire output of a long running command to the model, but there's not a great way to know which parts of the output are important to what the model is doing. Sampling could be used here, but it's not well supported yet. *Solution:* I arrived at a pull-based solution for this. The command from the model is sent to the terminal, and the model is made aware of how many lines of output were generated. The model can choose to retrieve as many lines of the buffer that it thinks are relevant. ### 2. Long-Running Process Support I wanted to support long running processes. It turns out that when you run `brew install ffmpeg` - it takes a while, and it's not always clear when the job is done. In early proof of concepts, the model would assume the command completed successfully and begin sending additional commands to the terminal before the first command had finished. *Solution:* iTerm provides a way to ask if the terminal is waiting for user input, but I found that it tended to show false positives in certain situations. For example, a long running command would result in iTerm reporting that the terminal was waiting for input when in fact the command was still running. I found that inspecting the processes associated with the terminal and waiting until the most interesting of those processes settles to a low resource usage is a fair indicator of long running commands being ready for input. ## Requirements * iTerm2 must be running * Node version 18 or greater ## Safety Considerations * The user is responsible for using the tool safely. * No built-in restrictions: iterm-mcp makes no attempt to evaluate the safety of commands that are executed. * Models can behave in unexpected ways. The user is expected to monitor activity and abort when appropriate. * For multi-step tasks, you may need to interrupt the model if it goes off track. Start with smaller, focused tasks until you're familiar with how the model behaves. https://ift.tt/8KLXDrf January 30, 2025 at 11:44PM