开启时会模糊预览图，关闭后正常显示
As promised, the Ghostty search UI for GTK is on the way (PR is open). There's polish to do, but it's fully functional. For those who haven't paid attention, the macOS app (in tip) already has this.
Working on a new terminal: Ghostty. 👻 Prev: founded @HashiCorp. Created Vagrant, Terraform, Vault, and others. Vision Jet Pilot. 👨✈️
The next big thing after AI influencers will be AI audiences They will consume each other’s content, and then we can seal it off and launch the whole thing to outer space
“The woman scooping Silicon Valley” — BBC・hacker turned builder, blogger & consultant・ex: Threads, Instagram, etc
"A good deck opens doors before the product even exists." We're upgrading the system prompt to make it sleeker. （consulting-level, $1000/page worth quality） Stay tuned!
Staff @Kimi_Moonshot prev. co-maker of ModelizeAI & gemsouls "Personality goes a long way" @UCSanDiego
if you don't want to shell out $1700 for a souped up older thinkpad, get a USB 5G modem and an older thinkpad and just shell into a computer at home with mosh (an SSH remote shell that can handle flaky connections and no perceived latency)
the distribution is anything but normal
will be at re:Invent, Las Vegas (Dec 2) and Neurips (Dec 3-5)! please dm me if you would like to meet 1:1 or have cool events!
@axiommathai : careers@axiommath.ai
Actually, I like the first one it came up with, too, I'm going to include both in my AGENTS dot md: --- ### Morph Warp Grep — AI-powered code search **Use `mcp__morph-mcp__warp_grep` for exploratory "how does X work?" questions.** An AI search agent automatically expands your query into multiple search patterns, greps the codebase, reads relevant files, and returns precise line ranges with full context—all in one call. **Use `ripgrep` (via Grep tool) for targeted searches.** When you know exactly what you're looking for—a specific function name, error message, or config key—ripgrep is faster and more direct. **Use `ast-grep` for structural code patterns.** When you need to match/rewrite AST nodes while ignoring comments/strings, or enforce codebase-wide rules. **When to use what** | Scenario | Tool | Why | |----------|------|-----| | "How is authentication implemented?" | `warp_grep` | Exploratory; don't know where to start | | "Where is the L3 Guardian appeals system?" | `warp_grep` | Need to understand architecture, find multiple related files | | "Find all uses of `useQuery(`" | `ripgrep` | Targeted literal search | | "Find files with `console.log`" | `ripgrep` | Simple pattern, known target | | "Rename `getUserById` → `fetchUser`" | `ast-grep` | Structural refactor, avoid comments/strings | | "Replace all `var` with `let`" | `ast-grep` | Codemod across codebase | **warp_grep strengths** * **Reduces context pollution**: Returns only relevant line ranges, not entire files. * **Intelligent expansion**: Turns "appeals system" into searches for `appeal`, `Appeals`, `guardian`, `L3`, etc. * **One-shot answers**: Finds the 3-5 most relevant files with precise locations vs. manual grep→read cycles. * **Natural language**: Works well with "how", "where", "what" questions. **warp_grep usage** ``` mcp__morph-mcp__warp_grep( repoPath: "/data/projects/communitai", query: "How is the L3 Guardian appeals system implemented?" ) ``` Returns structured results with file paths, line ranges, and extracted code snippets. **Rule of thumb** * **Don't know where to look** → `warp_grep` (let AI find it) * **Know the pattern** → `ripgrep` (fastest) * **Need AST precision** → `ast-grep` (safest for rewrites) **Anti-patterns** * ❌ Using `warp_grep` to find a specific function name you already know → use `ripgrep` * ❌ Using `ripgrep` to understand "how does X work" → wastes time with manual file reads * ❌ Using `ripgrep` for codemods → misses comments/strings, risks collateral edits
Former Quant Investor, now building @lumera (formerly called Pastel Network) | My Open Source Projects: https://t.co/9qbOCDlaqM