Discrawl

Use local Discord archive data first for Discord questions. Hit Discord APIs only when the archive is stale, missing the requested scope, or the user asks for current external context.

Sources

• DB: platform-native XDG data dir, usually ${XDG_DATA_HOME:-~/.local/share}/discrawl/discrawl.db on Linux or ~/Library/Application Support/discrawl/discrawl.db on macOS
• Config: platform-native XDG config dir, with legacy fallback to ~/.discrawl/config.toml
• Cache: platform-native XDG cache dir
• Logs: platform-native XDG state dir
• Git share repo: platform-native XDG data dir
• Repo: openclaw/discrawl; use ~/GIT/_Perso/discrawl only after verifying its remote targets openclaw/discrawl, otherwise use a fresh checkout
• Preferred CLI: discrawl; fallback to go run ./cmd/discrawl from the repo if the installed binary is stale

Freshness

For recent/current questions, check freshness before analysis:

discrawl status --json

For precise freshness from the default database:

# Discrawl uses macOS ~/Library defaults unless XDG_DATA_HOME is explicitly set.
case "$(uname -s)" in
  Darwin)
    db="$HOME/Library/Application Support/discrawl/discrawl.db"
    ;;
  *)
    db="${XDG_DATA_HOME:-$HOME/.local/share}/discrawl/discrawl.db"
    ;;
esac
sqlite3 "$db" \
  "select coalesce(max(updated_at),'') from sync_state where scope like 'channel:%';"

Routine diagnostics:

discrawl doctor

Desktop-local refresh:

discrawl sync --source wiretap

Bot API latest refresh, when credentials are available:

discrawl sync

Use --full only for deliberate historical backfills:

discrawl sync --full

If SQLite reports busy/locked, check for stray discrawl processes before retrying.

Query Workflow

1. Resolve scope: guild, channel, DM, author, keyword, date range.
2. Check freshness for recent/current requests.
3. Prefer CLI search/messages for slices; use read-only SQL for exact counts.
4. Report absolute date spans, counts, channel/DM names, and known gaps.

Use root or subcommand help for syntax: discrawl --help, discrawl help search, discrawl search --help. Use DISCRAWL_NO_AUTO_UPDATE=1 for read smokes when you do not want git-share updates.

Common commands:

DISCRAWL_NO_AUTO_UPDATE=1 discrawl search --limit 20 "query"
discrawl messages --channel '#maintainers' --days 7 --all
discrawl dms --last 20
discrawl tui --dm
DISCRAWL_NO_AUTO_UPDATE=1 discrawl --json sql "select count(*) from messages;"

SQL

Use discrawl sql for exact counts, joins, and ranking queries when normal CLI reads are too coarse. The command is read-only by default, accepts SQL as args or stdin, and supports --json for agent parsing.

Useful examples:

DISCRAWL_NO_AUTO_UPDATE=1 discrawl --json sql "select count(*) as messages from messages;"
DISCRAWL_NO_AUTO_UPDATE=1 discrawl --json sql "select coalesce(nullif(c.name, ''), m.channel_id) as channel, count(*) as messages from messages m left join channels c on c.id = m.channel_id group by m.channel_id order by messages desc limit 20;"
DISCRAWL_NO_AUTO_UPDATE=1 discrawl --json sql "select coalesce(nullif(mm.display_name, ''), nullif(mm.global_name, ''), nullif(mm.username, ''), m.author_id) as author, count(*) as messages from messages m left join members mm on mm.guild_id = m.guild_id and mm.user_id = m.author_id group by m.guild_id, m.author_id order by messages desc limit 20;"

Never use --unsafe --confirm unless the user explicitly asks for a database mutation and the write has been reviewed.

When the installed CLI lacks a new feature, build or run from a verified openclaw/discrawl checkout before concluding the feature is missing.

Discord Boundaries

Bot API sync requires configured Discord bot credentials; do not invent token availability. Desktop wiretap mode reads local Discord Desktop artifacts and

…