However jira, trello, linear and basecamp are all SaaS. Then when you create a ticket, what starts the agent? Linear has integrations however that either needs codex/github running things (another SaaS) or you need to do your own agent setup.

This is a replacement for jira/etc for a project, rather than an addon.

https://chatgpt.com/share/e/6a0bf28b-e198-8012-9a88-c777d965...

Product owners can very quickly get, for many problems, an interactive demo without coding. For lots of problems this can be somewhere from a static html page which shows the interactions to a hacked in feature that lets them actually test if it solves the customer need and try several variations before handing over much more concrete specs of what they want to happen. So much time is lost between getting an idea from someone’s head to code to use to then find out it wasn’t communicated well and then finally that the idea didn’t help anyway and we want it in a different way.

Yes yes I know someone is about to say that now there’s pressure to push the prototype out but that’s an organisational level problem that existed anyway.

And small problems can much faster to solve as well, or even move away from devs. Often people just need some text changed somewhere or html putting together, or some basic code for analysis. They could understand the logic, but the task of writing it from scratch and how to run things may be too much - now you don’t need to prioritise work for a dev to get some sql written and they can spend their time on the larger more software engineering level problems.

These are language models, being able to talk through something with them and have them extract some information is what they excel at. Given that you’d probably get a halfway decent result with a literal fixed set of questions (an Eliza level docbot) gpt 5.5 is going to nail that as a task.

I’m not talking about gotcha level stuff here where the first time it didn’t compile because of a bracket or anything, or even first time wrong. They couldn’t do Fizzbuzz in a language of their choice, at all.

Those that could were always annoyed at having to do such things because how could someone coming for a contract position not be able to do this? Without seeing what a filter it really was.

I find repos because of search engines, links from project pages, links from package managers, hn, all external sources. If it’s from linked issues that’s user generated and can easily link off site (and often do).

Are you following users and finding repos like that by seeing that they commit to? Having GitHub recommend repos?

And global search but I don’t feel like that even really works.

All these other services have what you're talking about, and the only cross-repo/org work I can see here is:

* Aligned accounts (person X on one service is person Y on github), if you want that continuity across services

* Forking

And the whole forking/branching/merging side is handled by raw git.

That's why I've been asking what githubs huge centralisation gets us. It has a UI and features that are useful, great, those exist in other projects too, so what is the stickiness?

I'm quite sure at the time that they said they wouldn't give compensation, not that they wouldn't refund them.

All you've pointed to is devs working together and people filing bugs. All that requires is auth, no? Is that it? Is an SSO button really this enormous hurdle?

> It's just the same thing,

Saying dropbox is irrelevant because all end users could just "build such a system yourself quite trivially by getting an FTP account, mounting it locally with curlftpfs, and then using SVN or CVS on the mounted filesystem." is not the same as saying "what is the social aspect of github?".

Closer is what I've argued elsewhere, which is that multiple different hosts running (something like) gitea selling cloud based storage as a service would be extremely close to github for end users. And it would be identical for what you've talked about wouldn't it?

> you both are ignoring how important convenience is.

The convenience of what, specifically? Not having to click an SSO button on a new website?