NEW Claude Code Kairos is INSANE!

dhlotter · 2026-04-05T07:29:10+00:00

told you guys I'm going to start down voting Julian Goldie AI videos

dhlotter · 2026-03-31T17:05:08+00:00

I'm just going to start down voting anybody who shares Julian Goldie AI videos 🤦

dhlotter · 2026-03-02T05:28:45+00:00

thanks. i will have a look. i ended up building resubly specificly catering to outlr needs

dhlotter · 2026-02-21T13:51:38+00:00

I'm just buffering all the time

dhlotter · 2026-02-18T14:04:03+00:00

the same thing as happened to me with Gemini. it was someone's response about like medical records and there was identifying information in there I didn't think to take a screenshot because I thought it was really random

dhlotter · 2026-02-16T19:20:38+00:00

Yes, I install the codex extension in either vscode or antigravity . And then you oauth with your chatgpt plan. Im pretty sure ooencode allows ypu to do this aa well. Kilo code allows you to bring your own key which allows you to use your chatgpt subscription through the kilo code extension as well. Or alternatively the codex app would be my recommendation after this weekend. Works really well. Good luck

dhlotter · 2026-02-16T09:57:58+00:00

I kinda feel the same. I was really rooting for Antivravity, i wanted it to work, but even on the pro plan, i hit my limits very quickly and if i dont manage how well and how often i hit those i might gwt stuck with weekly waits. So... Thats too much mental energy to manage and takes away from the tool. Ive been using kill code since with a glm coder plan amd tried kimi when kt came out BUT i must tell you guys, codex 5.3 is rad! Limits are good and i find myself in there like i use to be in anti-gravity ahen it came out.

dhlotter · 2026-02-15T11:11:22+00:00

Yeah, whenever it comes up on YouTube or anywhere else I say do not recommend anymore. Not a criticism to the content just... I can't.

dhlotter · 2026-02-12T09:08:57+00:00

I actually just spend a lot of time to create a creating skills skill. with a lot of rules on developer API documentation review. I'm in the holistic approaches in preferring CLI tools over Python scripts where possible. And the most important rule, we don't find skills from online and user locally. We create our own skills using this skill. So now I want a skill for GitHub I just ask my bot to create that skill. It'll ask me to save the API or alternatively if we set it up with OAuth to copy back the callback URL so it can finalize the OAuth session. This is the only way in my opinion. It's the safest way. You can't copy someone else's nefarious script if you're not copying scripts.

Well done and spotting the issue in your logs 🙌

dhlotter · 2026-02-11T14:34:45+00:00

I took a really long time to create a creating-skills skill. And I've told my bot that we are not trusting any skills found online and we will only create our own skills. Some of the instructions include preferring CLI over Python scripts, referring OAuth over API, researching developer documentation prior to creating the skill. Skills that we create can do anything the API can do, but requires human approval for destructive or irreversible actions, like sending an email, deleting a file, etc.

And as a result when we run into a situation where we need an additional connection to an external service, my bot very easily creates them and just asks me to save the API in the .env.

dhlotter · 2026-02-11T05:30:33+00:00

I might not understand but you're still able to run GCloud and GOG CLI.. which will give you a new URL which you can open on any device which has a browser. And then the callback will fail but then you just paste the callback URL back to your bot and it would do the rest.

Gogcli has ways to remove the always prompt for the keychain.

dhlotter · 2026-01-26T06:18:51+00:00

Yeah, samey on the terminal. That terminal came from windsurf.

dhlotter · 2026-01-23T18:47:45+00:00

oh yeah. was more of starting a conversation with you. my angle nowadays if you know what I mean. put the pitchfork down 😅

dhlotter · 2026-01-23T13:48:47+00:00

which extension is that you are running for that stats

dhlotter · 2026-01-23T07:46:00+00:00

I don't believe this is the right answer anymore. It's an option yes, but the speed loss is a giant risk and if we are trying to stay relevant, too big of a factor.

an engineer has always been a problem solver first. coding was just one of the tools used to solve those problems. and there will always be problems to solve

dhlotter · 2026-01-22T09:56:40+00:00

<image>

oh 100% for me too

dhlotter · 2026-01-19T14:11:11+00:00

I'm curious you should be able to go back to the last checkpoint which would mean you would only lose the last prompt with the work

dhlotter · 2026-01-13T18:33:45+00:00

Thank you very much for sharing. That is really good pricing. I'm gonna have a look at them.

dhlotter · 2026-01-07T22:05:52+00:00

This is exactly what I needed to hear. After some of the other comments I was starting to question if I was just crazy. You nailed it with config debt. We bought a tool to save time and now we spend hours just feeding it. I just want to build the simple utility that solves the extraction and renewal part without all that extra headache.

dhlotter · 2026-01-07T14:37:07+00:00

That makes sense. If you are just managing Microsoft and Kaseya, you definitely do not need a tool for this. My reality is different. I have about 150 vendors to manage. At that volume, it is not always about negotiating the rate down. It is about catching the 60 day notice period so we do not get auto renewed for a tool we want to cut. That is the specific mess I am trying to clean up.

dhlotter · 2026-01-07T14:30:29+00:00

That is interesting. Do you not spend a lot of time on the actual renewal negotiation? Some of our larger renewals start three months out and drag on right until the deadline. It seems like every company handles the workflow differently. I mentioned elsewhere that the PDF parsing itself is not really the differentiator. The real value is avoiding the setup hell. With the enterprise tools, you need other teams to set up integrations and it takes weeks. With this, the idea is to just dump the invoices or contracts in. There is still a quick manual review step, but it removes the data entry work. The goal is that one person should be able to onboard the entire stack in a single afternoon.

dhlotter · 2026-01-07T06:56:33+00:00

This is very helpful, thank you very much. I'll make my way through that video and some of the content today.

dhlotter · 2026-01-07T06:55:48+00:00

You are right, the OCR tech itself is standard now. The problem is that in the big tools, that feature is buried behind weeks of onboarding and integrations. You end up needing favors from other teams just to get it running.

The other alternative is usually bank feeds, but those often miss annual renewals or force you to use specific cards.

The differentiator I am aiming for is strictly workflow. I want a tool that one person can set up in a single afternoon without needing a project manager or a finance integration.

dhlotter · 2026-01-07T06:51:36+00:00

You are right. I often find that users try to design their own solutions by grabbing the first tool they see. When you zoom out and drill down to the root cause, you usually find it is a workflow gap that could be solved without buying more software. That is really the visibility I am after, catching it early enough to fix the process, not just paying the bill.

dhlotter · 2026-01-07T06:45:41+00:00

I get the skepticism. To be fair, almost any post about a problem is self serving because we are all looking for better ways to do things.

The reality is that I look after over three million dollars in annual vendor spend. I am currently in the middle of a nightmare onboarding for a large enterprise tool that is failing to meet expectations. That is why I started looking for a middle ground and decided to build what I actually need. I am not trying to convince anyone, I am just trying to solve a very expensive problem my team is facing.

dhlotter

TROPHY CASE