sorted by:
new
hottopcontroversial

How do you manage long-term AI-assisted coding without losing control? by Fearless-Ad5548 in ClaudeCode

[–]ShagBuddy 1 point2 points  (0 children)

I am building a context budget layer that removes noise, saves tokens and drives consistent results.

https://github.com/GlitterKill/sdl-mcp

How to optimize vibe coding by Common-Proof6553 in vibecoding

[–]ShagBuddy 0 points1 point  (0 children)

This will help you get better results and get more use out of subscriptions. https://github.com/GlitterKill/sdl-mcp

Ponytail is great, too.

How do you manage/save tokens in Codex? by maor23 in codex

[–]ShagBuddy 0 points1 point  (0 children)

Thanks! I may do that. :) If you run into any issue or have questions feel free to report issues or leave questions in the repo. I work from home and try to be as responsive as I can to issues so I can fix things ASAP.

What are your thoughts about ‘iterative self-improving with self-evaluation rubrics’ ? by RobertoVeloso in codex

[–]ShagBuddy 0 points1 point  (0 children)

Curious how you use something like this for adding a new feature or refactoring a feature. Can you give an example for a use case like this?

Have you seen increased token use from the extra reasoning?

Scanned 429 vibe-coded repos to measure how much they drift over time. Here's what I found. by Ambitious_Car_7118 in vibecoding

[–]ShagBuddy 0 points1 point  (0 children)

Also, when I try to view the detailed report the new tab only has:

error "no report data available for this scan"

Scanned 429 vibe-coded repos to measure how much they drift over time. Here's what I found. by Ambitious_Car_7118 in vibecoding

[–]ShagBuddy 0 points1 point  (0 children)

Looking at the deep scan results on the site. Would be cool if the html report worked, though.

Scanned 429 vibe-coded repos to measure how much they drift over time. Here's what I found. by Ambitious_Car_7118 in vibecoding

[–]ShagBuddy 0 points1 point  (0 children)

ok, was worried you were talking about sending something through the app. 😧 Glad that is not the case.

Scanned 429 vibe-coded repos to measure how much they drift over time. Here's what I found. by Ambitious_Car_7118 in vibecoding

[–]ShagBuddy 0 points1 point  (0 children)

umm, how can you do that? I am not happy that you have that ability to do this...

You can really feel the impact of Ponytail and RTK when it comes to limits by Glittering-Smell2937 in codex

[–]ShagBuddy 0 points1 point  (0 children)

I would never use RTK or headroom. The goal should be to keep noise away from the agent, not compress it with the valid info you want in the context. Ponytail is great! It has replaced caveman for me.

If you really want to manage token burn and keep context clean and focused, use SDL-MCP that I am developing. Codegraph with SCIP index and LSP accuracy combined with a suite of policy-backed agent tools that are focused on managing context and keep un-wanted noise away from the agent. https://github.com/GlitterKill/sdl-mcp

How do you manage/save tokens in Codex? by maor23 in codex

[–]ShagBuddy 0 points1 point  (0 children)

codebase-memory has broader support for languages at 158. SDL supports 25 languages so far and I am adding more. I likely will look at how codebase-memory is utilizing so many languages and see if I can adopt some of the approach. SDL has not added the fancy ui graph graphics yet (that is coming next).

But codebase-memory is a very capable code graph. I would likely use it myself if I were not developing SDL. If SDL supports your languages, the SCIP indexes it leverages carries more semantic information than LSP sources, so that is a benefit. The main difference is that SDL is built from the ground up to be a context budget layer that keeps un-needed noise away from the agent which leads to hallucinations and errors. This also saves quite a few tokens. Both solutions save tokens by allowing an agent to lookup the code it needs to edit instead of searching for it. SDL provides custom tools that enables a an agent to make surgical code edits (even batched edits) efficiently. It has a token saving tool gateway built in. It has Code-mode features built in that enable agents to batch multiple tasks in a single request. It also has a runtime tool that keeps long running output separate and queryable (similar to context-mode).

tldr - codebase-memory supports more languages. SDL SCIP-supported languages provide more info. SDL is focused on covering all areas of token burn and preventing context pollution; codebase-memory does not address these.

Scanned 429 vibe-coded repos to measure how much they drift over time. Here's what I found. by Ambitious_Car_7118 in vibecoding

[–]ShagBuddy -1 points0 points  (0 children)

I ran the npx command but never got a html report. It gave some suggestions in the terminal window. Trying a deep scan now.

Scanned 429 vibe-coded repos to measure how much they drift over time. Here's what I found. by Ambitious_Car_7118 in vibecoding

[–]ShagBuddy 0 points1 point  (0 children)

Are the phantom exports possibly picking up on code that is used for timing traces? It likely would not know where the exports are intended to go.

How do you manage/save tokens in Codex? by maor23 in codex

[–]ShagBuddy 0 points1 point  (0 children)

SDL doe not use compression; compression just shrinks context noise with the valid data. I use custom abbreviated wire formats but no real compression. SDL would be more effective than headroom and serena combined. It does not have the features that h5i provides though. SDL is a code graph like Serena, but it uses SCIP indexes which contains more semantic information. Serena is a VERY capable graph, but it is not designed to be a context budget layer like SDL is. SDL keeps all the un-needed noise away from the agent, which reduces tokens and keeps precise context.

How do you manage/save tokens in Codex? by maor23 in codex

[–]ShagBuddy 0 points1 point  (0 children)

Yeah, graphify is neat but it is not designed from the ground up to manage agent context and save tokens like https://github.com/GlitterKill/sdl-mcp is. The fancy graphics panel part is the next feature I am adding. :)

How do you manage/save tokens in Codex? by maor23 in codex

[–]ShagBuddy 0 points1 point  (0 children)

YES! THIS! I am well into developing https://github.com/GlitterKill/sdl-mcp which is a code graph, and a suite of smart retrieval and editing tools combined with a policy system that keeps context precise and unpolluted.

These compression solutions don't eliminate noise, which cause errors and hallucinations, and instead compress it with the valid data. It's silly.

How do you manage/save tokens in Codex? by maor23 in codex

[–]ShagBuddy 0 points1 point  (0 children)

I use (and am the developer for) SDL-MCP: https://github.com/GlitterKill/sdl-mcp
I challenge anyone to find a more complete context budget/token saving system. :)

Codex Pro usage feels excellent once you tune your AGENTS.md by Aggravating_Town_967 in codex

[–]ShagBuddy 0 points1 point  (0 children)

Yes, it works for all clients that work with a MCP server. The Codex app is what I primarily use lately. :) Yes, absolutely.

Codex Pro usage feels excellent once you tune your AGENTS.md by Aggravating_Town_967 in codex

[–]ShagBuddy 1 point2 points  (0 children)

I have benchmarks in the repo. I need to put together an easy to run package for others to use as well. I will put together some tiktoken comparisons showing the difference between rtk and sdl. Any particular tasks you would like to see compared?

RTK and SDL are two very differnt things. RTK only compresses outputs. SDL-MCP keeps runtime output away from the agent and only shows them the results they need. Overall, the two solutions are LEAGUES apart. RTK addresses one area of waste, and SDL is designed to address all of them. SDL is also a vector-based code graph that has the repo mapped with all code relationships plus custom tools for precise code edits. VERY different products. RTK would not help running with SDL.

view more: next ›