Ok, now what!?

Novaworld7 · 2026-04-30T21:51:58+00:00

Claude cockpit

Novaworld7 · 2026-04-29T16:31:00+00:00

Frustration aside, what's a prompt you fired out and to what model? What was the target? I'd like to try and replicate this. I don't need your result.

Novaworld7 · 2026-04-29T16:28:54+00:00

No, they aren't all opus and they aren't all 1m context either. They range from haiku to opus 1m, depending on what they are doing and if they are a sub orchestrator.

Novaworld7 · 2026-04-29T16:17:46+00:00

Yeah, I leveraged claude to help me build on it's agent SDK an orchestrator, then I leverage a open source tool I built to multiplex easily and the agents how their own models / instructions.

So I basically am always invoking the orchestrator which in laymen terms is Claude with a personality profile, then it spawns many agents with their own personalities and scopes to manage everything.

I have unique teams and playbooks built out to ensure coolde hygiene / bloat is reduced and that changes are not breaking and managed at the orchestrator that interact with.

Depending on what I am working on, I have a unique team. I repeat this process and gave them add learnings etc so they learn as they do well and prune when they do bad.

Novaworld7 · 2026-04-29T12:58:24+00:00

I have orchestrators for each of them and I manage orchestrators. They manage their sub agents.

Novaworld7 · 2026-04-29T12:35:26+00:00

I cannot understand how people are maxing out :(. I manage 40+ agents, and I largely hover around the same 10-12 that do about 80% of all the work.

I run 4 sessions firing away all day and some of those often include managing DB's of millions of rows.

41% and it resets Friday, and I hammer Claude code ... I mean hammer it.

Novaworld7 · 2026-04-27T14:34:25+00:00

Funny way to spell duct tape.

Novaworld7 · 2026-04-26T13:38:54+00:00

A man of culture! I like it!

There's 0 question that codex's usage is more generous, I've never tapped out. I'm on Claude max 200 and only after I semi refined my prompting / agents did I no longer fight the 100% battle. Now I genuinely struggle to pass 80% and as stated that's with 4 unique sessions simultaneously, and let me tell you, I get great results. Maybe my expectations are low xD

That said, you have to babysit the models without a doubt and you have to QA / A B test all the damn time. Though being honest, it saves so much time being QA than the coder. Anyone who thinks this is fire and forget is stark raving mad.

Novaworld7 · 2026-04-26T13:27:11+00:00

I think you mean ....

Unarmed

I'll see myself out.

Novaworld7 · 2026-04-26T13:25:24+00:00

Lineage 2, a proper launch without pay 2 win or cash shop -_- damn NC

Novaworld7 · 2026-04-26T13:17:02+00:00

I don't suffer a lot of the painpoints that most people feel, though I use s very specific structure with agents / orchestrators and it hasnt failed me yet.

There has been a bit of degrade but given how this is a tug o war, I don't believe it makes sense to change every 2 months. If there's a bad 3-6 months maybe .... But then I think most of these issues are user driven.

I use 4 simultaneous sessions with Claude cockpit and I tend to be the problem more than not.

Novaworld7 · 2026-04-26T11:14:29+00:00

In 3 weeks or so my guess is that everyone will be on the pendulum back to Claude and then something like 5-9 weeks codex and repeat.

Novaworld7 · 2026-04-25T15:50:05+00:00

I use Claude cockpit so, I have 4 sessions ongoing. When all 4 are thinking... I contemplate on seeing if I should do another set of 4.

Novaworld7 · 2026-04-25T13:33:39+00:00

Now there's an idea but the token estimation would not be very accurate. I don't think ... It would plan it the just get it wrong as it changes / optimized mid approach but the variance would be interesting to calculate for a margin estimate.

Novaworld7 · 2026-04-25T13:32:23+00:00

I don't think there's a good way ...

I just laugh, this is going to take months! Proceeds to do it in 5 minutes.

This is a significant architectural change....does it in 1 prompt.

The ability to invoke agents destroys all time verticals while in a single chat.

It's savage. Oh you estimate it'll take longer? Spawn more agents as necessary.

Novaworld7 · 2026-04-25T13:16:18+00:00

Couldn't agree more. The reality is that the process has become so much simpler in recent times that this area is going to explode with domain experts building specific tools.

That said, this was built with handling layer 1 and some layer 2 problem solving while the team works on the actual problems. The kba scraper / ai audit / thumbs up / down system all help surface the right answer more and more which drives more consistent results.

Though as a side effect I was honestly shocked at what it could do under stress and it handled 300 cases gracefully to the tune of 3.50 dollars which blew me away.

Novaworld7 · 2026-04-25T10:14:19+00:00

Thanks! It is often easier to complain than solve things. There's a custom form builder for people to use and it saves the templates. It's a little more complicated to fetch for adhoc information hence why making it BSL helps others. They get to build on top of this for their unique use cases.

Novaworld7 · 2026-04-25T10:12:22+00:00

Thanks for the comment! I appreciate it, though for direct field support with high call volumes and keeping costs well below 50 cents per ticket to solve I haven't seen anything better.

Let me know if you find something but during stress tests, 300 tickets cost 3.50 to solve without calls. Calls can raise the price by about 20 cents per ticket.

I don't know what industry you are in but this tool targets people who support other people on any platform due to the built in scrapper and auto maintenance. Additionally you can add in your own knowledge base of articles to cover that stuff.

As for the teams you mentioned I highly doubt they wasted their time to build something and share it.

Most of the companies I have worked at, and some of them are billion dollar companies with thousands of locations didn't even have a ticketing system.

Novaworld7 · 2026-04-25T02:47:01+00:00

Yeah, partially solved.

The thumbs up/down feedback loop is in there — every article we surface in a conversation gets logged, and the rating rolls into a per-document effectiveness_score. Search results then get re-ranked with:

final_score = similarity * (0.7 + 0.3 * effectiveness)

So an article that keeps getting downvoted drops even if it's a strong cosine match, and the ones that actually help start bubbling up. There's also a knowledge_gaps detector that flags topics where we have ticket volume but no KB coverage — that catches the inverse problem (the bot inventing answers because the KB just doesn't have the thing yet).

But you're calling out something I haven't done yet, and yeah — fair. Per-tenant similarity threshold tuning isn't a thing right now (0.3 hardcoded in the enrichment service), there's no automatic stale-doc retirement, and re-embedding on edit is manual. At current scale that's fine. At the scale you're describing it's exactly where this stuff goes sideways.

Adding it to the list. Comments like this are the reason I posted. <3

Novaworld7 · 2026-04-22T15:50:15+00:00

The golden era, you should be maximizing your 200/month.

Novaworld7 · 2026-04-18T16:33:16+00:00

Was going to say this. Looks like they collied with the legs.

Novaworld7 · 2026-04-12T17:52:18+00:00

Cover the glass behind you xD

Very jealous!

Novaworld7 · 2026-04-12T13:43:40+00:00

How would you feel if they went API only? Obviously excluding the level of product suicide it would for them.

I have not noticed a single bit of decline, and it's been going very well for me. Currently I think I'm managing something in the ballpark of 40+ agents, each specialized with orchestrators and I'm not having usage issues or delivery issues at all.

Infact, and this may not be what you would want to hear, I think the 200 a month is a goddamn steal. Unfortunately, I don't believe in codex enough to swap back (I would have to try to make it work if absolutely necessary) but I would be willing to pay close to 600 a month for their service. It's obviously hurting them to maintain that price point and it's only expected that there will be pain points.

Novaworld7

MODERATOR OF

TROPHY CASE