chachachainsaw

3 ms·

1.
by chachachainsaw 14d ago
“I haven't had great success making Claude Code work with local Ollama/Quen.” What’s been the biggest blocker for you?
2.
by chachachainsaw 15d ago
I use omnigent with claude code and codex. I also built a tool ( https://frontmatter.news ) to help me figure out what similarities and differences there are between tools so my agents behave the same way across tools.
3.
by chachachainsaw 21d ago
Definitely. Especially since those standards are fairly aligned across lots of tools. The other cool thing is a lot of desktop clients like Claude Cowork and ChatGPT Desktop also speak plugins, so hooking up marketplaces help with further d
4.
by chachachainsaw 24d ago
Most guidance I’ve read, and experienced success with, is keeping a lean agents.md file and building out a tree of docs or skills that an agent can navigate via progressive disclosure.
5.
by chachachainsaw 24d ago
How do you think about using these vs using something like plugins + plugin marketplaces to distribute skills that ship natively in a lot of tools?
6.
by chachachainsaw 24d ago
Have you seen mattpocock’s skills? I know they are hecka popular with people I work with.
7.
by chachachainsaw 24d ago
Tracking skill usage like this is really smart, stealing this!
8.
by chachachainsaw 24d ago
I’ve been keeping all skills in .agents/skills and symlinking .claude/skills, this way I can use them across both claude code and codex. One of the not so straight forward things is knowing what frontmatter overlaps, or subtle con
9.
by chachachainsaw 24d ago
I’m a heavy user of wisprflow for speech to text and prefer html output for richer understanding. Unfortunately I don’t use a text to speech with a CLI, but want to follow this thread because I’m interested in seeing what’s available!
10.
by chachachainsaw 25d ago
100%. Finding the right hook is important though, especially because CC gives you so many. For my setup I use multiple coding agents and so I use frontmatter.news to compare hooks across agents so I get the same behaviour.
11.
by chachachainsaw 29d ago
I mentioned on the main thread, but thought it would be topical here too. Claude Code ships LSP support but only if packaged within a plugin. So there are hoops you have to jump through to get it rather than getting it out of the box. But i
12.
by chachachainsaw 29d ago
Claude Code ships LSP support, but only as part of a plugin. I think they’re currently the only vendor to fully support it.
13.
by chachachainsaw 1mo ago
One of the things I struggled with for a while was diffing the configs between tools when switching over and keeping them all straight. I recently built a free directory I’ve been hacking on to continually diff coding agents docs and source
14.
by chachachainsaw 1mo ago
Came here to say this. Output styles help a lot in cutting down the fluff.
15.
by chachachainsaw 1mo ago
I use a lot of agent hooks to force deterministic guardrails in the moment for faster feedback loops, like someone else mentioned. Others like pre-commit hooks and CI checks are still great for things like enforcing conventional commits, li
16.
by chachachainsaw 1mo ago
Some of the configs are fairly similar, and if you bundle in a plugin they can be distributed without much ceremony. Something you can do for forcing cli migration generation is to write a pretool hook. Here’s an example of shared hooks. h
17.
by chachachainsaw 1mo ago
Nice write-up! I’ve moved a lot of my prose based guardrails into agent supported hooks, pre-commit hooks and CI checks. I’ve found this deterministic back pressure helps coding agents more consistently figure out for themselves when they’r
18.
by chachachainsaw 1mo ago
I’m fully on letting agents write all code, no longer doing autocomplete. I switch between Claude Code and Codex mostly, although found Cursor’s cloud agents a nicer experience.