Hidde

Founding AI Engineer @ | prev: ML @Cambridge_Uni

[Hidde @piros_dev]

Building the best tool to set up your @shadcn project

No more security issues, dependency hell, linting errors, or config headaches.

Just code that works.

[Hidde @piros_dev]

@maoniushanensis i'll send some

[Hidde @piros_dev]

Introducing claude code uptime merch

https://t.co/DNeddEWoPn

[jack friks @jackfriks]

claude is down with a major outage for everyone

except for the government

[Hidde @piros_dev]

@Osamadev_ yes

[Hidde @piros_dev]

@colmtuite @base_ui If people use the same combination of primitives+logic (queue, edit state, /,@ etc etc), it seems nice to have something stable, instead of having people to re-combine everything themselves.

I see it as a cmdk or a drawer which both build on Dialog, but maybe out of scope.

[Hidde @piros_dev]

Assistant-ui has a few for: composer (with submit, queue, being able to @ / in the composer etc) https://t.co/lFetjksjNF which build on top of other radix-ui primitives under the hood I think

Fluid functionalism or AI elements are the same. Everyone is re-inventing the same logic under the hood, while I would prefer to have an headless library that can handle this stuff, so people can focus on the styling part (while still being able to decide themselves what happens onSubmit)

I fully understand that base-ui would probably want to focus on the lower-level primitives primarily, but I can see a world how this could set it apart from things like Radix. Like how the Drawer extends Dialog, or how people combine Dialog+auto complete for cmdk menus.

(like an attachment could be similar to the Avatar component, where you have control over how you style the loading state etc)

https://t.co/KCkJTkAJjk
https://t.co/XMzStwZdRa

[Hidde @piros_dev]

epic! yeah I don't think there are any good ai-primitive libraries rn. and ofc they can be made using other primitives, but then it feels like everyone is reinventing the same wheel.

I don't know if that is in scope for base-ui, but would love some ai-primitives where the user would only need to decide on how they want things to be styled etc. Assistant ui and vercel ai primitives are kinda clunky and forgotten (unlike base-ui).

And I think it would be good for a headless package like base-ui to have proper accessibility decisions baked in for common components like these

https://t.co/MBydmrjYYC

[Hidde @piros_dev]

easy way to set up storage (history, mayb memory could be cool like mastra). MCP, guardrails. branching etc.

I love how easy it seems to set up the harness with eve, but actually deploying in in frontend production still seems to require like a lot of work (unless you deploy as a slack agent).

AI Elements feels like a forgotten child (and alternatives like assistant-ui are also not great) and could be integrated very nicely. This stuff is probably out of scope for eve, but would love to see a more opinioted headless components library (like base-ui), but for composer with / commands @ tagging, message queuing or steering.

know you could set this up all manually, because you have the tool call type safety, but this is why it kinda felt more as it was built for "internal agents" or background agents, that the customer would not necessarily directly interface with.

Amazing work regardless for the first release, and looking forward to where this goes!

[Hidde @piros_dev]

@colmtuite @base_ui This looks epic! is this already possible and works for arbitrary triggers? ($, @, / etc), and how is this structured under the hood? like if you would send this message to an agent what would it see?

Als need to be able to render these tags and skills in messages ofc.

[Hidde @piros_dev]

@fuma_nama Could be huge for companies that release product changelogs as well (instead of just package changelogs for oss)

[Hidde @piros_dev]

@devongovett need the first one in base ui @colmtuite 👀

[Hidde @piros_dev]

easy way to set up storage (history, mayb memory could be cool like mastra). MCP, guardrails. branching etc.

I love how easy it seems to set up the harness with eve, but actually deploying in in frontend production still seems to require like a lot of work (unless you deploy as a slack agent).

AI Elements feels like a forgotten child (and alternatives like assistant-ui are also not great) and could be integrated very nicely. This stuff is probably out of scope for eve, but would love to see a more opinioted headless components library (like base-ui), but for composer with / commands @ tagging, message queuing or steering.

know you could set this up all manually, because you have the tool call type safety, but this is why it kinda felt more as it was built for "internal agents" or background agents, that the customer would not necessarily directly interface with.

Amazing work regardless for the first release, and looking forward to where this goes!

[Hidde @piros_dev]

@FredKSchott @flueai Really appreciate the transparency here! Would love to hear what you think about mastra

[Daniel A. Saedi (DataManDan) @TheRealDanSaedi]

Every sales and marketing tool now promises AI will improve your results

but they don't tell you how it will cost thousands of dollars and hours of time to onboard

We built a system with @OpenAI for the part everyone hides: onboarding

And today we're giving it away for free

[Hidde @piros_dev]

@roshunpatel this disclaimer will become the biggest flex in a year or two 👀

[Daniel A. Saedi (DataManDan) @TheRealDanSaedi]

AI can now read your customers' minds.

We raised a $20M Series A lead by 8VC & Lingotto to build this.

Introducing Minerva, built in collaboration with OpenAI:

[Hidde @piros_dev]

@VictorTaelin thats opus for ya

[Hidde @piros_dev]

@Osamadev_ @thsottiaux 5.6

[Hidde @piros_dev]

@RCAgator @joshscorcher now replace the blue people with babies or elderly

[Hidde @piros_dev]

@ericzakariasson wish it could do this locally tbh.