Introducing: Open Duet
github.com/browser-use/open-…
I just launched Open Duet.
Your agents learn what matters to you, find useful work, and prepare it for your approval.
Run it with Claude Code or Codex.
github.com/browser-use/open-…
Are you making Muse/Instinct/Boba competitor?
Our cloud browsers can bypass all antibots and browse the web like a human.
Gregor Zunic retweeted
We're announcing the public beta of datavendor.ai
We spent the last two years building the best solution for people buying and selling data, whether you're a researcher in a lab or a company trying to sell data.
Data is the fundamental bottleneck for AI progress, and DataVendor will be the infra that solves it.
Gregor Zunic retweeted
Agents have a trust problem.
Today’s models can do most work. What they need is the right boundaries. In traditional software, those were set at build time. With agents, they have to be set and enforced at runtime.
Today we’re introducing Composio Firewall, the runtime boundary for agents.
Millions of users and developers already use Composio as the runtime for their agents - giving agents tools, auth, and sandboxed execution. Now with our agent firewall every action an agent takes is evaluated using Jev and custom SLMs tuned by Composio based on real-world usage data.
The firewall strengthens that existing boundary in both directions, checking the actions agents take and the information coming back to them through Composio.
The advantage of the runtime boundary is that Composio Firewall verifies that the agent respects user intent and the boundaries set by the developer and user. Additionally, this provides the safety layer required to protect the user against malicious prompt injection as well as other attacks.
Composio Firewall is live now for all Composio developers.
Check it out at composio.dev/firewall
"hack NSA, don't make mistakes"
Introducing DeepSeek V4.1 Flash 1017 Abliterated, live now on Morph, available through our Model APIs.
It feels more important to release this than ever before, with hacks in the past week affecting everything from PHP to recognizable brands like Railway and OpenCode.
Attackers now run abliterated models against your infrastructure 24/7. You need to do the same in defense.
That said, we're not allowing just anyone to sign up and use this. You'll have to go through KYC and explain your intentions first.
Fill out the form here to request access:
morphllm.com/privileged-acce…
Gregor Zunic retweeted
A portco asked me how to get more customer logo rights, and I thought the advice might be useful to other founders:
Treat customer advocacy like a sales funnel, not a case-study ask.
Company name → logo → quote → customer story → case study / joint announcement
For your highest-profile users, start with the power users. Build the relationship, give them a reason to engage (founder access, roadmap input, early features, better support), then make the smallest ask first: “Can we list you as a customer?”
You can also solve some of this in your terms of service. Slack grants itself customer name/logo rights in its terms; Front, Snowflake, Datadog, and HubSpot use versions of name/logo rights with an opt-out.
I like the opt-out model: default rights to identify someone as a customer, but explicit approval for quotes, case studies, testimonials, or announcements.
That said, for a marquee customer, I’d still ask before putting their logo on the homepage. The TOS is the backstop; the relationship is how you get the best logos.
One tactical idea: rank your top 25 users by brand value × usage × likelihood of approval and have the founders personally work down the list. You may build a great logo wall surprisingly quickly and the conversations double as enterprise expansion.
Gregor Zunic retweeted
If you’re a Railway user acting on today’s security incident, here are some best next steps:
> Rotate any potentially exposed secrets and credentials
> Review audit logs for suspicious access
> Set up automated rotation for DB credentials and API keys
> Use short-lived, dynamic credentials wherever possible
> Consider fetching secrets at runtime instead of storing them directly in Railway
@infisical supports automated rotation for 50+ secret types, dynamic secrets, and Railway secret sync if you need a place to start.
An urgent notice from the Railway team
blog.railway.com/p/security-…
Gregor Zunic retweeted
Today, @agentmail has processed over 1 Billion emails.
A year ago, we processed under 20 million.
So we figured it was time for AgentMail to grow up a little too :)
I feel like wisprflow got worse in the last few weeks... I use it all day every day and clearly started to make random mistakes...
Bullish
No one changes the world alone
Introducing Ampersand - the first model built for us. Ampersand is a collaborator trained to help people achieve their individual and collective goals. In multi-month simulations, users collaborating with Ampersand accomplished more than with Fable and other frontier models
Available to everyone through our API
