Struct RecallScope 

pub struct RecallScope {
    pub namespaces: Option<Vec<String>>,
    pub since: Option<String>,
    pub tier: Option<String>,
    pub limit: Option<u32>,
}

v0.7.0 (issue #518) — operator-configured recall defaults. Each field is optional; when present and the inbound recall request omits the corresponding axis AND passes session_default=true, the handler splices in the configured value before dispatching to the storage layer.

Resolution: explicit request args > recall_scope defaults > compiled defaults. The splice never overrides an explicit filter — operators can always narrow the result set further at call time.

Wire format:

[agents.defaults.recall_scope]
namespaces = ["projects/atlas"]   # default namespace filter
since = "24h"                     # duration → since = now() - 24h
tier = "long"                     # "short" / "mid" / "long"
limit = 50                        # default cap

Fields

namespaces: Option<Vec<String>>

Default namespace filter applied when the request omits its own namespace field. The current recall handlers accept a single namespace per call; when multiple namespaces are configured we apply the first one. (The list form is future- compatible with a planned multi-namespace recall surface.)

since: Option<String>

Default time-window applied when the request omits since. Expressed as a duration string: "24h", "7d", "30m", … See parse_duration_string for the parser. The handler resolves it to now() - duration at request time and passes the resulting RFC3339 timestamp through the existing since filter — no new SQL path.

tier: Option<String>

Default tier filter applied when the request omits its own tier. Accepted values: "short" / "mid" / "long". The sqlite recall handlers do not currently expose a tier parameter, so this knob is applied on the postgres SAL path (which carries a Filter.tier) and stored on the request envelope for forward-compatibility on sqlite (no observable behaviour change there).

limit: Option<u32>

Default recall limit applied when the request omits its own limit. The handler still clamps to the per-tool maximum (50) after applying this default, so an oversized value here degrades gracefully.

Trait Implementations

impl Clone for RecallScope

fn clone(&self) -> RecallScope

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for RecallScope

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for RecallScope

fn default() -> RecallScope

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for RecallScope

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Serialize for RecallScope

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.