Daniel Adams

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. github.com/entireio/git-s…

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

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

@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.

@dipreecom @ashtom Do you might know how long it takes before repos are loaded in after the GitHub app has been approved for those repos on an organization? We approved some repos over an hour ago but they're still not showing up on entire.

This week we focused a lot on performance improvements to make the Entire CLI better, faster, and more capable.🏃And Marvin authors our Dispatch now 🙂

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

@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.

@ashtom Does this loading state ever change? 🤔

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

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

You are right but not entirely (pun inteded). On entire.io 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 entire.io 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.

The downside of using @EntireHQ is that it requires read access to your repositories. This is because the CLI stores session metadata on a Git branch, and their servers read that branch to render the web dashboard. Therefore, this means that your repository data will be passing through their infrastructure. It will be great to have a local first viewer.

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. 🌧️

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

@dipreecom That was so fun tho! 😂

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.

@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.

@EntireHQ couple of issues - right now badge showing claude code even though using opencode - i see the diff in checkpoints but no session

Beep, boop. Come in, rebels. Today, Checkpoints are available for all @opencode users. Capture your context automatically on every git push. 🎉 Try here: #opencode" target="_blank" rel="nofollow noopener">github.com/entireio/cli?t…

@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" github.com/entireio/cli/b… everything is preserved.

@ashtom @EntireHQ Checkpoints for agent context is the feature I didn't know I needed. Biggest pain right now is losing state when switching between coding agents mid-task. Does it capture tool call chains or just conversation context?

tl;dr Today, we’re announcing our new company @EntireHQ to build the next developer platform for agent–human collaboration. Open, scalable, independent, and backed by a $60M seed round. Plus, we are shipping Checkpoints to automatically capture agent context. In the last three months, the fundamental role of the software developer has been refactored. The incredible improvements from Anthropic, Google, and OpenAI on their latest models made coding agents so good, in many situations it’s easier now to prompt than to write code yourself. The terminal has become the new center of gravity on our computers again. The best engineers can run a dozen agents at once. Yet, we still depend on a software development lifecycle that makes code in files and folders the central artifact, in repositories and in pull requests. The concept of understanding and reviewing code is a dying paradigm. It’s going to be replaced by a workflow that starts with intent and ends with outcomes expressed in natural language, product and business metrics, as well as assertions to validate correctness. This is the purpose of our new company @EntireHQ, to build the world's next developer platform where agents and humans can collaborate, learn, and ship together. A platform that will be open, scalable, and independent for every developer, no matter which agent or model you use. Our vision is centered on three core components: 1) A Git-compatible database that unifies code, intent, constraints, and reasoning in a single version-controlled system. 2) A universal semantic reasoning layer that enables multi-agent coordination through the context graph. 3) An AI-native user interface that reinvents the software development lifecycle for agent–human collaboration. In pursuit of this vision, we’re proud to be backed by a $60M seed round led by @felicis, with support from @MadronaVentures, @m12VC, @BasisSet, @20vcFund, @CherryVentures, @picuscap, and @Global_Founders alongside a global group of builders and operators, including @GergelyOrosz, @theo, Jerry Yang, @oliveur, @garrytan, and many others, who all recognize that the time is now to take such a big swing. And we begin shipping today with Checkpoints, a new primitive that automatically captures agent context as first-class, versioned data in Git. When you commit code generated by an agent, Checkpoints captures the full session alongside the commit: the transcript, prompts, files touched, token usage, tool calls, and more. It’s our first crack at the semantic layer, as open source CLI on GitHub. From here on out, no more stealth. We are building in the open and as open source! More to come soon, in the meantime check out all the details in our blog.

@adrianmg x.com/dipreecom/stat…

Whats your favorite icon set nowadays

@moby763canary21 @EntireHQ Cool, let me know your thoughts.

Just made my first commit with @entirehq. Looking forward to using it from now on.

Hi, this is unfortunately a common source of confusion. The "Act on your behalf" message is a generic label GitHub shows on every OAuth authorization screen. We do use a GitHub app, and this is the OAuth flow of the GitHub app. It simply means the app will use your user access token to make API calls as that user. The user token is still scoped to whatever permissions the GitHub app has configured. You can validate the permissions of the GitHub app in the user settings under "integrations > applications > Entire" to be read-only for the mentioned scopes.

@EntireHQ Thanks for reply, Why full access is required? Instead of github app based approach.

Why @EntireHQ? This is the only thing preventing me to try.

From today’s episode of „Agents“: Claude accidentally changed their policy and rolled back x.com/trq212/status/…. People instantly lost there minds about it x.com/gergelyorosz/s…. Meanwhile Codex can‘t work off a list of tasks they said to work off weeks back and now have to re-align x.com/thsottiaux/sta…. Did I miss anything? 🍿

@thsottiaux github.com/openai/codex/i… this would be great github.com/openai/codex/i…

Codex team is fairly distributed, but most of the team is gathering in person over next 48 hours to take a step back and align on what’s next this year. What should we discuss?