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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:24:10 PM 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
Ask HN: What are you building – I'd try it, pay for it, or even star your repo direct repository linkInformational

The discussion features a diverse array of independent developers showcasing projects ranging from API key management agents to coding tools and personal productivity apps. Participants primarily share links and brief descriptions of their work without engaging in substantive technical debate or criticism.

10 readable replies · Supporting reply 1 · Supporting reply 2 · Supporting reply 3

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

56 sources
I've been building VT Code for about a year as a way to understand how coding-agent harnesses work in practice. Most of the code has been built with the help of coding agents, including VT Code itself. My focus has been on designing and iterating on the harness: tool execution, context management, sandboxing, permissions, verification, long-running sessions, subagents, and provider support. It's written in Rust and runs primarily in the terminal. https://github.com/vinhnx/VTCode I'd be interested in feedback from others building coding agents, especially around long-running reliability and harness design.
In Show HN: VT Code – My attempt at building a coding-agent harness
This month marks 1 year since I first started self-research and building my own coding agent VT Code [0]. I've been learning and experiment with a lot of things to first adapt myself and to learn about AI native/harness engineering. Thankfully, last month VT Code receives highest amount of contributions from the open-source community. This month I will be focusing and enhance more long-running horizontal for VT Code such as plan mode, better strengthen tools policy structure and improve its harness as new and existing model grows exponentially. And If you are curious and want to fork it feel free, and welcome, let's build! [0] https://github.com/vinhnx/VTCode
In Ask HN: What are you working on? (August 2026)
This month marks 1 year since I first started self-research and building my own coding agent VT Code [0]. I've been learning and experiment with a lot of things to first adapt myself and to learn about AI native/harness engineering. Thankfully, last month VT Code receives highest amount of contributions from the open-source community. This month I will be focusing and enhance more long-running horizontal for VT Code such as plan mode, better strengthen tools policy structure and improve its harness as new and existing model grows exponentially. And If you are curious and want to fork it feel free, and welcome, let's build! [0] https://github.com/vinhnx/VTCode
In Ask HN: What are you working on? (August 2026)

Showing the 15 most recent of 56 sources. Enable JavaScript to search and browse every indexed mention.

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.