Christoph Sitter

Co-Founder/CTO @FiftySixtyHQ

[Christoph Sitter @ChristophSitter]

Looking forward @RaiseSummit

[Michael Hochberg @hochberg_]

Will be back in Paris the week of July 6 for @RaiseSummit! We’re helping companies navigate data center power strategy, utility engagement, deal structuring, siting, and powered land at @FiftySixtyHQ. Lmk if you’ll be there, would be great to connect in person.

[Christoph Sitter @ChristophSitter]

@chadbyers Congrats on the Venture!
Would be very keen to learn more and see if we can work together. We have some interesting sites with near-term power availability that may be of interest to you.

[Michael Hochberg @hochberg_]

It all comes down to vetted schedules for the complex, overlapping workstreams that make power delivery real.

Through exclusivity at sites and ranches that provide access to near-term power across the US, that is exactly what we’re building at @FiftySixtyHQ.

[Jeremy Yudkin @yudDIDit]

Today, @editframe emerges from stealth. Agents need video.

Editframe Agent Skills:

npm create @editframe@latest

Just prompt Claude Code, Cursor, or Codex and get a working video or a full interactive GUI.

This video was created just by prompting 👇

[Michael Hochberg @hochberg_]

@PeterDiamandis Reach out if you’d like to discuss how we at @FiftySixtyHQ navigate the core challenges causing these issues, along with our near-term powered land and data center projects 🤠

[FiftySixty @fiftysixtyhq]

Some people like beach photos.
We like this.

[Christoph Sitter @ChristophSitter]

Biggest mistake: I treated memory like storage, not like accumulated experience.

[Christoph Sitter @ChristophSitter]

A few weeks ago we gave an AI agent a real job:

Data center developer.

It ran diligence, sent emails and worked on live projects. It was shockingly good.

Then I accidentally wiped its memory.

Turns out: when AI systems learn, infra mistakes don’t just break things, they erase experience.

We're now building it again, but better. Full story 👇

[Christoph Sitter @ChristophSitter]

https://t.co/hsnwXcym90

[Christoph Sitter @ChristophSitter]

This is what the protocol should look like everywhere.

Claude Code gave us the hooks. We built the integration. Zero-touch persistent memory.

Now imagine if ChatGPT, Gemini, Cursor all had the same hooks.

One config. Every tool remembers you. That's the future.

https://t.co/gK6xsjLx1i

[Christoph Sitter @ChristophSitter]

The problem with AI memory: there's no easy way to share it across tools

You can build the best memory layer in the world, but if the AI tool doesn't call it at session start, users have to manually configure system prompts.

Claude Code just shipped HTTP hooks. And we use them to solve it.

[Christoph Sitter @ChristophSitter]

Here's what Memobase + Claude Code HTTP hooks does:
Session starts: memory capabilities auto-injected. No system prompt.
While you work: tool usage silently tracked.
Before compaction: session activity preserved.
Session ends: everything persisted for next time.

Paste one config. That's it. Memory just works.

[Christoph Sitter @ChristophSitter]

Memobase is live in open beta. The universal memory layer works today. The open protocol is the mission. If you're tired of being the memory layer yourself — try it: → https://t.co/FbyttOqBdb

[Christoph Sitter @ChristophSitter]

I've been building a fix for #aiamnesia — one memory layer that works across all your #AgenticAI tools. Here's the problem, what's live, and why this is harder than it looks. 🧵

[Christoph Sitter @ChristophSitter]

The harder part: getting AI tools to actually USE memory automatically. There's no standard for ambient memory — no protocol that lets you plug in your memory server and have it work everywhere without manual setup. That's the mission. Build that protocol.