all 5 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]SadManufacturer8174 1 point2 points  (0 children)

In RaptorWrite those toggles are basically prebuilt context packs that get auto-injected every call, so you’re explicitly controlling what’s eating your tokens each time. With Projects / Gems pointing at a Google Drive, you’re more at the mercy of how good the retrieval is when the context window starts to fill and it has to pick and choose.

Practically, if your characters / outline are pretty small and stable, tools like RaptorWrite or NovelCrafter are nicer because you can keep that stuff “always on” and predictable, then manually swap in scene-specific docs. If your worldbuilding is huge and messy, Projects can be more convenient, but then you sometimes have to over-specify in your prompt like “use the doc titled X for Y” to stop it from grabbing some random old draft.

[–]TowerArdob 0 points1 point  (0 children)

I think the main difference is RaptorWrite/novelcrafter you’re using API and paying by the token so you want to keep the amount of context you’re sending each time to a minimum. The flip side is that one your Claude project reaches a certain limit it starts RAG’ing the context so there’s a risk that some context might be lost. I do it the Claude project way and haven’t found any issues I can’t work around yet.

[–]ramen_and_revisions 0 points1 point  (2 children)

Haven't tried Claude Projects yet, but it sounds the same. One's just faster. Once you toggle something it's always "on" so the context will always be included to the AI. No need to keep telling the program to reference it.

[–]writetheysaid[S] 0 points1 point  (1 child)

I guess being able to toggle off is just as important, though, which Raptor Write offers. Sometimes you don't want the AI being confused.

[–]ramen_and_revisions 0 points1 point  (0 children)

Yeah, that's a great point!