Flux 3

Writing by hand is good for your brain

The Beam Engine

What happened to TheNumbers.com

Why Software Factories Fail (or: harness engineering is not enough)

What else do people draw on gradient.horse?

Quickly rewrite Git repository history

98.css

I regret migrating to Codeberg

Hi HN, we are Marcos and Harrison, cofounders of Palmier (<a href="https:&#x2F;&#x2F;palmier.io">https:&#x2F;&#x2F;palmier.io</a>). We are building Palmier Pro, an open source macOS video editor, with built-in AI generation and a local MCP server that connects to your agent. Here are a few demos:- Making some AI transitions: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=hbM_-eR1GX4" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=hbM_-eR1GX4</a>- Multicam editing with Codex: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=SjS2q2LT1q8" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=SjS2q2LT1q8</a>- Cutting long form clips into shorts: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=PR66eN2ouuQ" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=PR66eN2ouuQ</a>We built Palmier Pro as an internal tool when we were making AI launch videos for other startups. The main problem it solved in the beginning was the back-and-forth between AI generation platform and video editor. The iteration loop was awkward: AI videos → download → import to editor → edit → realize we need to change the AI video → repeat. So we built a minimal video editor where we could let Claude generate AI videos inside the editor.As we gave more and more tools to the agent, we wanted to push to see what else agents can do in the video editing space. So today, your Claude&#x2F;Codex can:- Manage projects inside Palmier Pro- Import media from a public URL or filesystem to the project, and organize them in folders- Search media (by embedding footages using SigLIP2 running locally)- Edit the timeline (tracks&#x2F;clips&#x2F;keyframes operations)- Generate images, videos, sound effects, captions, music- Export videosThere are two ways for LLMs to interact with the editor: by connecting to the local MCP server, or using the in-app chat. Both use the same tools and APIs exposed by the video editor.We have seen people using MCP server to connect to their own workflow to automate massive-scale video editing (e.g. given this same podcast style, replicate it with other footages that I have). We have also seen people using the in-app chat where it lives closer to the editor UI, with lower latency for faster iteration.We don&#x27;t believe that AI is going to replace human creativity (nor should it), but where it can really help is in automating the gruntwork in video editing. Most work in the editing workflow is more mechanical than creative. Our vision is to build a video editor where AI can enable more individuals to create.Throughout our experiments, AI is not very good at creative editing, but given a pattern (transcription-based, beat-based), it can do a decent job at rough cut.We built Palmier Pro in Swift as an MVP because we wanted better performance and minimal dependencies (no nodejs&#x2F;webview), with some native macOS APIs like SpeechAnalyzer and CoreML for us to run some models locally. We use SpeechAnalyzer for local transcriber, SigLip2 to embed video frames, beat_this for beat detection, Silero VAD for silence detection, all running locally. The tradeoff is that we don&#x27;t support Linux or Windows at the moment.Palmier Pro is open source and free to try out (macOS 26 only at the moment, though - we&#x27;ll support more platforms over time, but for now are focusing on iterating the core product).No login required except for the AI generation features, which route requests to our backend. We are offering free credits on sign up so you can try out the AI generation as well.We&#x27;d love to hear your feedback!

Show HN: Palmier Pro – Open-source macOS video editor built for AI

Why Sony can't bring back its classic Walkman models

Astronomers may have found the first exomoon

The arguments against open source AI are bad

hey HN, Jonathan and Guy here, creators of OneCLI (<a href="https:&#x2F;&#x2F;onecli.sh&#x2F;">https:&#x2F;&#x2F;onecli.sh&#x2F;</a>). OneCLI is an open source vault for AI Agents.Traditional vaults are used to store your secrets and, on demand, provide them to you all in a secure way, trusting the person to keep them safe. We figured that in the agent&#x27;s world, this is not the case, as you don&#x27;t know what happens with the secret after it&#x27;s delivered to the agent, or where it was saved. Or maybe someone even manipulated them to hand them over...From that understanding, we decided to build a network gateway that sits between your AI agents and the services they call. OneCLI matches the request by host&#x2F;path, verifies the agent should have access, swaps the placeholder for the real credential, and forwards the request. 
the secrets set inside the OneCLI vault, encrypted on rest, or could fetch in realtime from your bitwarden &#x2F; 1password wallets.Demo - <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=5e5pbPEzZfY" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=5e5pbPEzZfY</a>.We started working on this by accident, even though our careers were in the security space. We were working on a devtool called ChartDB, an open-source DB tool. When OpenClaw took off back in January, we started using it to orchestrate agents on top of ChartDB. We quickly understood there is a big issue around auth. Agents need credentials to do real work, but to give them those secrets would not be the best idea. they keep them in their memory and also write them down to local files and their sessions as plain text. And we knew that agents can easily be fooled into giving up those API keys&#x2F;secrets. So we needed some way to control the agent and stop prompt injections from tricking it into using its services for an attacker&#x27;s benefit. Not providing the keys to the agent + adding alerts or human-in-the-loop for sensitive operations, in case someone manipulates the agent, and access logs are being audited.We use it ourselves daily. My OpenClaw runs my day across Attio, Gmail, and my calendar, with human-in-the-loop approval on sensitive actions. The approval is enforced at the network layer, so it holds whether the agent goes through MCP, CLI, curl, or code it wrote on the fly. Guy uses it to review PRs but can&#x27;t merge without his approval.Companies mostly use it for coding agents currently, which get creative about finding ways to elevate their permissions to reach the goal. With OneCLI, it doesn&#x27;t matter what the agent finds: if the request isn&#x27;t in policy, it will not go through.The proxy is written in Rust, the dashboard is Next.js, and secrets are AES-256-GCM encrypted at rest. Everything runs in a Docker container. It works with any agent framework (Claude Code, Codex, Cursor, OpenClaw, Hermes or anything that can set an HTTPS_PROXY).It won&#x27;t stop an agent from misusing access it legitimately has, so scope policies tightly!happy to answer anything. We believe we can&#x27;t trust the model to behave and have to set deterministic rules to stay in control. Comments welcome!

Show HN: OneCLI – OSS credential gateway that keeps secrets out of AI agents

Learn WebGPU for C++

Show HN: Claude-thermos keeps your Claude session warm for you

AI Companies Are Trying to Hide a Staggering Amount of Debt

Emacs Is a Lispboard

Visualizing the Artemis II Mission

Trifle is an open-source time-series analytics library that aggregates nested counters instead of storing raw events. All in the database you already have. After rebuilding it twice over 10 years, it now tracks ~1B events a day at my day job.It started in 2015 as my own Rails APM. I plugged into ActiveSupport::Notifications, got a few small users, and one bigger one whose scraping app broke everything. That sparked the core idea: aggregate counters into pre-defined time buckets, so a single write increments multiple buckets at once. The APM eventually faded away without much traction.Later in 2021 I needed analytics at my day job. Instead of going for something out there I revised the idea of Trifle as a more generic analytics library, borrowing some data warehouse ideas. First used Redis, then Postgres, eventually MongoDB. Hence why Trifle::Stats comes with multiple drivers that keep the DSL unified while storage layer changes with your needs. In our case (huge write volume, some reads) PG read faster but slowed on large writes.The nested values are the whole trick here. Single:<pre><code> Trifle::Stats.track(
 key: &#x27;requests::aws::s3_uploads&#x27;,
 values: {
 count: 1,
 status: { request.response_code =&gt; 1 },
 size: payload.bytes,
 duration: { sum: request.duration, count: 1 }
 }
 )
 </code></pre>
builds up counts for requests, success rate, result status codes, duration for multiple time buckets at once. Single bucket from 2am then looks like:<pre><code> { count: 14, status: { 200: 12, 500: 2 }, size: 5628341, duration: { sum: 43, count: 14 } }
</code></pre>
If request.duration is in seconds, then sum stored under duration would be in seconds as well.Success rate is never stored, but it is calculated by dividing 200s over total number of requests. Same with average duration: sum over count. You ask for a metrics key, granularity and timeframe and you get back aggregated values at each point. Ready for charts or to answer &quot;Average response time over last 30 days&quot;.There&#x27;s a Series wrapper for aggregating and formatting values for charts in a simple call. And as building dashboards is not as much fun for other devs as I thought, I built Trifle App - a visual layer with dashboards, scheduled digests and alerts. It&#x27;s written in Elixir, so I ported the library to Elixir too. And later to Go for a CLI. All three are compatible, write in one and read in another.Today we track activity from over 100M background jobs a day which turns into about 1B events. It runs surprisingly cheap when you&#x27;re willing to trade some safety away (turn off journaling and write concerns in Mongo). 3-node Hetzner MongoDB cluster where the primary does 20% utilization costs us around $1k&#x2F;month.It has its limitations. Payloads can&#x27;t hold tens of thousands of keys. Documents becomes too large to update efficiently. Some planning ahead is needed. And then there are no dimensions. Sometimes you can nest them (country - there are only so many countries), sometimes it&#x27;s better to have dedicated metrics key per dimension (customer - growing forever). That multiplies tracked events, hence 1B events from 100M jobs.The libraries are MIT. The App is source-available under ELv2 - free to self-host and paid cloud if you want it managed. I build this on the side with no investor money to burn on a free service.Happy to answer anything about architecture, storage models, my failures or why I didn&#x27;t give up on this yet.

8:10:31 AM FRIDAY JULY 24, 2026

THE HACKER NEWS