> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usealmanac.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> This handbook preview targets personal CLI 0.11.1. Check installed command help and the matching backend schema before using examples with another release. Examples with named people and placeholder IDs are fictional.

# Research Reddit discussions

> Choose search or a subreddit listing, read nested comments and check the scope of returned evidence.

Reddit post search, a community's post listing and a discussion's comment tree answer different questions. Post search finds matches across communities. A subreddit listing gives posts from one community in a chosen order. Reading a thread returns comments, often with replies nested under top-level comments; a count of top-level objects is not a count of all returned comments.

There are two Reddit engines. The CLI's unqualified `reddit.post.search` description selects the Almanac/Apify contract; for the cursor-capable Netrows search, select `--engine netrows` explicitly. The examples below use Netrows consistently. Engine choice changes the input contract, paging and result shape; selecting an engine is not a guarantee that a particular request will succeed.

```sh theme={"theme":{"light":"github-light","dark":"vesper"}}
almanac web describe reddit.post.search --engine netrows
almanac web search --source reddit --type post --engine netrows 'Python asyncio' --limit 10 --output page1.json
almanac web search --source reddit --type post --engine netrows 'Python asyncio' --limit 10 --cursor @page1.json --output page2.json
```

Fetch page 2 only if page 1 returns a `next_cursor`; repeat the query and filters. Use a returned Reddit `permalink` to cite a discussion. Its separate `url` may point to an external article. The Netrows search contract has no structured subreddit filter. For a question restricted to one community and newest order, read that community's posts and inspect their subreddit, text and timestamps:

```sh theme={"theme":{"light":"github-light","dark":"vesper"}}
almanac web read --source reddit --type subreddit --part posts --engine netrows --subreddit Python --sort new --limit 100 --output community.json
```

A newest-post listing can reach beyond a date cutoff without proving that every relevant post was returned. If it supplies no continuation, describe the returned window rather than claiming exhaustive coverage. `--time` on the Netrows community listing is for `top` sorting; with `new`, check dates yourself. The Apify post-search description lists both `--sort new` and `--time month`, but the CLI rejected that combination: its time filter works only with `top`, `controversial` or `relevance`. Treat that as a current contract defect, not a filter to assume was enforced.

To read a known post's replies, carry its subreddit and post ID from the post URL:

```sh theme={"theme":{"light":"github-light","dark":"vesper"}}
almanac web read --source reddit --type post --part thread --engine netrows --subreddit Python --post-id 1w43div --limit 500 --output thread.json
```

Count nested replies as well as top-level comments when summarizing the retrieved discussion. A post's comment count can disagree with the returned tree, and absence of a cursor does not prove that the tree includes every live comment. Describe the comments returned by this read and any visible gaps. If a provider returns HTTP 400, no comment evidence was retrieved by that attempt; inspect the other engine's contract or report the missing evidence rather than inferring replies from a search snippet.