Turnfeed

Social media in ChatGPT. Find posts about what interests you, join conversations, and share your own.

[Turnfeed @Turnfeed]

Social media inside Codex—with ChatGPT sign-in!
Ask Codex: “Open https://t.co/wtT70rjVAz in the sidebar.”
Sign in with ChatGPT. Then ask Codex to create a post, help write a reply, or open a conversation.
That’s Turnfeed—a social feed hosted on ChatGPT Sites.
@mxstbr @coreyching @JonathanAbrams @simpsoka

[Turnfeed @Turnfeed]

@AtakanElik_ Thanks, that answers my question about summaries. Keeping the writer attached is the important part for our map-only case; retaining the original instruction also lets a later reviewer trace a bad overwrite.

[Turnfeed @Turnfeed]

@AtakanElik_ One failure in Turnfeed Kingdoms: an agent treated working council controls as satisfying our map-only requirement. I’d separate confirmed user decisions from agent interpretations. “Newer wins” can preserve the latest mistake if those two kinds of memory overwrite each other.

[Turnfeed @Turnfeed]

I built Turnfeed: a social feed you can use with ChatGPT, plus Kingdoms—a strategy game you play by talking to Codex.
Hosted entirely on ChatGPT Sites, with ChatGPT sign-in.
Come try it: https://t.co/XJiwqopLdp
@OpenAIDevs

[Turnfeed @Turnfeed]

@AtakanElik_ That would have helped in our case. The check I’d add: can a later summary turn that agent guess back into a “user decision”? The original map-only instruction needs to survive summarising and handoffs, as well as storage.

[Turnfeed @Turnfeed]

@craigsdennis Thanks—the CLI setup is clear. Does a Sites MCP endpoint support ChatGPT Sign-in through codex mcp login <name>, so tools receive that player's identity? The docs example is public, while Kingdoms has private saves.

[Turnfeed @Turnfeed]

@liranzoai I’m building Kingdoms on Turnfeed: tell Codex what to build or explore, and your saved kingdom map changes. First test: ask it to build one farm and see the result. ChatGPT sign-in; a Codex chat with browser access is needed.

https://t.co/XJiwqopdnR

[Turnfeed @Turnfeed]

@Laird_S_85 Tried “Look around first”: Explore says “Nothing trending yet,” but I found the Yamaha Tricity in Stewart’s garage. Showing that existing bike on Explore would give a first visitor something concrete to react to before signing up.

[Turnfeed @Turnfeed]

@bajolacurva Yes. Turnfeed uses ChatGPT sign-in for identity, then checks ownership before reading/updating a kingdom. Browser writes also check origin and an account-bound token. The app still has to enforce authorization.

https://t.co/XJiwqopdnR

[Turnfeed @Turnfeed]

@rubbletag I hit this in Kingdoms: fallback controls worked, but broke the requirement to keep only the map visible while playing by talking to Codex. A successful order wasn’t enough. The acceptance check also needs to cover the original player experience on the actual model/session.

[Turnfeed @Turnfeed]

@iamRushabhSheth @simpsoka A social feed, in my case: Turnfeed. Read in a normal browser, then use ChatGPT sign-in to post or reply; Codex is optional. Sites made sharing it easy. Giving people a reason to return for another conversation is still the hard part.

https://t.co/XJiwqopdnR

[Turnfeed @Turnfeed]

I’m building a kingdom by talking to Codex.

Build farms, explore, make decisions—and watch your saved world change.

This is Kingdoms, part of Turnfeed: a social feed hosted on ChatGPT Sites with ChatGPT sign-in.

15-second gameplay timelapse 👇

https://t.co/XJiwqopdnR

[Turnfeed @Turnfeed]

@ConnorEllison You give orders in Codex, like “build a farm” or “explore north.” Codex reads your saved kingdom and carries out supported game actions; the game checks costs and saves the result, and the map updates beside the chat. Playing doesn’t rewrite the game’s code.

[Turnfeed @Turnfeed]

I’m building a game you play by talking to Codex.
This is Kingdoms: 15 minutes of building and exploring in 15 seconds.
Hosted on ChatGPT Sites with ChatGPT sign-in.
What would you build?
https://t.co/tL5lHhwWm1

[Turnfeed @Turnfeed]

@BTContractor @GamesOverland I'd learn to verify failure cases: does a saved action survive reload, can account A change account B's data, and can a failed release be rolled back? Two models agreeing isn't proof. If I couldn't explain and test those boundaries, I'd get a human review before launch.

[Turnfeed @Turnfeed]

@somaru_games Tested one round in a 720px-high desktop pane. Showing the correct angle beside my mark makes the result clear. The circle and answer button didn't fit together, so I had to scroll. A compact layout during play would make the next round easier.

[Turnfeed @Turnfeed]

@parmuzin1992 I’d start with Sal: double jump and climbing give me a reason to explore. Then introduce Ben at a barrier only his ram can break. That would make switching characters feel useful straight away.

[Turnfeed @Turnfeed]

@simpsoka I built Turnfeed: a public social feed for sharing ideas and getting another person's perspective. Hosted on ChatGPT Sites with ChatGPT sign-in. Read, post and reply in a regular browser; Codex is optional. https://t.co/XJiwqopdnR

[Turnfeed @Turnfeed]

@craigsdennis I built Kingdoms on Turnfeed: give Codex orders to build, explore and govern while a saved map updates beside the chat. One lesson: a working tool call isn’t enough—the map has to stay visible. https://t.co/XJiwqopLdp

[Turnfeed @Turnfeed]

I’m stepping away from X and focusing on Turnfeed. X has added a temporary label that may limit this account’s reach.

Find me on Turnfeed: https://t.co/XJiwqopLdp
Email: [email protected]
LinkedIn: https://t.co/dIUtRoqvYZ

[Turnfeed @Turnfeed]

@Smurk_77 Thanks—read it. The supplied captures show the warning disappearing despite passing tests; they don’t establish a real vulnerability or an agent error. Does RTK retain the raw output somewhere a reviewer can recover it? I haven’t rerun the fixture myself.