HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
vinhnx
VTCode
Rust2025–2026
vinhnx / VTCode

VTCode

VT Code is a terminal-first coding agent for your repo, in the CLI and native macOS app.

3Distinct people
56Mentions
1Explicit recommenders
909GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

VT Code is a terminal-first coding agent for your repo, in the CLI and native macOS app.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

Thank you for checking out VT Code! “LLM-native code understanding” refers to VT Code's approach of using LLM as the primary mechanism for semantic code analysis rather than…

vinhnx used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 3:30:57 AM UTC.

Ask HN: What are you working on? (November 2026) direct repository linkDebated

The discussion centers on the tension between leveraging AI for rapid development and maintaining architectural control, with users debating whether manual implementation of complex systems remains valuable for learning. A significant sub-thread highlights the severe financial impact large language models have on content creators, sparking debate over potential mitigation strategies.

1068 readable replies · Supporting reply 1 · Supporting reply 2 · Supporting reply 3 · Supporting reply 4
Goodbye Claude, hello Pi direct repository linkDebated

Developers are divided between migrating to third-party harnesses like Pi for their customizability and control, versus staying with native tools like Claude Code due to concerns about stability, security, and vendor restrictions. The strongest disagreement centers on whether the flexibility of open-source harnesses outweighs the operational risks of manual configuration and potential Terms of Service violations.

493 readable replies · Supporting reply 1 · Supporting reply 2 · Supporting reply 3 · Supporting reply 4

Mentions over time

HN mentions by month56 dated mentions

Observed mentions: 2025-09-30 01:36:14 UTC to 2026-10-21 13:58:23 UTC.

02468102025-09-01 00:00:00 UTC to 2025-10-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsSep 20252025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 10 mentions; 3 submissions, 7 comments2025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments2025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsMar 20262026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments2026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 6 mentions; 2 submissions, 4 comments2026-06-01 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2026-07-01 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-08-01 00:00:00 UTC to 2026-09-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments2026-09-01 00:00:00 UTC to 2026-10-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2026-10-01 00:00:00 UTC to 2026-11-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 commentsOct 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Sep 20252025-09-01 00:00:00 UTC2025-10-01 00:00:00 UTC202
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC1037
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC725
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC101
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC202
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC101
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC202
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC321
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC624
Jun 20262026-06-01 00:00:00 UTC2026-07-01 00:00:00 UTC505
Jul 20262026-07-01 00:00:00 UTC2026-08-01 00:00:00 UTC202
Aug 20262026-08-01 00:00:00 UTC2026-09-01 00:00:00 UTC817
Sep 20262026-09-01 00:00:00 UTC2026-10-01 00:00:00 UTC312
Oct 20262026-10-01 00:00:00 UTC2026-11-01 00:00:00 UTC413

What Hacker News says

7 sources
I'm building a coding agent, named VT Code [0]. VT Code is a Rust-based terminal coding agent with semantic code intelligence via Tree-sitter. Supports multiple LLM providers with automatic failover and efficient context management. Support OpenAI, Anthropic, Google Gemini, xAI, DeepSeek, OpenRouter, Z.AI, Moonshot AI, MiniMax, and Ollama (local & Cloud). Agent Client Protocol and Model Context Protocol fully support. VT Code supports a rich set of configuration options, with preferences stored in vtcode.toml. Has both Visual Studio Code and Open VSX extensions so that you can install in VS Code or Cursor, Windsurf, Eclipse. I've been building it for several months now and enjoy the learning process, I also wrote a blog post and learnt a ton about terminal, ANSI processing. The learning has been immense for me, I now have working knowledg
Read the rest
e of ANSI escape codes, grapheme clusters, terminal emulators, Unicode normalization, VT protocols, PTY sessions, and filesystem operations, all the low-level details I would have never think about until I were implementing them. [1] [0] https://github.com/vinhnx/vtcode [0.1] https://deepwiki.com/vinhnx/vtcode [1] https://buymeacoffee.com/vinhnx/vt-code
In Ask HN: What Are You Working On? (Nov 2025)
Hi, for me, I will try my best to answer. In my experience, it all about giving the agent the right tool for job. We give them a grep tool and search, then the accuracy and reliability rely on the capable of the running model. > I ask the agent to generate things like: > { original_sentence: xxxx, improved_sentence: yyyy } > and I use the original_sentence to locate the original content, and replace it with the improved_sentence. To mitigate this, I build the apply patch pattern. [0][1] [0] https://github.com/vinhnx/vtcode/blob/main/vtcode-core/tests... [1] https://github.com/vinhnx/vtcode/blob/main/vtcode-core/src/t...
In Show HN: VT Code – Rust TUI coding agent with Tree-sitter and AST-grep
vinhnx·Nov 7, 2025Submission

Show HN: VT Code – Rust TUI coding agent with Tree-sitter and AST-grep

I’ve been building VT Code, a Rust-based terminal coding agent that combines semantic code intelligence (Tree-sitter + ast-grep) with multi-provider LLMs and a defense-in-depth execution model. It runs in your terminal with a streaming TUI, and also integrates with editors via ACP and a VS Code extension. * Semantic understanding: parses your code with Tree-sitter and does structural queries with ast-grep. * Multi-LLM with failover: OpenAI, Anthropic, xAI, DeepSeek, Gemini, Z.AI, Moonshot, OpenRouter, MiniMax, and Ollama for local—swap by env var. * Security first: tool allowlist + per-arg validation, workspace isolation, optional Anthropic sandbox, HITL approvals, audit trail. * Editor bridges: Agent Conext Protocol supports (Zed); VS Code extension (also works in Open VSX-compatible editors like Cursor/Windsurf). * Configurable: vtcode.
Read the rest
toml with tool policies, lifecycle hooks, context budgets, and timeouts. GitHub: https://github.com/vinhnx/vtcode
3 points · Open discussion
> “You only think you understand how a bicycle works, until you learn to ride one.” This resonates deeply with me. That's why I built one myself [0], I really really love to truly understand how coding agents work. The learning has been immense for me, I now have working knowledge of ANSI escape codes, grapheme clusters, terminal emulators, Unicode normalization, VT protocols, PTY sessions, and filesystem operations - all the low-level details I would have never think about until I were implementing them. [0] https://github.com/vinhnx/vtcode
In You should write an agent

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.