@theo This could really help with our product that we’re building since we could essentially use t3 as a harness for ppl to use rather than building our own and then shipping our product around it. Would love it!
@theo thank god, thankyou for adding this, and since you’ve added this, there is another thing that could be useful; different teams having their different environments and workspaces. Basically, if a team supposedly uses t3 code and they dont code, they could customize diff workspaces
@theo Hi theo, used t3 code for codex as we’ve been doing for the past 2 months.. Noticed that from the doubling of usage for codex, drained from 100 percent of weekly limit to 0 in like 4 hours. We’re very concerned since we had only two sessions running on t3 code at the time
@thsottiaux@OpenAI Yall finally made the usage terrible to the point that im no longer a fan. This is a lie, a blatant lie tibo. I cannot believe that, after this change of yours, my limit felt as if it was the 20$ plan? Unbelievable. Truly devastated since I was getting important work done. Unsub.
@theo Hi @theo , can we have multiple github acc auths for t3 code. I have repos in different github accounts and I wanted a way to have them all in t3 :))
Big companies typically have standard practices and flows which may or may not be documented. For example, I have an underperforming team member and need to put them on a PIP and I want an agent to draft the formal paperwork in accordance with HR’s requirements (ie step 1. email [email protected] with Subject PIP, then wait for HR to confirm pip plan, then schedule meeting with person from HR and employee, etc)
If HR was maintaining the docs that define the process and had them loaded into memory for the agent, my job as a manager would be 10 times easier, could tell my agent to start the pip process in accordance with HR’s protocol, it could read HR’s processes and procedures and draft the PIP and send it to the right email in HR, and even auto schedule the meeting on my calendar.
Now imagine this for every red tape process in a large company, getting new equipment, new employee onboarding, how to hire contractors, how to get approval for a new project, etc. There are a million red tape scenarios that could be automated with agent memories maintained by various departments that create a shared brain for how the company works. In a small company this could just be a Google doc, but in a large Comoany this knowledge base could be massive where you may need a RAG database to search for keywords to even find the proper documentation.
@theo Building something in this space. Did dm you about it. Happy to give real examples and free pilot/demo to people interested.
Also, It’s less about “giving an agent memory” and more about capturing and connecting the context an organization builds up across people, teams etc.