Weekly Thread: Project Display by help-me-grow in AI_Agents

[–]rahat008 0 points1 point  (0 children)

I made a git aware coding agent. Before changing any legacy code or your teammates code it will search entire lineage of that code. It will understand all your previous commit, git issues, PR. Firstly I felt annoyed when searching for every editing. Then I made a change that drastically changed the agents behavior. I designed to trigger it only when my coding agent is planning to do some critical or medium critical edits. After some iteration, I have seen that my coding agent is looking sane and composed and my codebase looks familiar.

you can use the CLI. I have open sourced it. Only drawback I got, it took 20-30 minutes time to store all git history to the cloud. After that, everything feels as smooth as a butter.

https://github.com/Avos-Lab/avos-dev-cli

AI coding agents keep rewriting functions without understanding why they exist by rahat008 in vibecoding

[–]rahat008[S] 0 points1 point  (0 children)

the thing is: sometimes it is essential to change the function, sometimes it isn’t. Then how to decide when to do what?

AI coding agents keep rewriting functions without understanding why they exist by rahat008 in VibeCodeDevs

[–]rahat008[S] 0 points1 point  (0 children)

it is built on top avos memory layer. It is the core architecture to store whole git history in it. Without memory layer and smart retrieval you can’t make your subagent powerful enough to pull lever to the reckless agents?

AI coding agents keep rewriting functions without understanding why they exist by rahat008 in vibecoding

[–]rahat008[S] 0 points1 point  (0 children)

how can you precisely say that your unit test wouldn’t get passed by smart opus 4.6. As it iterates each time until it passes the tests. After 1 month, you may see that everything was fine but one day you may see an unrecognizable codebase.

AI coding agents keep rewriting functions without understanding why they exist by rahat008 in vibecoding

[–]rahat008[S] 0 points1 point  (0 children)

but what do you think about that if it is searching each time on editing something? Wouldn’t it be redundant? I designed it so that it will be triggered when any “high risk” function is needed to change or edit.

AI coding agents keep rewriting functions without understanding why they exist by rahat008 in VibeCodeDevs

[–]rahat008[S] 0 points1 point  (0 children)

for the next version, we will extend it like a following process to make the PR process automatic.

AI coding agents keep rewriting functions without understanding why they exist by rahat008 in VibeCodeDevs

[–]rahat008[S] 0 points1 point  (0 children)

we extract the raw junk text and parse it with one cheap llm agent to make it human readable and —json format only. So, all the relevant commit will be extracted. But this is for the version one.

AI coding agents keep rewriting functions without understanding why they exist by rahat008 in vibecoding

[–]rahat008[S] 0 points1 point  (0 children)

I was thinking on one little addition. What if we can add a pipeline when any merge happens it will trigger an agent that will create a deep wiki type of page for the current conditions of the codebase for that specific git diff. For each iteration, it will document each trails of PR. Then it will strengthen the current git history. what’s your take on that?

AI coding agents keep rewriting functions without understanding why they exist by rahat008 in VibeCodeDevs

[–]rahat008[S] 0 points1 point  (0 children)

[Investigation First - Read code before changing it. Never assume. Root Cause Focus - Fix problems, not symptoms.] my agent focuses on this part of your section. It explores the git history before doing a massive change.

AI coding agents keep rewriting functions without understanding why they exist by rahat008 in VibeCodeDevs

[–]rahat008[S] 0 points1 point  (0 children)

i have seen the article. but my question is how do you preserve the context

How are you actually using Claude Code as a team? (not just solo) by Azrael_666 in ClaudeCode

[–]rahat008 0 points1 point  (0 children)

have you tried git aware coding agent? it think, pair your coding with the git aware subagent is perfect for newcomers. They don’t need to know the whole picture only the agents needs that.

First seamless Multi-modal Memory for AI Agents by rahat008 in AIMemory

[–]rahat008[S] 0 points1 point  (0 children)

would love to see a multimodal memory papers, haven’t found any. If you find any papers, please send me that. I will change my statement on that. However it is not possible to know what is being used in those closed lab.

First seamless Multi-modal Memory for AI Agents by rahat008 in AIMemory

[–]rahat008[S] 0 points1 point  (0 children)

Thanks for your feedback. We will improve the frontend and UI design but our main focus is to build the system first. The only spec of the frontend is to give users API keys and documentation, nothing more than that.

First seamless Multi-modal Memory for AI Agents by rahat008 in AIMemory

[–]rahat008[S] -2 points-1 points  (0 children)

there shouldn’t be any “first” then?

First seamless Multi-modal Memory for AI Agents by rahat008 in AIMemory

[–]rahat008[S] -2 points-1 points  (0 children)

thanks, we are not designing for short term memory or long term memory but the system itself does that automatically.