While managing files in the terminal recently, I’ve been feeling a bit torn: on one hand, Yazi, as a next-generation terminal file manager, is genuinely excellent — fast, with great preview capabilities, and a flexible plugin system; on the other hand, if you’ve spent years using dual-pane file managers like Midnight Commander or Total Commander as I have, many operational habits are already ingrained in your muscle memory.
So I went ahead and forked Yazi to create dual-yazi: https://github.com/jtianling/dual-yazi. It’s not a ground-up rewrite of a file manager, but rather an added workflow layer on top of the original Yazi that I wanted most: fixed dual panes, independent tabs per pane, direct cross-pane copy/move, and toggling between single-pane/dual-pane and preview modes.
For me, this was a natural direction. I love Yazi’s modern TUI file management experience, but I’ve always missed the directness of traditional dual-pane managers — having two directories side by side, always in view. Now I’ve finally brought these two worlds together.
Repository links:
Read more....
I recently came across openai/symphony, and my first reaction wasn’t “I want to try this implementation” — it was “this release approach is interesting.”
Because the first option in its README isn’t teaching you how to install the official implementation. Instead, it directs you to build your own based on SPEC.md. Of course, they also included an experimental Elixir reference implementation, but that’s listed as the second option. This ordering itself is telling: what OpenAI really wants to convey first may not be a specific piece of code, but the design of the system.
I think this is worth noting. As code agents become increasingly capable, the “release” of some software in the future may not necessarily require a complete source code package. Instead, it could start with a sufficiently clear spec, letting everyone implement it in their own preferred language and runtime environment. Code will still exist, but it’s starting to look more like an instance of the spec rather than the sole deliverable.
Read more....
Sometimes when setting up a firewall whitelist for an app, the hardest part isn’t configuring rules — it’s not knowing which addresses the app actually connects to. And many modern apps aren’t just a single main process; they spawn helpers, renderers, crash reporters, and other child processes, so monitoring a single PID often isn’t enough. So I wrote a small tool called net-use that tracks the remote IPs accessed by a specified app and its entire process tree in real time, outputting deduplicated results.
Repository: https://github.com/jtianling/net-use
Read more....
While organizing skills for various AI coding tools recently, I realized each tool has its own directory and format, and switching between them gets confusing fast. So I built a unified management tool: skillsmgr. It installs skills centrally into ~/.skills-manager/ and deploys them to projects through a single .agents/skills/ directory, currently supporting 44 tools.
Repository: https://github.com/jtianling/skills-manager
Read more....
While using AI coding tools like Claude Code, Cursor, and Cline recently, I kept running into the same tedious problem: each tool has its own rules directory with slightly different formats, and team conventions need to be copy-pasted across multiple locations, easily drifting apart over time. So I built a small tool called rulesmgr to manage a single set of rules and deploy them to multiple tools at once.
Repository: https://github.com/jtianling/rules-manager
Read more....
A lightweight HTTP service that wraps Ollama’s Rerank model into a standard Rerank API, enabling Dify and other applications to use local Ollama models for document reranking.
https://github.com/jtianling/dify-ollama-rerank-adapter
Read more....
DeepSeek is great to use, but the company has never paid much attention to improving the user experience. For example, the DeepSeek website has never had a search function for conversation history. So I built one. It’s not published on the Chrome Web Store — it’s open source, feel free to grab it.
https://github.com/jtianling/deepseek-search-chrome
Read more....
I’ve always had to work with multiple programming languages simultaneously — either learning a new language while working on side projects, while also developing a company project, or writing both frontend and backend code in different languages within the same project. During these times, I always wished there was a website that could display syntax examples of the languages I’m using side by side, so my brain wouldn’t get mixed up when switching between them. After all these years, thanks to the maturity of large language models, building such a website has become incredibly easy. I’m posting the link here for anyone with the same need.
https://www.jtianling.com/programming-language-comparison
Read more....