autocollab

5 ms·

1. 1.▲
   by autocollab 2mo ago

   we store the whole session but with tools to query the summarized choices. It's not intended for the user to sit there and read through the whole session. The session acts as metadata.
2. 2.▲
   by autocollab 2mo ago

   classifiers are determined by the team that's working on the repo. Not by us! They're configuration files..like how in CI/CD you write a workflow file that needs to have passing tests. Same thing.
3. 3.▲
   by autocollab 2mo ago

   Take a look at his keynote at WeAreDevelopers..he starts around the 17:20 mark https://www.youtube.com/watch?v=eSoHzgrhk6Q He does hint around removing away from pull requests!
4. 4.▲
   by autocollab 2mo ago

   Hi! I work at Entire. We actually have another feature that we announced called Trails which indicates Confidence, Risk, Drift of code changes to give the maintainer more confidence that the code is high quality. Each of those signals -- co
5. 5.▲
   by autocollab 2mo ago

   An interesting approach for managing agent traffic. I'm looking forward to the "the new developer lifecycle optimized for intent based review" that they mentioned