HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
notque
vexjoy-agent
Python2026–2026
notque / vexjoy-agent

vexjoy-agent

VexJoy AI Agent with Jev Intelligent Routing - /do routes plain-English requests to the right specialist agent and gates the work with reviews, tests, and a learning loop.

2Distinct people
7Mentions
0Explicit recommenders
449GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

VexJoy AI Agent with Jev Intelligent Routing - /do routes plain-English requests to the right specialist agent and gates the work with reviews, tests, and a learning loop.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

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

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week7 dated mentions

Observed mentions: 2026-05-05 01:22:19 UTC to 2026-09-13 21:03:09 UTC. Weeks start Monday, UTC.

01232026-05-04 00:00:00 UTC to 2026-05-11 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 commentsMay 42026-05-11 00:00:00 UTC to 2026-05-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-18 00:00:00 UTC to 2026-05-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-25 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-01 00:00:00 UTC to 2026-06-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-08 00:00:00 UTC to 2026-06-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-15 00:00:00 UTC to 2026-06-22 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-06-22 00:00:00 UTC to 2026-06-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-06-29 00:00:00 UTC to 2026-07-06 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-07-06 00:00:00 UTC to 2026-07-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 62026-07-13 00:00:00 UTC to 2026-07-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-20 00:00:00 UTC to 2026-07-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-07-27 00:00:00 UTC to 2026-08-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-03 00:00:00 UTC to 2026-08-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-10 00:00:00 UTC to 2026-08-17 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-08-17 00:00:00 UTC to 2026-08-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-24 00:00:00 UTC to 2026-08-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-31 00:00:00 UTC to 2026-09-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-07 00:00:00 UTC to 2026-09-14 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 7

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
May 42026-05-04 00:00:00 UTC2026-05-11 00:00:00 UTC303
May 112026-05-11 00:00:00 UTC2026-05-18 00:00:00 UTC000
May 182026-05-18 00:00:00 UTC2026-05-25 00:00:00 UTC000
May 252026-05-25 00:00:00 UTC2026-06-01 00:00:00 UTC000
Jun 12026-06-01 00:00:00 UTC2026-06-08 00:00:00 UTC000
Jun 82026-06-08 00:00:00 UTC2026-06-15 00:00:00 UTC000
Jun 152026-06-15 00:00:00 UTC2026-06-22 00:00:00 UTC101
Jun 222026-06-22 00:00:00 UTC2026-06-29 00:00:00 UTC000
Jun 292026-06-29 00:00:00 UTC2026-07-06 00:00:00 UTC101
Jul 62026-07-06 00:00:00 UTC2026-07-13 00:00:00 UTC000
Jul 132026-07-13 00:00:00 UTC2026-07-20 00:00:00 UTC000
Jul 202026-07-20 00:00:00 UTC2026-07-27 00:00:00 UTC000
Jul 272026-07-27 00:00:00 UTC2026-08-03 00:00:00 UTC000
Aug 32026-08-03 00:00:00 UTC2026-08-10 00:00:00 UTC000
Aug 102026-08-10 00:00:00 UTC2026-08-17 00:00:00 UTC101
Aug 172026-08-17 00:00:00 UTC2026-08-24 00:00:00 UTC000
Aug 242026-08-24 00:00:00 UTC2026-08-31 00:00:00 UTC000
Aug 312026-08-31 00:00:00 UTC2026-09-07 00:00:00 UTC000
Sep 72026-09-07 00:00:00 UTC2026-09-14 00:00:00 UTC101

What Hacker News says

7 sources
This is why I Blind A/B test everything. I burn a ton of tokens, but things actually have to prove their value. And the vast majority of things do not come close to doing so. I have my own AI agent full of stuff. I blind A/B test everything, but I also don't think the results are all that useful as a signal to others. Just because I Blind A/B test it 4 months ago, it's maybe not meaningful today. Maybe the word choices I use dramatically impact things. I do it, because I can prove the value, and see it with my own eyes. I don't even bother publishing the specific Blind A/B tests. Also, I've seen other people try to Blind A/B test and get it very wrong. If your measurements aren't good, the test is meaningless. I don't know. We're all working on these problems together. There's a lot of black magic (which is why I rely on hooks a lot). I'm
Read the rest
sure I have tons of black magic, I have a large little AI Agent. But what I know for certain, is it works for me. All it takes is for me to not use it, and I honestly don't know how everyone currently works with AI. I will link it, but it is not an endorsement for what you do. Mostly only other software engineers use it. And it's so very specific to the things I have to do. At best, maybe it sparks an idea for you to implement on your own. https://github.com/notque/vexjoy-agent
In The Token Compression Illusion: Why I'm Skeptical of RTK
This is why I created the /do router, to route to all skills. I also have anti rationalization, progressive context discovery etc. I only make it for me, so it's a bit complex and targeted towards me, and what I do, but it's pretty easy to adjust things. https://github.com/notque/vexjoy-agent Working on reading through Agent Skills, it seems we've converged on a lot of the same points, and I've never seen it, so trying to get an understanding of it. Edit 1: I don't like all the commands. I just rely on a single router to automatically decide what I want, and that feels like the most reasonable way to me to communicate with it. I don't want to remember things. And that's the way for me to scale the number of skills and activities. I don't have to think about them. Edit 2: We have very different routers. https://github.com/addyosmani/agent-
Read the rest
skills/blob/f504276d8e07... vs https://github.com/notque/vexjoy-agent/blob/main/skills/do/S... I personally wouldn't call theirs an intelligent router. They are dancing between a few different skills. We have extremely different setups there. But of course, I'm using way more context to get it done. I'm even sending it out to Haiku to build the route choices. I choose to use tokens to make things better for myself, not everyone would make the same choice, so I certainly see why they are using a few skills, and composing them. Edit 3: This is much easier for a user to wrap their head around because there's much less. I am only focused on the best improvements I can make that show value for my use cases. This is straight foward to reason about. This seems like a nice way to get the best concepts for people trying to understand them. I commend them for a clean, simple approach. Edit 4: Yeah, I think there are some things I can learn from them which is always good. I especially like simple decisions like collapsing the install details for each harness in the readme. I'm going to read over the entire thing and look for opportunities to improve my stuff. We are all working together, learning, testing, building, trying to find the best way to implement things.
In Agent Skills

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.