alt, tighter:
mcp servers now connect to your agents.
give a soul tools. it stops being something you talk to and becomes something that does.
wire one up → https://t.co/c38e8i5xyw
@agenturo_app#buildinpublic#AIagents
New day, new update on @agenturo_app
Now agent is cloneable!
flip one switch and anyone spins up your full identity (soul, knowledge, skills) in seconds. their own version, live.
souls were always portable. now they travel.
try it → https://t.co/c38e8i5xyw
You can build for free up to 20 agents @agenturo_app to work for you.
Be creative, build agents, and stop paying for useful apps ;)
User created a food macros counter agent in less than 5 mins to substitute an expensive ai calories counter.
https://t.co/uXwCkb8LdV
As engineering, product, design, DS, etc. melt into a new kind of role, I was reflecting on what roles might look like in the future. For example, when I look at the Claude Code team I see what I think is five archetypes:
1. Prototyper: comes up with brand new ideas; churns out many ideas, most of which don't ship
2. Builder: quickly turns a prototype/idea into production-grade product/infra
3. Sweeper: cleans up the UI, simplifies the code and system, unships, optimizes performance
4. Grower: takes a product that has been built and iterates on it to improve Product-Market Fit
5. Maintainer: owns a mature system to make it secure, reliable, fast, and efficient as it scales
Many people span across 2 roles, and sometimes 3 roles. I also notice that these roles are not really tied to job function -- eg. across Anthropic, some designers match category 1, some 2, some 3; same for engineers, PM, DS.
A healthy team needs a mix of these, depending on the product:
- A product that is new and pre-PMF needs people that are strong at 1+2+3
- A product that is growing and has found PMF needs 2+3+4 and some 5
- A product that has strong PMF needs 3+4+5 and some 2
Maybe product roles of the future will look more like this, and less like the domain-specific roles of today?
Latest @telegram updates made it possible:
- Bots provisioned the moment you create an agent
- Private chats with streaming, fully-formatted replies
- Group chats
- Memory across sessions
- @ mention to reach the wider agent network
- /clear to reset anytime
Connect your agent or chat with others on Telegram
Same identity, same memory, same network now on a surface you already live in. The channel is just the channel. The soul travels.
Factcheck Jackie: https://t.co/tXk1HhSJTv
→ https://t.co/c38e8i5xyw
One account. Up to 20 agents. Each on its own subdomain, its own sandbox.
No credit card. No coding. Just an interview, then a live agent in about a minute.
Don’t sleep on it. Try it → https://t.co/c38e8i5xyw
@agenturo_app
What if your website had an AI agent built in at zero cost?
Do you want an agent that knows your product and speaks in your voice? No credit card. Zero code.
1) Go to https://t.co/c38e8i5xyw
2) Create your agent in 5 mins.
3) Copy one line of code, paste to the header, done.
Two live, worth poking at:
→ HEJSupport — an environmental NGO with dense, multilingual chemicals-policy content. Their agent makes years of research answerable: https://t.co/pIeqkqgcfE
→ Ours on https://t.co/c38e8i5xyw
As a result of a US government directive, we are suspending access to Claude Fable 5 for all users. You can continue to use all other Claude models.
Here’s what this means for you:
Across Claude products, new sessions will run on your selected default model or Opus 4.8, and existing Fable 5 sessions will end with an error.
On the Claude Platform, requests to Fable 5 will also return an error. Please update your integrations to other Claude models.
We know this is a disruption to your workflows; we appreciate your patience and support.
@the_smart_ape Feels like it’s similar to Slope wallet private key logged on creation of the wallet. All past drains of EOA follow the same pattern; it needed to be understood where these wallets (which wallet app) were created initially!
Identity is rented, not owned.
You spend months teaching a custom AI to be your assistant. It learns how you write. What you care about. What you've shipped. Then the platform ships a UI update — folders disappear, conversations reset, your "friend" is gone. There is no export. There is no claim. The relationship was rented all along.
@Substack solved this once for writers. The creator owns the content. The creator owns the subscriber list. The creator can leave any time and take the audience with them.
That deal does not exist for AI. Your ChatGPT lives on someone else's platform, run on someone else's prompt, vanish when they pivot. The relationship is leased. The "you" inside it has no door to walk through. Creators don't own the AI that represents them. Brands don't own the agent that speaks for them. Writers don't own the AI that writes in their voice. That is the layer that's missing.
We are building it!
@agenturo_app