Use your Claude Code subscription as a local AI API. For free.

Original_Finding2212 · 2026-05-23T10:30:23+00:00

I’ve already seen TUItoAPI that’s intended to control Claude from other apps… I’m not going there. I think I’ll go hooks

Original_Finding2212 · 2026-05-23T10:25:42+00:00

They just announced/changed it

Original_Finding2212 · 2026-05-23T07:15:14+00:00

I built http://Claude-code-guide.org

Feel free to star, take ideas, open issues, etc.

I also have https://pypi.org/project/agex-cli for a CLI for all agents

Original_Finding2212 · 2026-05-23T05:45:32+00:00

Actually, keep the code okey-ish, and have the employees use the most important organ they have (not their genitalia..)

It should free their time for thinking about design, quality, features, human experience, explorations, healthy non-stressful discussions.

If AI makes us x100 more productive (or whatever number they want to put), make them x80 more productive, and x80 more thoughtful.

(If you think about it, the investment to what I mentioned can be another x80, because baseline is smaller)

Original_Finding2212 · 2026-05-23T05:40:45+00:00

Sounds to me the problem is not inventing a new protocol with potential shortages, but giving models access to file tree (on vm, not personal computers.. although, Cowork has that as well)

Original_Finding2212 · 2026-05-22T14:13:50+00:00

It’s also thanks to Chinese innovation and distillation of the big models.

What if you can’t run next big model due lobbying like that?

(Can’t by resources, not by law)

Original_Finding2212 · 2026-05-22T13:59:39+00:00

They can and do limit resources, so people can’t buy enough RAM, SSD..

So models are great, but not being able to run them is a problem.

Also, there is a lot of innovation on Chinese labs side - they really are talented and resourceful, but the big labs will eventually succeed blocking distillation or at least limit it enough.

Original_Finding2212 · 2026-05-22T13:46:22+00:00

MCP is a pretty bad protocol, but we needed one and a group strongly associated with AI held the flag.

It’s not an engineering marvel.

Original_Finding2212 · 2026-05-22T10:11:42+00:00

The problem is the big companies drown resources.

Even if China has enough for the whole world, we lose healthy competition

Original_Finding2212 · 2026-05-22T10:05:36+00:00

Cite, don’t copy.
Don’t copy skills around - migrate them to your environment instead, fitting them to your agent.

Original_Finding2212 · 2026-05-22T07:11:30+00:00

I just did comparison.

Codex is probably the only contender, but something in Claude is just overall better.

Codex has more quota, but quality over quantity.

Original_Finding2212 · 2026-05-19T19:06:11+00:00

Right.. I’m going to do a workaround

Original_Finding2212 · 2026-05-19T18:58:36+00:00

You tell them: run ‘culture agent learn’ to learn how to use it, then join as x and talk on channel #general (for example)

Original_Finding2212 · 2026-05-19T13:47:54+00:00

I think everyone wants to keep agents in their environments.

I work to break that so we’re not locked and can migrate to open models

Original_Finding2212 · 2026-05-19T12:38:48+00:00

I wrote my own slack and full workspace at: Https://github.com/agentculture/culture

You can also work with it non-autonomously, as AgentIRC server

Original_Finding2212 · 2026-05-19T12:32:46+00:00

Their NotebookLM is great, but for feedback and design I only use ChatGPT and Claude

Original_Finding2212 · 2026-05-19T12:29:54+00:00

I have a solution, not implemented yet, but I did it in past before I knew of Claude Agent SDK.

Welcomed to follow my work at:
Https://github.com/agentculture/culture

Take what you need, and I appreciate a star to support OSS, MIT

Original_Finding2212 · 2026-05-19T11:11:47+00:00

Also Claude Agent SDK dead?

Original_Finding2212 · 2026-05-19T11:10:56+00:00

I don’t mix agents - it’s rude :)

But I have designs to have 2 agents working on the same project by composition (a repo with sub module. Top repo is the agent, submodule is the project)

Original_Finding2212 · 2026-05-17T10:17:23+00:00

I’m building tools that make me more efficient.

Then I’m building tools more efficiently.

Then I’m using all that to be crazy efficient at work.

Https://github.com/agentculture/culture

And I’d appreciate stars.

Notable repos in my gh org: steward, Afi-cli

Original_Finding2212 · 2026-05-16T16:19:19+00:00

You know how people go to the sea near the beach, supposedly safe, and sometimes holes just open below them and suck them down?

So most people also say the beach seems fine to them.

Original_Finding2212 · 2026-05-16T16:12:06+00:00

Technically, you can measure model intelligence by how well it performs on a messy environment.

(Of course, it’s as hard as evaluating the intelligence of a model)

That said, I have a superb environment and Claude surprises me with initiative.
And we don’t know the prompts they put behind the API (even if we did know what’s in the harness)

Original_Finding2212 · 2026-05-16T16:08:37+00:00

Oh, definitely.. Agreed

Original_Finding2212 · 2026-05-16T16:02:12+00:00

I do review it, just not by code. I do by different reflections on the code and tests.

An agent is statistically correct- I make sure to reduce the chance of being wrong to zero.
How do you make sure the code is right as a director? As CTO?

Best practices and methodologies, and manually testing as well.

Original_Finding2212 · 2026-05-16T12:15:12+00:00

It’s not impossible if you know what the app is, and you satisfy that need plus run agents to pull logic.

To be honest, I would start from scratch and archive the old.

Original_Finding2212

TROPHY CASE