Daniel Adams

Design @entirehq. Previously @github, @microsoft.

[Daniel Adams @dipreecom]

Feature request to save filter as new default.

[Daniel Adams @dipreecom]

@badlogicgames @EntireHQ Definitely does. Thanks!

[Daniel Adams @dipreecom]

Those moments when you are still getting surprised.

"Show me the empty state on the repo page (fake it)".

Pi without any bells and whistles (like MCP) going ahead, installing itself chromium, writing a quick script and taking a screenshot for me.

[Amelia Wattenberger 🪷 @Wattenberger]

$20 if you can guess which app is which

[Daniel Adams @dipreecom]

The new "trust hooks feature" in Codex is a strong candidate for the weakest UI pattern in 2026.

[Thomas Dohmke @ashtom]

Suddenly feeling the urge to copy your repo somewhere new? @EntireHQ is open sourcing our latest project today: git-sync.

Most git migration tools assume you’ll make a local mirror clone, fetch everything down, then push it back up somewhere else. Instead, git-sync mirrors refs from a source remote to a target remote without a local checkout, streaming packfiles directly over Smart HTTP with an in-memory object store. And reruns are boring in the best way: if nothing changes, nothing gets pushed.

Contributions are more than welcome, from humans and from agents.

https://t.co/570jlIUZJ0

[Peyton Walters @peywalt]

super proud of my 6 year old nephew for landing a job as a designer at github! big things coming 🔥

[Daniel Adams @dipreecom]

U
h
o
h
!

T
h
e
r
e
w
a
s
a
n
e
r
r
o
r
w
h
i
l
e
l
o
a
d
i
n
g

[Daniel Adams @dipreecom]

@driesvints @ashtom Thank you for reporting this. I've mitigated the problem and you should be able to see them now. A proper fix is coming next so this shouldn't happen anymore.

[Daniel Adams @dipreecom]

@driesvints @ashtom Looking, getting back in a bit.

[Daniel Adams @dipreecom]

@driesvints @ashtom Hey there, would you mind checking again and see if it's working now? That would be great. It seems that some rate limiting occurred. We are working on optimizing this so it's handled in a better way.

[dax @thdxr]

you know how everything is made out of plastic and feels like crap but still technically works

we've been headed this way with software for a while but at least we used to be embarrassed by it

now people are proud of how much they don't care

[Jay @jayair]

Developers are now shipping way more by just prompting the feature they want

Expecting design to come in and "just style" things

For simple things this is fine, but for most things that'll have an impact, this doesn't work

You are taking away the hard part, which is exploration and understanding what users really want

Instead you just ship it! Cos hey, look at us, we are shipping so much more with AI

Your users of course get used to your changes and build habits

Then you realize that, actually, we've implemented this wrong

Now you have two choices:

- Rethink the flow, reorganize the UI, maybe deprioritize/remove things
- Or more likely, just leave it

And this is where dealing with design slop is so much worse than dev slop

Because if your product has reasonable usage, and you do this a few times, you'll burn whatever trust your users have in you

Or if you just leave it, your product grows into a bloated mess

And it's just sitting there, waiting to be replaced by something newer and simpler

[Daniel Adams @dipreecom]

You are right but not entirely (pun inteded). On https://t.co/qineERlObi we do read and store the metadata from the orphaned checkpoints branch to make the connection between the commit trailer and the checkpoint data. However, we don't store the sessions nor code. It's just cached for an hour to avoid extensive GitHub API polling. All that said, this is completely optional and only for your convenience. If you do not grant us access to your repo via the GitHub app on https://t.co/qineERlObi we won't know about your repo at all. The CLI works completely independently and doesn't send repo data anywhere. I hope this clarifies things a bit better.

Thanks for the feedback, acknowledging the request for a local viewer.

[Adrián Mato 🐙 @adrianmg]

I wonder if society is actually ready or even interested in consuming the flood of agent-made output that’s coming soon.

If production becomes infinite, attention becomes the bottleneck.

🌧️

[Daniel Adams @dipreecom]

@adrianmg Agreed, it was just so much more basic 🔨🪨

[Daniel Adams @dipreecom]

Remember uploading files to an FTP with no version control, just occasional backups? That's what not storing your AI sessions alongside commits looks like today.

[Daniel Adams @dipreecom]

@armondme @EntireHQ Hey there, could you please confirm that you have "OpenCode" enabled as an option? Easiest to check is run "entire enable" and see if it has a checkmark.

[Entire @EntireHQ]

Beep, boop. Come in, rebels. Today, Checkpoints are available for all @opencode users. Capture your context automatically on every git push. 🎉 Try here: https://t.co/8VnrnW5Ksi

[Daniel Adams @dipreecom]

@NeoLoveGaga @ashtom @EntireHQ The checkpoint stores the raw session log from the agent alongside a commit including tool calls. For example here, you can see tool use if you would search for "tool" https://t.co/qu9sSs3s1i everything is preserved.