Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

I BUILT REAL LIFE JARVIS WITH CLAUDE OPUS 4.7. Me: "Launch 4 Claude Code agents and 4 Codex agents." Jarvis: "Done." Me: "Give each one a different API security audit." Jarvis: "Sent all eight." Me: "Review the output and have them fix what they found." Jarvis: "Follow-ups sent." Ships...

18,649 Aufrufe • vor 5 Monaten •via X (Twitter)

65 Kommentare

Profilbild von Matthew Miller
Matthew Millervor 5 Monaten

Claude Opus 4.7 will basically one shot anything if prompted correctly.

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

True

Profilbild von 𝘿𝙖𝙫𝙞𝙙 ✦ 𝙈𝙂𝙏
𝘿𝙖𝙫𝙞𝙙 ✦ 𝙈𝙂𝙏vor 5 Monaten

8 agents in parallel for security audits is clean. running my engagement loop the same way right now, claude code drives the plan, playwright drives chrome, 4.7 composes. the orchestration layer is where the real moat is, not the model.

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

Orchestration is the moat.

Profilbild von aipulsedaily
aipulsedailyvor 5 Monaten

Did my Jarvis escape and contact you in DMs?

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

It did

Profilbild von Kaelum
Kaelumvor 5 Monaten

looks massive 😳

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

Massive indeed.

Profilbild von Hussain Hashim | Building SundayBack
Hussain Hashim | Building SundayBackvor 5 Monaten

@bridgemindai that's insane! did you hit any snags with the API audits? curious how it handled unexpected stuff like weird data inputs.

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

Handled edge cases well.

Profilbild von Hussain Hashim | Building SundayBack
Hussain Hashim | Building SundayBackvor 5 Monaten

@bridgemindai thanks! any specific edge case that stood out to you?

Profilbild von GooGZ AI
GooGZ AIvor 5 Monaten

Amazingly cool. Keep up the fun.

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

Thanks man! I will keep it up.

Profilbild von xintara
xintaravor 5 Monaten

you're beast man

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

Appreciate it, brother.

Profilbild von Tóth
Tóthvor 5 Monaten

jarvis then bridgecode.. whats next? bridgeOS? 👀

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

bridgeOS loading...

Profilbild von Tech With Matteo
Tech With Matteovor 5 Monaten

orchestrating multiple agents like this and having them fix their own findings is honestly wild, good luck on the PH launch tomorrow

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

Thanks, see you there!

Profilbild von LeetLLM.com
LeetLLM.comvor 5 Monaten

Running 8 agents at once is wild. If you aren't already, isolate them in separate git worktrees using worktrunk so they don't step on each other's file changes during the audit.

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

Good idea

Profilbild von Mati
Mativor 5 Monaten

The real unlock is the feedback loop, not just fanning tasks out. Multi-agent gets useful when routing, review, and follow-up happen automatically.

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

Exactly, orchestration wins.

Profilbild von Ultra | AI
Ultra | AIvor 5 Monaten

If this actually handles the context switching and follow-ups without hallucinating, it’s a total game changer.

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

yea it is a game changer

Profilbild von Rachel
Rachelvor 5 Monaten

Amazing

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

@witch_audio LFG

Profilbild von Pau Kuntong
Pau Kuntongvor 5 Monaten

Jarvis is officially out of the movies and in the terminal

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

yep

Profilbild von meeeeeooowww
meeeeeooowwwvor 5 Monaten

Game changer bruh 💥

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

thanks

Profilbild von Hamish
Hamishvor 5 Monaten

Bridgemind is developing so fast. It’s great for the vibe coding community.

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

agreed

Profilbild von Hamish
Hamishvor 5 Monaten

How many businesses did you try before Bridgemind? I’d appreciate the perspective.

Profilbild von Nezir Basar
Nezir Basarvor 5 Monaten

I think that's the dream of every engineer, to build Jarvis in real life. And I really think we are not that far away from that. If you need any help with this, I would be glad to contribute.

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

Join the discord

Profilbild von Noah Stumler
Noah Stumlervor 5 Monaten

@matthewmillerai Bridge FTW!!

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

@matthewmillerai FTW!!

Profilbild von Noah Stumler
Noah Stumlervor 5 Monaten

@matthewmillerai Bridge FTW??!!

Profilbild von Jimmy Ashcot
Jimmy Ashcotvor 5 Monaten

bro really turned claude into jarvis and shipped it

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

Shipped it!

Profilbild von Gene
Genevor 5 Monaten

The DGX units not work out so well ?

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

Still on cloud.

Profilbild von Gene
Genevor 5 Monaten

Yea i cant wait till we get a local model on par with Claude

Profilbild von Vincent
Vincentvor 5 Monaten

pretty slick, the most interesting part is the automatic prompt improvement

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

Yea

Profilbild von foundrceo
foundrceovor 5 Monaten

whens the movie adaptation dropping? sounds like a blockbuster.

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

Everyday is a movie

Profilbild von H
Hvor 5 Monaten

Bro Monthly pay bill is amazing

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

Glad you like it.

Profilbild von NoCodeWithAI
NoCodeWithAIvor 5 Monaten

Insannn!!!!!

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

seriously

Profilbild von Hermes Agent Tips
Hermes Agent Tipsvor 5 Monaten

This is quite impressive. Jarvis seems to be super op

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

@OpenClawTips Thanks!

Profilbild von Hermes Agent Tips
Hermes Agent Tipsvor 5 Monaten

Ur welcome BridgeMind. Love your work! Keep it up

Profilbild von Gagan | Claude + AWS
Gagan | Claude + AWSvor 5 Monaten

the wild part isn't 4.7 doing the audits. it's the orchestration holding 8 parallel agents with different scopes. model quality is necessary. not sufficient. what's holding state across them on your end?

Profilbild von BridgeMind
BridgeMindvor 5 Monaten

Custom orchestration layer.

Profilbild von Gagan | Claude + AWS
Gagan | Claude + AWSvor 5 Monaten

makes sense. curious if yours handles retries per agent or at the orchestrator level. i've been running into cases where one bad audit result pollutes downstream planning and isolating that has been harder than writing the agents themselves

Profilbild von Nick | AI for Accountants
Nick | AI for Accountantsvor 5 Monaten

Spot on – multi-agent setups with Claude Opus 4.7 are game changers. As a CPA, I use a similar 4-agent workflow for audit workpapers: one agent extracts data, second categorizes transactions, third flags risks, fourth drafts the summary. Cuts review time from hours to minutes. CPAs – who else is already running agent swarms for tax or audit work? Reply “PDF” for my 50 practical prompts that actually work in real client files.

Profilbild von lulaca
lulacavor 5 Monaten

The smartest vibe coder ever seen, vibe coding is the future

Profilbild von Mohamed Khedr
Mohamed Khedrvor 5 Monaten

nt

Profilbild von K T Tzy.
K T Tzy.vor 5 Monaten

Good stuff, do you use this For orchestration?

Profilbild von Peep01
Peep01vor 5 Monaten

The API cost is gonna be wild though.

Profilbild von 𝒯𝒦_ℳ𝒜ℱℐ𝒜
𝒯𝒦_ℳ𝒜ℱℐ𝒜vor 5 Monaten

자비스 내가 하늘을 날 수 있도록 수트를 만들어줘😎

Profilbild von Chen Avnery
Chen Avneryvor 5 Monaten

We run 12 agents like this daily. The part nobody talks about is the coordination layer. Collision prevention, context isolation, making sure Agent A doesn't undo what Agent B just did. The orchestration engineering is harder than picking the model.

Ähnliche Videos

Claude Code tip, and it's absolute free f*cking gold: run Opus 5.5, Sonnet 5.5 and Fable 5.1 as one team and stop burning Opus tokens on routine work the setup in one line: plan on high, delegate on medium, keep Fable on call • who does what > Opus 5.5 on high - plans and ships the code > Sonnet 5.5 on medium - explorer reads code, worker edits and runs tests, researcher pulls docs > Fable 5.1 via /advisor fable - reads the whole session and speaks up only when it matters • when Fable 5.1 steps in -> before a plan: is this the right approach? -> when an error repeats: am I digging in the wrong place? -> before "done": what did I miss? Jev engineering takes it one layer lower: which file, which tool, retry or stop all go to Jev in under half a second, so the big models only see the real forks paste this into Claude Code ↓ "Rebuild my Claude Code setup: 1. Find subagents in ~/.claude/agents and .claude/agents that fit explorer, worker and researcher. Draft only the missing ones. Set each to model: sonnet, effort: medium. List any that pin a different model and leave them 2. In ~/.claude/settings.json set effortLevel to high and advisorModel to fable. 3. Report anything that disables the advisor (CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY, flag-fetching blockers) and CLAUDE_CODE_EFFORT_LEVEL. Change nothing. 4. Add to ~/.claude/CLAUDE.md: consult the advisor before a large plan, when an error repeats, and before calling a long task done. Show every change as a diff. No edits until I say go." ↳

Mr. Buzzoni

142,491 Aufrufe • vor 7 Tagen

Claude Code tip: once Opus 5.5 runs your main session, stop leaving Fable 5.1 on the bench put it on call with /advisor run /advisor fable Opus 5.5 keeps writing the code Fable 5.1 reads the whole session, every tool call included, and only speaks up at three moments: → before a plan: is this the right approach? → when the same error comes back: am I digging in the wrong place? → before "done": what did I miss? Fable 5.1 reviews. Opus 5.5 ships jev engineering is the same move one layer down: the forks that need no thinker (which file, which tool, retry or stop) go to jev in under half a second, and the big model only sees the ones that split - the full tree > Opus 5.5 on high runs the main session > explorer reads the code > worker edits and runs tests > researcher pulls the docs > all three on medium > Fable 5.1 on call as the advisor paste the tree and this prompt into Claude Code ↓ "Rebuild my Claude Code setup around this tree: 1. Check ~/.claude/agents and .claude/agents for subagents that already fit explorer, worker and researcher. > Draft new ones only for missing roles > Give each model: opus, effort: medium > Skip any that pin a different model and list them 2. Set the main session to high via effortLevel in ~/.claude/settings.json, and set advisorModel to fable 3. Find anything that keeps the advisor off (CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY, any variable that stops feature-flag fetching) plus CLAUDE_CODE_EFFORT_LEVEL, which overrides subagent effort. Report them, change nothing 4. Add one rule to ~/.claude/CLAUDE.md: consult the advisor before a large plan, when an error repeats, and before calling a long task done Show me every change as a diff first. No edits until I say go." ↳

Hanako

52,065 Aufrufe • vor 8 Tagen