@Aaryaman

This project is finally over and I regret forgetting to post devlogs about it.

This is Warden: An agentic windows sytstem troubleshooter.

I spent a week trying to think of an agentic tool which is original, everything I thought of had already been built. During the brainstorming phase, I ran into wifi problems which led me to think of building an agentic system troubleshooter for windows.

I quickly wrote down the idea on a page and described it with as much detail as I could and then showed it to my friends. They loved the idea but worried about the feasibility, I assured them and said that it didn’t matter because the important thing is what you learn from it.

I spent another week trying to brainstorm the features and the technical aspects and when we were ready, we all started building.

After some time, we were ready with the first draft. It wasn’t great, the ui was very bad but it was a start. Soon after, we hired claude code and spent hours trying to debug and improve the badly written code in hopes of learning from our mistakes.

This went on for some time.

Eventually, the first version was ready and it passed all the tests. But, it still failed to actually troubleshoot real windows errors.

In the end, we realized that with 0 funds and a team of 5 lazy students, it wasn’t possible to compete with the folks at microsoft who built the not so useful windows troubleshooter.

My respect to real CPU designers, this is tricky work! The most difficult thing is working with the 256 different registers, that’s lots of wiring to get done.

Devlog #4 (Day 3)

Vector can talk now 🗣️🗣️

Added vector mentions, just @vector and say anything you like, it’s powered by groq and it also pulls the last 10 messages from the chat or thread for context.

“Tries” to use real names instead of user ids but that is still under progress.

Replies in threads 👍

and I wrote a proper README, edited package.json/package-lock.json as the names wasn’t updated there

LIST OF ALL CURRENT COMMANDS:

/vector-ping
/vector-weather
/vector-define
/vector-remind
/vector-reminders
/vector-unremind
/vector-apod
/vector-earth
/vector-github
/vector-leetcode
/vector-catfact
/vector-joke
/vector-hello
/vector-about
/vector-help
@vector

Total: 16

Now all i have to do is find a better weather api as someone told me that wttr.in isn’t that accurate and I also have to still make changes to the groq section, specifically the prompts and id formatting and how it reads the context

Devlog #4 (Day 3)

Vector can talk now 🗣️🗣️

Added vector mentions, just @vector and say anything you like, it’s powered by groq and it also pulls the last 10 messages from the chat or thread for context.

“Tries” to use real names instead of user ids but that is still under progress.

Replies in threads 👍

and I wrote a proper README, edited package.json/package-lock.json as the names wasn’t updated there

LIST OF ALL CURRENT COMMANDS:

/vector-ping
/vector-weather
/vector-define
/vector-remind
/vector-reminders
/vector-unremind
/vector-apod
/vector-earth
/vector-github
/vector-leetcode
/vector-catfact
/vector-joke
/vector-hello
/vector-about
/vector-help
@vector

Total: 16

Now all i have to do is find a better weather api as someone told me that wttr.in isn’t that accurate and I also have to still make changes to the groq section, specifically the prompts and id formatting and how it reads the context

Devlog #3 (end of day 2)

VECTOR HAS BEEN DEPLOYED 🎊 (nest application got approved)

man deployment took quite some time, I ran into a few problems, I created the path for systemd which i assumed was already supposed to exist, i installed git, node, npm, etc…

Added more meaningful slack commands:

1. REMINDERS!!!
   a. reminders are stored in a JSON database and periodically checks for reminders that are due. When the scheduled time arrives, the bot shoots a dm to the user
   b. the time though has to be in UTC, working on that

2. WEATHER!
   type ur city and boom

3. DEFINE!
   defines any word you want

minor changes:
/vector-about: links to github repo and this project
updated /vector-help of course
there is APOD video support
better command ui

LIST OF ALL CURRENT COMMANDS:

• /vector-ping - Check if Vector is online

• /vector-weather - Get current weather information for a city

• /vector-define - Look up dictionary definitions

• /vector-remind “” YYYY-MM-DD HH:MM - Create a reminder (UTC)

• /vector-reminders - List your active reminders

• /vector-unremind - Cancel a reminder

• /vector-apod- NASA Astronomy Picture of the Day

• /vector-earth - Latest EPIC Earth image from NASA

• /vector-github - View GitHub profile information and recent repositories

• /vector-leetcode - Get today’s LeetCode Daily Challenge

• /vector-catfact - Random cat fact

• /vector-joke - Random joke

• /vector-hello - Say hello to Vector

• /vector-about`- Information about Vector, creator links, and project pages

• /vector-help - Display all available commands

Total: 15

Devlog #2 (Day 2)

Vector has officially been used by other humans in the slack workspace, yay

Since the last devlog, I have added:

/vector-apod
/vector-earth
/vector-github
/vector-leetcode

I also built Slack Block Kit messages with images, allowing Vector to render images directly in chat instead of just showing a URL.

Had to debug the /vector-earth command a LOT but realized that my GET request url was wrong 😭

Current command list:

/vector-ping
/vector-hello
/vector-catfact
/vector-joke
/vector-apod
/vector-earth
/vector-github
/vector-leetcode
/vector-help

I still need to host it on Nest though

Devlog #1

Started work on Vector the Slack bot

So far I’ve:

followed the tutorial 😭

Added slash commands:
/vector-ping
/vector-catfact
/vector-joke
/vector-hello
/vector-help

Added global error handling

Today was Day 1 of building this bot. I have 0 experience making slack bots but I’ve made a few discord bots before.

It’s not much yet but I’ll take it.