We didn't seem to allow disableMemory in Browser.launch(), so I added that. We were also missing some documentation for it.
I did find that opts.disableMemory was true when passing --hdrDisable but not clear if that persists inside AgentBrowser, which appears to still hardcode memory stuff.
In general, I believe that it should be all or nothing: read-only memory index use shouldn't be possible in basic Nolita. So if you disable using memories you should disable writing memories at the same time.
Adds a help command with our commands, version, etc.
If we don't have a key we tell the user to use npx nolita auth, unless hdrDisable flag is passed, then we suppress the warning.
npx nolita auth pushes user to the dashboard, where they sign in with magic link (see PR in dash repo) and then procure a key, entering it in here.
hdrApiKey flags and env variables still work but we should basically discourage it in docs now. The auth flow is easier and compartmentalises it.
disableMemoryinBrowser.launch(), so I added that. We were also missing some documentation for it.opts.disableMemorywastruewhen passing--hdrDisablebut not clear if that persists insideAgentBrowser, which appears to still hardcode memory stuff.helpcommand with our commands, version, etc.npx nolita auth, unlesshdrDisableflag is passed, then we suppress the warning.npx nolita authpushes user to the dashboard, where they sign in with magic link (see PR in dash repo) and then procure a key, entering it in here.hdrApiKeyflags and env variables still work but we should basically discourage it in docs now. The auth flow is easier and compartmentalises it.