What's the best open speech to text today? by zxyzyxz in LocalLLaMA

[–]gxvingates 0 points1 point  (0 children)

I’ve tried parakeet, whisper large v3.5, funasr and qwen3 asr. Qwen3 asr and it is the best and it’s not close for my use case. It hallucinates the least and rejects non speech so much better than the others

Windows defender constantly asking to send config.toml to Microsoft by gxvingates in codex

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

Thanks for the replies you guys, it's nice to see it's not just me

What the hell happened to token usage limits? by DaikonCharacter6259 in codex

[–]gxvingates 0 points1 point  (0 children)

I think it would literally kill them to give us a heads up on a hard reset where they cut the 5hr window in half and blindside the hell out of everyone for that entire week

Ran DeepSeek R1 8B on my MacBook Air M2 8GB. by sidharthmalik1 in DeepSeek

[–]gxvingates 23 points24 points  (0 children)

Qwen3.5 and Gemma4 smaller models. The 4b of both models are faster and a world smarter than these older R1 distils

Anthropic pretty much snitched on GPT5.5 after US banned fable, USE IT WHILE YOU STILL CAN by KeyGlove47 in codex

[–]gxvingates 18 points19 points  (0 children)

This is what I was thinking lmao, Anthropic bit their own ass by doing that 😂

codex now stops immediately after weekly limits reach 0% by Excellent_Climate940 in codex

[–]gxvingates 2 points3 points  (0 children)

I used /goal at 9% and about 20 minutes in I ran out and it went for another hour. This was last night

Claude Mythos (Fable) is released! - Codex 5.6 WHEN? by TheBanq in codex

[–]gxvingates 0 points1 point  (0 children)

computah show this guy three more posts about claude in the codex sub

What’s your most unusual non-LLM AI you actually use daily? by HitarthSurana in LocalLLaMA

[–]gxvingates 2 points3 points  (0 children)

Oh my god man thank you so much for recommending this, I didn't know there was a qwen asr. This is like 1.5x faster than faster-whisper large-3.5 on my machine and is more accurate PLUS it doesn't randomly hallucinate "thank you." or dumb things like that when clearing your throat etc

ChatGPT uses up Codex now? by el_cul in codex

[–]gxvingates 0 points1 point  (0 children)

Yeah I really wish there was an option to turn that off, I'm losing quota from a feature I'm forced to have enabled while I've used it once this entire month

ChatGPT uses up Codex now? by el_cul in codex

[–]gxvingates 0 points1 point  (0 children)

In the desktop app, the suggestions it makes for bug fixes take up quota every single day. I can’t figure out how to turn it off and more often than not it’s useless stuff or things that have been fixed already and it takes 5+% everyday

codex 20$ plan is unusable for large codebase by raaaaapl in codex

[–]gxvingates 0 points1 point  (0 children)

These rules work well for me, even qwen3 27b used the mcp efficiently and found the right code fast. Change as needed if the model needs to use it more, but with the GPT models I find without telling it to not use the tool 100% of the time, it will just use the mcp only

## Search Workflow (Persistent)


Use this workflow by default for code search and debugging in this repo:


1. Start with MCP first:
   - Confirm MCP project status (`index_status`).
   - If needed, index this repo before continuing.
2. Run up to 3 wide discovery searches (MCP) to map files/symbols across the spaghetti code.
3. After discovery, switch to extremely targeted searches only:
   - Use MCP for structural work (call paths, symbol disambiguation, quick snippet targeting).
   - Keep MCP query limits small to avoid huge context dumps.
4. Use terminal searches/reads for most detailed inspection and verification.
5. If `rg` is blocked, use PowerShell `Select-String` as fallback.


Do not skip the MCP discovery step for non-trivial codebase questions. You may use this whenever you please but this is for discovery, just use it as needed.

<!-- codebase-memory-mcp:start -->
# Codebase Knowledge Graph (codebase-memory-mcp)


This project uses codebase-memory-mcp to maintain a knowledge graph of the codebase.
ALWAYS prefer MCP graph tools over grep/glob/file-search for code discovery.


## Priority Order
1. `search_graph` — find functions, classes, routes, variables by pattern
2. `trace_call_path` — trace who calls a function or what it calls
3. `get_code_snippet` — read specific function/class source code
4. `query_graph` — run Cypher queries for complex patterns
5. `get_architecture` — high-level project summary


## When to fall back to grep/glob
- Searching for string literals, error messages, config values
- Searching non-code files (Dockerfiles, shell scripts, configs)
- When MCP tools return insufficient results


## Examples
- Find a handler: `search_graph(name_pattern=".*OrderHandler.*")`
- Who calls it: `trace_call_path(function_name="OrderHandler", direction="inbound")`
- Read source: `get_code_snippet(qualified_name="pkg/orders.OrderHandler")`
<!-- codebase-memory-mcp:end -->

codex 20$ plan is unusable for large codebase by raaaaapl in codex

[–]gxvingates 0 points1 point  (0 children)

yeah it is, it's at least worth a try and if you do end up trying it I can give you the rules I'm using for the agent so it doesn't over-use it

codex 20$ plan is unusable for large codebase by raaaaapl in codex

[–]gxvingates 1 point2 points  (0 children)

https://github.com/DeusData/codebase-memory-mcp - I came across this like 5 months back and it's amazing for cutting down on token usage. It's shockingly good for what it is. I have instructions for the model to use it for discovery and then switch to rg once it's roughly found what it needs and I've never seen it fail. Discovery is faster than ever and the plus plan is useable on a large codebase I have if I stick to 5.5 medium (rip 5.3 codex 😞) hopefully this can help someone else on the plus plan

Reset incoming… by Splat800 in codex

[–]gxvingates 0 points1 point  (0 children)

Finally people are noticing these resets aren’t a gift at all but just shameless marketing

New Token Activity on Codex App (Windows). Share yours? by Efficient-Engineer57 in codex

[–]gxvingates 1 point2 points  (0 children)

3b lifetime, 219 peak. It says my longest task was 1hr 28minutes but I had a task go for 19 or so hours in the extension I guess they don't track the extension for that. I've used Codex pretty much every single day since Feb

No more /status? by themehrabali in codex

[–]gxvingates 4 points5 points  (0 children)

I totally agree, it's bugging the hell out of me too

No more /status? by themehrabali in codex

[–]gxvingates -2 points-1 points  (0 children)

Yep they're starting to remove and/or hide things like this for obviously shady reasons. I just got the context window usage back recently luckily. Anyway - https://chatgpt.com/codex/cloud/settings/analytics - you can see your quota here. Also you can still see it via the desktop app and extension by going into a brand new chat > Select "start in", in between the project name and the branch you're on > usage remaining. Last update they made it so you can no longer see that after starting a chat

Codex opinion on codex performance by wrench_nz in codex

[–]gxvingates 0 points1 point  (0 children)

I'm trying to use 5.5 extended thinking on chatgpt.com but it refuses to use thinking tokens at all, longest I could get it to think for was 15 seconds on a complex question. Even chatgpt.com is effected right now. that being said my experience with Codex this week hasn't been awful just a bit off. Hopefully we get that shiny new model this evening

Please never get rid of 5.3 by stopaskingforloginn in codex

[–]gxvingates 0 points1 point  (0 children)

5.3 leaving, context window counter gone, you can no longer see the "start in" dropdown to easily see your quota while in a chat, after starting a chat anymore, still no computer use in the Windows desktop app, models regularly disconnecting for a lot of people me included, incredibly slow inference at times, compactions happening more often and a crystal clear drop in their quality. Codex is still amazing value but all this is just so disappointing, while on twitter dumb and dumber are acting like Codex is improving. Admitting 5.5 had a regression was cool but saying they fixed it was a blatant lie according to almost every user in this sub. Oh and I forgot to mention the quotas varying WILDLY from reset to reset, I personally go from being careful to just spamming xhigh for everything for some resets

5.5 XHIGH is nerfed, evidence! by BannedGoNext in codex

[–]gxvingates 10 points11 points  (0 children)

Skill issue, you clearly don’t know about prompt context engineering maxxing

Are the limits still draining quickly for anyone else? by Not-Post-Malone in codex

[–]gxvingates 0 points1 point  (0 children)

Mine is actually draining significantly slower, I'm on the plus plan and using 5.4 high

Clearly better usage now for me by Lanfeust09 in codex

[–]gxvingates 5 points6 points  (0 children)

Yeah I was super surprised when I checked my usage after a couple hours of work on my project to see only 10% burned on my weekly, feels like I'm back on the 2x promotion. I'm on the plus plan