
Ops & growth for AI agents and developer ecosystems What works (and breaks) when you're growing agent products @VectoreeAI · https://teapawt.net/t.co/rXs1S6M74x
Los Angeles, CA
Joined August 2024
- Tweets670
- Following1.3K
- Followers1.2K
- Likes1.7K
Pinned Tweet
I work on growth for AI agents, mostly the unglamorous part: getting a first project live without standing up a second backend.
If you're building with agents, come hang out: discord.gg/vwBkxhEnbA
Or try the stack I work on, @VectoreeAI: vectoree.ai
2
24
941
Models, tools, auth, database, and storage. One key for OpenAI, Anthropic, Google, and xAI.
Give your agent a backend.
Models, tools, auth, database, and storage.
One key for OpenAI, Anthropic, Google, and xAI.
Install the skill, log in, link the project.
Five dollars to start. Then pay per token.
vectoree.ai
1
27
Skill → login → link → gateway.
Your agent writes code. It can't store users, or the data.
Vectoree is the backend.
Skill → login → link → gateway.
vectoree.ai
1
14
pinning Codex on mobile is the part I care about. reviewing agent PRs from my phone would be nice @thsottiaux
We’re also working on a new mobile experience for ChatGPT!
It’s easier to get to your favorite features and discover what you can do in ChatGPT. We’re starting with Pro users who have a dot or are eligible to create one. Your dot gets its own tab, and you can pin Codex, Projects, Images, and more to the tab bar. Some of you will see the new experience by default.
You can turn it on or off anytime in Settings > New ChatGPT Design.
Super excited to hear your feedback before we roll it out more widely!
1
75
Hey founders! @X
Looking to connect with people building in:
• Mass
• AI Agent
• Agentic AI
• indie hacker
• Full-Stack developer
• content creators
Drop what you're working on
18
9
453
GPT-6.2 Astra and Sol are now available. @OpenAI
Some of you have been asking very politely. Some of you have just been asking.
GPT-6.2 Astra and Sol are now available.
Super efficient and built to perform where it counts—the real world.
openai.com/index/introducing…
2
97
Hello @X family, my product account @VectoreeAI
looking to #connect with people into:
🎨 Full-Stack developer
🧩 DevOps backend
🚀 Maas
🎯 AI agent
Agentic AI
9
12
521
This release is worth paying attention to @liquidai
Today, we release d1.2 and d1.2-ultra, the state-of-the-art omnimodal decision models. d1.2 and d1.2-ultra both can process text, images, and audio with new output capabilities.
> #1 on the @ArtificialAnlys Decision Index (75)
> Read a value from the input (text, number or date)
> Find every passage of a kind in a text (spans)
> Locate things in a picture (box for one, boxes for every instance)
> Estimate a number (number with a range)
> Pick every option that applies (choice)
1/ 🧵
2
62
The agent part is fun.
One key instead of five dashboards. If you're building with Cursor or Claude Code, give it a try. @VectoreeAI
1
2
55
leaving because the culture changed, not the job. that's the quiet kind of exit most companies never see coming.
@darrell_dai
I’ve decided to leave NVIDIA. There are a few things I want to say.
As a robotics engineer at NVIDIA, I have seen Jensen as much more than the company’s CEO.
I admire his willingness to invest in a future that was not yet obvious. He committed to CUDA long before the deep learning boom and positioned NVIDIA for AI before it became everyone’s priority. Those decisions helped build the infrastructure that powers today’s AI.
I have seen that same vision in physical AI: investing in robotics, sharing open-source tools and projects, and building computing platforms that bring AI into the physical world. This is the work I do every day—and a future I believe in.
But what matters most to me is the culture he helped build.
Engineers are encouraged to explore, take risks, and learn from mistakes. Jensen reads employees’ Top 5 emails, follows their work, and engages directly. In a company this large, that connection matters. It makes an individual engineer feel that their ideas can still be heard.
That is why this has been so disappointing.
I do not have all the facts surrounding the allegations, and I cannot prejudge the investigation. My admiration for Jensen does not put him above scrutiny.
What I find difficult to accept is having to come to terms with his departure before receiving an explanation that helps me understand it. What this means for our direction, our culture, and the people doing the work remains unclear to me.
I have felt that engineers’ perspectives matter here. On this decision, I have not felt heard. That gap has been more painful than I expected.
I understand that some information cannot be shared immediately. But that does not erase the feeling of being left outside a decision that affects the company we help build every day.
A company’s greatness comes from its leadership, its governance, and the people who turn its ambitions into reality. Employees’ trust and sense of belonging are part of that, too.
Jensen’s vision and the engineering culture he shaped were important reasons I wanted to stay. His departure led me to decide that my own chapter here should also come to a close.
I leave with sadness and gratitude. The colleagues I have worked with, and the work we believed in together, will always matter to me.
These are my personal views.
Everyone's sharing what Claude Fable 5.2 can write this week.
From the ops side, I keep looking at a different part of those demos: what happens after the code works.
I work on growth for agent products, and the pattern I see hasn't changed with better models. People rarely get stuck writing the agent. They get stuck right after:
• which model, and where the keys live
• how users sign in
• where each user's data goes
• where files go
• who pays for the calls
None of it shows up in a demo video. All of it has to exist before a second person can use what you built.
Better models don't close this gap. They make it easier to see. Writing gets cheaper with every release. Getting a first project live doesn't.
That's the part I work on at @VectoreeAI: one project key for models, tools, auth, Postgres, and storage, so the backend stops being a second project.
If you're building with agents right now, what was the last thing that stopped you from shipping?
3
4
216
Code is the recipe, not the kitchen.
Models can write the program. Someone still has to turn the power on.
@claudeai @VectoreeAI
Claude Fable 5.2 has owned the timeline this week.
4,800 lines of Python → a pelican riding a bike in Blender, GUI never opened 2,000 lines of Three.js → one animation, 83 minutes of rendering A custom paint engine → 700,000 brushstrokes on a single canvas
Then the scores landed: #1 on the Artificial Analysis Intelligence Index. FrontierCode 2.0 up from 32.4% to 49.1%. Up to 30% faster output. Prices down 20%.
Code is becoming AI's universal medium. If it can be defined, executed, and checked on a computer, AI can attempt it.
Here's what the demos skip: the model writes the program. It doesn't deliver it to users. It can't open a cloud account, manage keys, set permissions, or pay for its own calls.
Code is the recipe, not the kitchen.
The bottleneck moved. It was "can we build it?" Now it's what comes after:
• which models, whose keys
• sign-up, sessions, access control
• Postgres, per-user data isolation
• file buckets and uploads
• usage, billing, a public URL
"We're just one programmer short" has become "we're just one backend short."
That's Vectoree. One project key for models, tools, auth, database, and storage.
• Model Plaza: 315 models, or just use vectoree/auto
• Tool Hub: hosted MCP tools for search and extraction
• Skill + CLI: your agent creates tables, uploads files, calls models
• OpenAI-compatible: change the baseURL, swap the key
• No monthly fee. $5 welcome credit after CLI login + link
Deploy and Payments are coming soon. We're not going to pretend they're live.
AI is learning to create worlds. We want to turn the power on.
Where do you get stuck: writing the agent, or shipping it?
2
48
I've noticed that AI-generated work often looks fairly professional if you leave it untouched.
But in real situations, you have to keep revising it, and that's when AI becomes inefficient—sometimes even slower than doing it from scratch.
1
2
149
i work on ai agents all day and this loop is way too real. half the time i can't tell if i'm early or just very online @waitbutwhy
[read about what’s happening with AI]
ME: Wow we’re actually legit fucked this is so bad.
[go outside]
ME: Wait those people are all acting like nothing unusual is happening. Maybe I was just in a paranoid bubble? Yeah it must be that. Phew.
[read more about what’s happening with AI]
ME: Wait no we ARE fucked. Shit. It’s all those people outside who are in a delusional bubble.
[go outside]
ME: Wait...
1
77















