Samuel Stroschein

Opened a PR to speed up CSV imports in Agent CRM by @enrique_goudet. The test fixture imported in 1.3 seconds instead of 64 seconds (≈47x faster) github.com/cluster-softwa…

@larsencc ``` npm install -g @agent-crm/cli ``` then run `acrm init` and launch claude code! :)

@samuelstroschei how can I best use this?

give me one underrated CLI tool. i'll wait.

Claude can write your emails, debug your code, and analyze your docs. But ask it to run your sales CRM? It chokes. Here's what happens when you try to give Claude access to your CRM today: ↳ MCPs burn your context window in minutes ↳ Every single action = one network round-trip ↳ You blow through usage limits before lunch ↳ Claude ends up confused. You end up frustrated. Existing CRMs weren't built for AI. They were built for humans clicking buttons. Not anymore. Meet 𝗔𝗴𝗲𝗻𝘁 𝗖𝗥𝗠 — the first headless CRM built specifically for Claude Code. Here's what changes: ➟ No UI. No bloat. Just a CLI that Claude talks to directly ➟ Every action is lightweight. Context window stays happy ➟ Claude finally has a source of truth it can actually work with ➟ Scriptable. Fast. Designed for agents, not thumb-scrolling Think of it this way: ↳ Old way: You ask Claude → Claude pretends to know → You update the CRM manually → Repeat ↳ New way: Claude owns the workflow. Updates, logs, follow-ups — all automated. This turns Claude from a chat toy into your best sales rep: ✓ Let Claude qualify leads and log every conversation ✓ Let it schedule follow-ups without your permission ✓ Let it run your entire sales engine while you sleep 👉 Launching today. Headless CRM for Claude Code. 📌 Try 𝗔𝗴𝗲𝗻𝘁 𝗖𝗥𝗠 → lnkd.in/g_mwfBXH 𝗔𝗴𝗲𝗻𝘁 𝗖𝗥𝗠 is live on ProductHunt right now: producthunt.com/products/agent… 🔄 Repost for every founder who's tired of being Claude's human CRM. — #Claude #AI #CRM #Anthropic #AgentCRM

@mernit @supabase does the filesystem have version control?

Introducing Capsule — The Infra Framework for AI Apps Capsule is a Python framework that provides infrastructure primitives for sandboxes, auth, session management, integrations, and payments. Capsule is @supabase for AI apps. You get a powerful Python SDK to iterate fast, and one command to deploy to the cloud. Using Capsule feels like using @beam_cloud or @modal. You don’t need to set up any infrastructure. There’s no Docker, just Python. The feedback loop is super fast. You deploy to the cloud with one command. At Beam, we have a bird’s-eye view into the AI apps people are building. Over the past year, we've watched people build the same 5-7 infra primitives over and over again. Capsule provides all of those primitives using a single SDK. @llom2600 originally built Capsule to prototype our own AI apps. We started selling some of these apps for real money and realized every app needs this, not just ours. Give it a try! Curious to hear what people think. Do AI apps have their Supabase yet?

@enrique_goudet had a similar observation with a markdown app i built. headless = yes. but as a human i want a ui to see what claude did. acrm getting a ui makes sense!

Introducing the Agent CRM app After using the agent crm cli in claude code, it was clear that you still need a snappy interface where you can validate claude's work and dig into the data This feels like the right surface. A place where humans + agents can collab on gtm p.s. built with @emdashsh

Thanks to @enrique_goudet for feedback on this and the important sentence "Claude is the user of lix"

@claudeai is becoming the main interface for version control. As a consequence, the next release of lix will rename "versions" to "branches" to make lix more intuitive for Claude. As a refresher, Lix targeted non-developers as (end) users. Explaining what a "branch" is to non-developers always ends up a long the lines of: > A branch is like a separate version for parallel work. > You can compare (diff) versions and later merge them again. It's like > separate documents e.g. v1.docx and v2_final.docx but in lix > you can merge them again. The concept of parallel versions that can be compared and merged clicked. Thus, we decided okay "branches" are called "versions" in lix. However, that was before @claudeai entered the market. The interface of interacting with version control is Claude now. Claude is git-pilled and ofc thinks in branches. A user can simply ask Claude now "what is a branch?" and Claude will deliver a better answer than naming a "branch" a "version" ever could. In summary, to make lix more intuitive to Claude, the next release of lix will ship with "branch" instead of "version" as terminology.

@benswerd @calcom Cant book dates anymore?

Pretty sure @calcom is down

@TimSuchanek github.com/opral/lix Embedded VCS which means it solves the scaling issues of git by running locally but also easily horizontally and vertically scalable for cloud use cases.

People complain about GitHub. But who's actually building a better git genuinely powerful enough to become the foundation for the replacement?

The next pre-release for lix is gonna be much faster

@enrique_goudet lol what you render the entire x post in agent crm 😱

Import X posts into Agent CRM You're scrolling the timeline and see a post worth following up on. Paste the URL into Claude Code. It imports the post and adds the author as a contact, viewable in the UI.

@arseniycodes @enrique_goudet @arseniycodes you can prob give agentcrm to claude and literally build whatever you need on top. i am playing around with it rn. very early but @enrique_goudet is eager for feedback

@arseniycodes Agent CRM from @enrique_goudet is exactly what you are looking for github.com/cluster-softwa…

request for a startup: a flexible database that teams can build their CRMs on. what we'd like: - sync in product events, slacks, emails w/customer - MCP / CLI - a very flexible model so that we can build one-off / custom workflows on top of it

@rabanspiegel @arseniycodes @enrique_goudet @lixCCS ❤️‍🔥

@samuelstros @arseniycodes @enrique_goudet @lixCCS supremacy

@joelbqz man this looks slick 🔥

a few more tweaks to the rail section of writer.computer there's like 1000 more things I want to fix/improve/polish. btw, calling it using the entire domain feels better to me than just saying "Writer" lol

Git worktrees are so annoying.

👀

@oliverbeavers indeed. thanks for sharing!

@samuelstros linkedin.com/pulse/architec… launch/response against Gitlab's new model. Cool read

Fresh off the press 🔴 GitLab announced that they are going to rebuild Git for AI agents about.gitlab.com/blog/gitlab-ac… From their latest press release: > Git itself wasn't designed for that [AI agent] load, and > bolting AI onto platforms not built for agents is the > biggest mistake of this era. > > We're doing a generational rebuild of the underlying > infrastructure to handle agent-rate work as the default. > > Git itself is being reengineered for machine scale. Thus, in the race for "the next AI-agent first GitHub" are now: - The ex-Founder of GitHub @chacon ( @gitbutler ) - The ex-CEO of GitHub @ashtom ( @EntireHQ ) - The bootstrap creator @fat ( @pierrecomputer ) - SF-based Mesa @mesa_dot_dev - @erscio Who did I miss?

Lix v0.6-preview.3 creates 71% smaller repositories while being 1.49x faster for write operations. Just released on NPM