—memory

Switches the log source to memory — logs that have been saved permanently when an issue was created. Memory logs survive your plan’s log retention window and are accessible indefinitely.

Syntax

--memory

Examples

--memory
--memory --count
message:"payment failed" --memory
level:error --memory --top:context.errorCode

What memory contains

When you create an issue via --task:jira|linear|github, Loguro saves the associated log(s) to a permanent memory store. These logs are not subject to retention expiry — they live forever.

Additionally, any future log with a similar message pattern is automatically linked to the same issue and also written to memory.

Combining with filters

--memory is a source switch, not a filter — combine it freely with level, message, context, and time filters:

level:error context.gateway:stripe --memory --count
message:"DB timeout" --memory @last-30d

See also

• Memory & Forever Logs — how pattern deduplication works
• —task — how logs get written to memory

Notes

• Only logs associated with created issues (and their pattern-matched siblings) appear in memory
• Memory results are fetched from a separate Parquet store, not the live log pipeline
• Scope: advanced filter bar
• Executes on submit