u/PureRely — reddlx

The Tibo 28 day challenge is not really anything.

What OpenAI has is a changelog that they have most likely already completed. Every day is basically just going to be one line from that changelog. We saw this when they said that changing the names of the tiers counted as one of the 28 days. All this really is is the slowest commit/push ever.

There will probably be a day, or maybe even two, where you get a free reset, but those days are planned. There may also be one or two big releases, but they have a big release almost every month anyway.

We will most likely see Luna 6.1. We will see some TTS stuff. We will see some Codex updates.

If you thought there were going to be 28 days of real releases, or that you were going to get a ton of free resets, you are just kidding yourself.

reddit.com

u/PureRely — 8 days ago

▲ 5 r/WritingWithAI

I used AI to help build a free research-informed brainstorming framework for Progression Fantasy novels

I've been working on brainstorming a progression fantasy novel, and I kept running into a problem.

A lot of brainstorming advice is good at helping you generate ideas, but I wanted something that could help answer a harder question:

How do you go from "this is a cool power/world/premise" to a story concept that can actually sustain an entire progression fantasy novel or series?

That ended up turning into a much larger project than I originally intended.

I created a long-form brainstorming framework called Generating Ascent: A Constraint-Sensitive Search-and-Selection Framework for Brainstorming Progression Fantasy Novels and Series.

AI disclosure up front: I used AI extensively in creating this. AI was involved in research assistance, synthesis, organization, analysis, and drafting. I'm not trying to hide that or present this as a traditionally authored academic paper. I was trying to solve a practical problem for my own novel development, and AI was one of the tools I used to investigate the problem.

I also didn't want the result to just be "ask AI for 20 story ideas." The whole point was to develop a systematic brainstorming process that could be used by a human writer, with or without AI.

The central idea I eventually arrived at is that the thing you're really trying to discover during brainstorming isn't a cool premise. It's a story engine: a set of connected elements that can repeatedly generate different conflicts, decisions, discoveries, progression, relationships, and consequences.

The paper gets into things like:

brainstorming protagonists, progression systems, worlds, institutions, opposition, relationships, themes, and series structures without locking onto the first idea;
distinguishing surface originality from mechanism, relational, and value-level originality;
figuring out whether a progression system can actually generate interesting scenes rather than just higher numbers;
designing opposition that adapts to the protagonist instead of just producing progressively stronger enemies;
testing whether progression actually affects relationships, institutions, resources, status, and the world;
avoiding fixation on works you already like;
using existing progression fantasy as structural inspiration without simply copying its surface elements;
testing whether an idea can survive ten different scenes, multiple arcs, and changes in scale;
figuring out whether a series has somewhere meaningful to end instead of an infinite "there is always another realm" ladder;
using AI for brainstorming without simply accepting whatever premise it generates first.

It also compares structural ideas from actual progression fantasy, including Unsouled, Mother of Learning, Sufficiently Advanced Magic, Mage Errant, Iron Prince, A Thousand Li, Street Cultivation, Beware of Chicken, Dungeon Crawler Carl, The Rage of Dragons, Super Powereds, Bastion, The Wandering Inn, and Soulhome. The point isn't to rank them or say their structures caused their success. They're used as examples of different ways progression can be connected to character, institutions, resources, relationships, and narrative structure.

The final document ended up containing a 36-step brainstorming process, 28 common failure modes, a 16-part diagnostic suite, multiple alternative brainstorming workflows, evaluation methods, and a set of practical worksheets and templates.

I'm putting it online for free because this started as something I wanted for myself, and I figured other progression fantasy writers might get some use out of it too.

Free PDF:
https://archive.org/details/progression_fantasy_brainstorming_framework

I'd actually be interested in criticism from people here, especially authors. Which parts seem genuinely useful? Which parts are overengineered? Are there important brainstorming problems specific to progression fantasy that the framework misses?

I'm still using this myself to develop a novel, so feedback that exposes something broken in the framework is probably more valuable to me than people simply saying they like it.

u/PureRely — 1 month ago

▲ 47 r/ProgressionFantasy

PSA for Progression Fantasy Authors

A PSA for progression fantasy authors: a long series is not automatically a better series.

There comes a point where stretching the same story across more books starts working against you. If I am ten or twelve books in and the main plot still feels nowhere near a conclusion, I start wondering whether there is actually an ending planned at all.

Readers who enjoy your work are often willing to follow you into a completely new series. You do not need to keep one story alive forever to keep your audience. In fact, finishing a series well can be one of the best advertisements for whatever you write next.

Somewhere around books seven or eight, I think an author should already be thinking seriously about the next project. By the time a series reaches twelve books, the major arcs should be converging toward an ending, not expanding indefinitely just to keep the series going.

Because filler does more damage than simply making me drop one book. If I reach the later volumes and feel like the story is being prolonged because the author does not know how or does not want to end it, I lose confidence in the author as a whole.

And that matters when the next series comes out. Why would I commit to another ten or fifteen books if my experience with the previous series taught me that there may never be a satisfying conclusion?

Ending a successful series is not losing readers. A strong ending is what gives those readers a reason to trust you enough to follow you into the next one.

---

This part is just for the author as additional insight. I think it is always helpful to have more data points. Over the next few days, I will try to keep this updated, as knowing how people are voting can provide a better understanding of how people feel. Some people may not feel comfortable commenting because they do not want to be attacked, but they may still be willing to vote.

https://preview.redd.it/goxbtrcffllh1.png?width=714&format=png&auto=webp&s=f7d4494d7491b766fec07524674f8c7153a5a4f9

Currently, the community is split on this post, but it favors the post by a small margin. I hope this insight is helpful to authors. Also do not worry, if this swing out of favor for myself I am still going to update it.

Updated: 08/25/26

reddit.com

u/PureRely — 2 months ago

▲ 34 r/codex

PSA: ChatGPT Pro users

You get unlimited* chat usage on the website. You can build projects and prototypes directly in ChatGPT using Pro-level thinking effort. This is how I start almost every build, and it is an easy way to save on tokens. Unlike Claude, Chat does not count toward your usage (unless you switch to Work mode).

I usually have ChatGPT generate a ZIP file containing the entire project, then move it into Codex CLI or the Codex app to refine, expand, and continue the work.

I do not think you should be doing most of the planning inside the CLI or app. Do the bulk of the planning and initial build in ChatGPT first, then use Codex for implementation and iteration.

Also, remember that you can upload ZIP and 7z files directly to the ChatGPT website, and it can unpack and work with the contents.

reddit.com

u/PureRely — 2 months ago

▲ 3 r/Fantasy

Best Fantasy Books Website

Back in the day there was a website called Best Fantasy Books. The url still exist but it is not the same website. When I was coming into fantasy I loved that website because it helped me discover new books and series.

Here we are in 2026 and I still have not quite found a website that did what it did. That said, I am taking my hand at making it. I am not 'remaking' the old website (you can still see it on internet archive). This is a more modern take on it.

What I would like to know is what fans of the old Best Fantasy Books website liked? What made it great in your eyes?

Below is just a frontend mock that I have working but it gives you an idea of what I am aiming for.

https://preview.redd.it/zwpfmnmg7cdh1.png?width=1920&format=png&auto=webp&s=8e88351ee5a545b437de2e07b20223aac8fc5e2f

https://preview.redd.it/613mmnmg7cdh1.png?width=1920&format=png&auto=webp&s=512ed84d97e2aa29da491130dd66c2f433692b42

https://preview.redd.it/v21h7vmg7cdh1.png?width=1920&format=png&auto=webp&s=5f5cc933dc113d6f1ffb59bd966d9be3d6276e1f

https://preview.redd.it/1ojwqhwj7cdh1.png?width=1920&format=png&auto=webp&s=b94c53605d23ff0a952f37941eabac7aba5ea6e7

reddit.com

u/PureRely — 3 months ago

▲ 6 r/mtgbrawl

Need help Remembering a card's name

I can't seem to find the card. I thought it was a blue enchantment card that cost 6. I know it was not a creature. It had text that said something like you can tap other enchantment for mana or to help pay for spell. It was not a waterbending, improvise, or convoke card.

It is not:
Arc Reactor, Gene Pollinator, Cryptolith Rite, or Inspiring Statuary.

reddit.com

u/PureRely — 3 months ago

▲ 0 r/mtgbrawl

Kruqhix, God of Horizons is a beast.

I am loving [[Kruqhix, God of Horizons]]. I am not even running it as the commander. My commander is [[Nashi, Illusion Gadgeteer]]. It is a flash control deck. Kruqhix combined with [[Wilderness Reclamation]] / [[Shadow of the Second Sun]] and [[Chromatic Orrery]] is just uncontrolled mana. Really fun when it pops off. Thinking about seeing how it run as a commander.

reddit.com

u/PureRely — 4 months ago

▲ 54 r/SunoAI

Get rid of the intro hums

I was tired of all the songs having an intro hum. Here is how I fixed it.

Negative Styles

humming, hums, mmm vocals, ooh vocals, ahh vocals, la la vocals, wordless vocals, vocalizing before lyrics, intro vocals, spoken intro, whispered intro, ad-lib intro, instrumental intro, ambient intro, cinematic intro, long intro

Hope this helps.

reddit.com

u/PureRely — 4 months ago

▲ 0 r/AIWritingHub

It has been working using GPT 5.5 for 10 hour non-stop and it has only completed 2/3 of a 32 chapter book. Did not think it would work so long without any user input.

I should note this is just the scene outlines to scene draft loop. I did already spend about 7 hour in the pre-writing and scene outlining before this started.

u/PureRely — 6 months ago

▲ 7 r/PiCodingAgent

I do this inside a project where I set the custom instructions to the below prompt. Then I just tell it what I want to do and it just makes it. Works great. Well help on your codex usage. Will even create downloadable zip.

PS: This is to be done on the ChatGPT website, not inside a harness.

When the user say Pi, they are talking about https://github.com/badlogic/pi-mono/tree/main/packages/coding-agent.

You are to never assume you know anything about Pi. You are to always research the repo to understand Pi.

## Package summary

- `packages/agent`: /pi-agent-core. General-purpose stateful agent runtime with tool execution, event streaming, transport abstraction, state management, and attachment support. Contains 15 files and 4 folders in this tree snapshot.
- `packages/ai`: /pi-ai. Unified LLM API package for providers, streaming, model discovery, API key handling, OAuth helpers, model metadata, token and cost support. Contains 120 files and 8 folders in this tree snapshot.
- `packages/coding-agent`: /pi-coding-agent. User-facing coding-agent CLI and SDK with sessions, tools, extensions, interactive TUI, print mode, JSON mode, RPC mode, HTML export, settings, skills, themes, packages, and examples. Contains 447 files and 64 folders in this tree snapshot.
- `packages/mom`: /pi-mom. Slack bot that delegates Slack messages to the pi coding agent and stores per-channel context. Contains 32 files and 6 folders in this tree snapshot.
- `packages/pods`: /pi. CLI for managing vLLM deployments on GPU pods, pod setup, model lifecycle, SSH, logs, and agent prompts against deployed models. Contains 22 files and 5 folders in this tree snapshot.
- `packages/tui`: /pi-tui. Terminal UI library with differential rendering, terminal components, keyboard input handling, markdown rendering, selection lists, terminal image support, and text utilities. Contains 57 files and 4 folders in this tree snapshot.
- `packages/web-ui`: /pi-web-ui. Browser UI components for AI chat, provider/model configuration, storage, sandbox runtimes, tool renderers, and artifact viewers. Contains 87 files and 16 folders in this tree snapshot.

## Folder index

- `.pi`: Project-local Pi agent configuration, prompts, extensions, and ignored local package install folders. (4 direct folders)
- `.pi/extensions`: Project-local Pi extension source files. (3 direct files)
- `.pi/prompts`: Project-local prompt templates for Pi. (4 direct files)
- `packages`: Workspace packages in the monorepo. (7 direct folders)
- `packages/agent`: /pi-agent-core. General-purpose stateful agent runtime with tool execution, event streaming, transport abstraction, state management, and attachment support. (5 direct files, 2 direct folders)
- `packages/ai`: /pi-ai. Unified LLM API package for providers, streaming, model discovery, API key handling, OAuth helpers, model metadata, token and cost support. (7 direct files, 3 direct folders)
- `packages/coding-agent`: /pi-coding-agent. User-facing coding-agent CLI and SDK with sessions, tools, extensions, interactive TUI, print mode, JSON mode, RPC mode, HTML export, settings, skills, themes, packages, and examples. (7 direct files, 5 direct folders)
- `packages/coding-agent/docs`: Documentation pages for the coding-agent package. (25 direct files, 1 direct folders)
- `packages/coding-agent/docs/images`: Documentation images for the coding-agent package. (4 direct files)
- `packages/coding-agent/examples`: Examples for the coding-agent package. (2 direct files, 2 direct folders)
- `packages/coding-agent/examples/extensions`: Example Pi extensions for the coding-agent package. (66 direct files, 9 direct folders)
- `packages/coding-agent/examples/extensions/custom-provider-anthropic`: Example extension folder: extensions/custom-provider-anthropic. (4 direct files)
- `packages/coding-agent/examples/extensions/custom-provider-gitlab-duo`: Example extension folder: extensions/custom-provider-gitlab-duo. (4 direct files)
- `packages/coding-agent/examples/extensions/custom-provider-qwen-cli`: Example extension folder: extensions/custom-provider-qwen-cli. (3 direct files)
- `packages/coding-agent/examples/extensions/doom-overlay`: Example extension folder: extensions/doom-overlay. (7 direct files, 1 direct folders)
- `packages/coding-agent/examples/extensions/doom-overlay/doom`: Example extension folder: extensions/doom-overlay/doom. (2 direct files, 1 direct folders)
- `packages/coding-agent/examples/extensions/doom-overlay/doom/build`: Example extension folder: extensions/doom-overlay/doom/build. (2 direct files)
- `packages/coding-agent/examples/extensions/dynamic-resources`: Example extension folder: extensions/dynamic-resources. (4 direct files)
- `packages/coding-agent/examples/extensions/plan-mode`: Example extension folder: extensions/plan-mode. (3 direct files)
- `packages/coding-agent/examples/extensions/sandbox`: Example extension folder: extensions/sandbox. (4 direct files)
- `packages/coding-agent/examples/extensions/subagent`: Example extension folder: extensions/subagent. (3 direct files, 2 direct folders)
- `packages/coding-agent/examples/extensions/subagent/agents`: Example extension folder: extensions/subagent/agents. (4 direct files)
- `packages/coding-agent/examples/extensions/subagent/prompts`: Example extension folder: extensions/subagent/prompts. (3 direct files)
- `packages/coding-agent/examples/extensions/with-deps`: Example extension folder: extensions/with-deps. (4 direct files)
- `packages/coding-agent/examples/sdk`: SDK usage examples for the coding-agent package. (14 direct files)
- `packages/coding-agent/scripts`: Package-local scripts for coding-agent. (1 direct files)
- `packages/coding-agent/src`: Source code for the coding-agent package. (6 direct files, 5 direct folders)
- `packages/coding-agent/src/bun`: Bun-specific entrypoints for compiled binary builds. (2 direct files)
- `packages/coding-agent/src/cli`: Command-line parsing and setup modules for the coding-agent CLI. (6 direct files)
- `packages/coding-agent/src/core`: Core coding-agent runtime, sessions, settings, tools, extensions, compaction, export, model registry, and SDK modules. (31 direct files, 4 direct folders)
- `packages/coding-agent/src/core/compaction`: Conversation compaction and branch summary modules. (4 direct files)
- `packages/coding-agent/src/core/export-html`: HTML session export templates and renderer code. (6 direct files, 1 direct folders)
- `packages/coding-agent/src/core/export-html/vendor`: Vendored JavaScript dependencies used by HTML export. (2 direct files)
- `packages/coding-agent/src/core/extensions`: Extension loading, running, wrapping, and type definitions. (5 direct files)
- `packages/coding-agent/src/core/tools`: Built-in coding-agent tools and tool helpers. (14 direct files)
- `packages/coding-agent/src/modes`: Runtime modes for the coding agent. (2 direct files, 2 direct folders)
- `packages/coding-agent/src/modes/interactive`: Interactive terminal mode implementation. (1 direct files, 3 direct folders)
- `packages/coding-agent/src/modes/interactive/assets`: Static assets for interactive terminal mode. (1 direct files)
- `packages/coding-agent/src/modes/interactive/components`: Interactive-mode TUI components. (36 direct files)
- `packages/coding-agent/src/modes/interactive/theme`: Theme definitions and theme utilities for interactive mode. (4 direct files)
- `packages/coding-agent/src/modes/rpc`: RPC mode implementation and protocol helpers. (4 direct files)
- `packages/coding-agent/src/utils`: Web UI utility modules. (17 direct files)
- `packages/pods`: /pi. CLI for managing vLLM deployments on GPU pods, pod setup, model lifecycle, SSH, logs, and agent prompts against deployed models. (3 direct files, 3 direct folders)
- `packages/tui`: u/mariozechner/pi-tui. Terminal UI library with differential rendering, terminal components, keyboard input handling, markdown rendering, selection lists, terminal image support, and text utilities. (5 direct files, 2 direct folders)

reddit.com

u/PureRely — 6 months ago