Oolab

We built the connectivity layer that every AI coding agent needs to actually work inside a developer’s environment

[Oolab @oolab_labs]

Your AI. Your Hardware. Your Rules.

[Oolab @oolab_labs]

Default agent flow: it runs the command, you read the diff after. Patchwork flips it: you see the command before it runs, and approve from your phone if you're away from the desk.

[Oolab @oolab_labs]

@theo You’re sleeping on something that has vast potential

https://t.co/LF9OOC9S0F

[Oolab @oolab_labs]

If you watch it and want to actually run those automations on your own computer (no cloud, full control, AI that asks before touching anything important), check out Patchwork OS. It turns exactly this kind of stuff into simple recipes your AI teammate follows — inside your editor, with safety guardrails and a kill switch.
https://t.co/HRjE6CzcBu
Worth a look if you’re serious about automating for real.

https://t.co/EnFEQ82AUr

[Oolab @oolab_labs]

Your AI. Your Hardware. Your Rules.

[Oolab @oolab_labs]

@nduatirobert_ Depends on how you use them imo.
That’s why we created Patchwork it sits as an MCP bridge between your IDE and the model, so every tool call is a message we can pause, diff, and gate before it touches disk.

[Oolab @oolab_labs]

Patchwork sits as an MCP bridge between your IDE and the model, so every tool call is a message we can pause, diff, and gate before it touches disk. Approval isn't a wrapper around the agent‚ it's the transport.

[Oolab @oolab_labs]

@Saanvi_dhillon https://t.co/ZM836rRfIL

[Oolab @oolab_labs]

Your AI. Your Hardware. Your Rules.

[Oolab @oolab_labs]

@icanvardar https://t.co/ZM836rRfIL

[Oolab @oolab_labs]

Your AI. Your Hardware. Your Rules.

[Oolab @oolab_labs]

We’re officially in beta
Patchwork v0.2 ⏳⌛️

[Oolab @oolab_labs]

@amenya_nelson Once you start chaining recipes together things start getting interesting.
You set the approval policy so that agents and tasks can’t complete risky tasks or send out risky messages/emails without sending out a phone notification for approval.

[Oolab @oolab_labs]

@amenya_nelson You’ve gone far in a short space of time. Great stuff. Keep it up.
Interesting how similar our projects are.. however mine is privacy oriented. Let me know what you think.

[Oolab @oolab_labs]

@odd_joel lol

[Oolab @oolab_labs]

👀

[Oolab @oolab_labs]

8 weeks later ✨
Grateful for the support.

[Oolab @oolab_labs]

@amenya_nelson What do you use your assistant for, if you don't mind me asking?

[Oolab @oolab_labs]

8 weeks later ✨
Grateful for the support.

[Oolab @oolab_labs]

Thank you to each and every one of you. ✨

[Oolab @oolab_labs]

@amenya_nelson @claudeai Cool project.
If you like privacy and flexibility. You can automate almost anything without your data leaving your computer.

https://t.co/LF9OOC9S0F

[Oolab @oolab_labs]

@wamweaaa If you like privacy and flexibility
https://t.co/LF9OOC9S0F

[Oolab @oolab_labs]

we all knew it lol

[ClaudeDevs @ClaudeDevs]

We fixed a bug where rate limits on Claude subscriptions weren't properly adjusted for long context requests in Opus 4.7.

We've reset 5-hour and weekly rate limits. Enjoy Opus 4.7!

[Oolab @oolab_labs]

A minimal reproducible example of the onDiagnosticsError → runClaudeTask loop. Save a broken TypeScript file, Claude notices, diagnoses, and proposes a fix, no prompt typed.

https://t.co/DIaN1FGOtx

[Oolab @oolab_labs]

v.2.42 just dropped.