Struct Chats 

pub struct Chats { /* private fields */ }

A conversation store on disk.

Implementations

impl Chats

pub fn open() -> Self

The operator’s conversations, <home>/chats.

pub fn at(root: PathBuf) -> Self

A store at an explicit root. Tests use this, which is why none of them need the operator’s real home.

pub fn root(&self) -> &Path

Directory holding the conversation files.

pub fn path_of(&self, id: &str) -> PathBuf

Path for one conversation id.

pub fn artifacts_of(&self, id: &str) -> PathBuf

Where one conversation’s prompts and CLI output are kept.

Beside the record rather than inside it, with the same stem convention a run’s nodes use, so a conversation that went wrong can be read back turn by turn - which is the only way to tell “the agent said nothing” apart from “magi never asked it”.

pub fn attachments_dir(&self, id: &str) -> PathBuf

Where this conversation’s attached images live: a subdirectory of artifacts_of, so deleting the conversation deletes its attachments too and nothing here needs its own cleanup path.

pub fn put_attachment( &self, id: &str, mime: &str, name: &str, data: &[u8], ) -> Result<Attachment>

Persist one already-validated attachment and return its metadata.

web::chat_attachment_post is the only caller: it has already checked mime against the whitelist and sniffed the bytes, so an unrecognised mime reaching here is a bug in that caller, not something an operator did. The id is minted here and never taken from the client; name is stored for display only and never used to build a path.

pub fn attachment_meta( &self, id: &str, att_id: &str, ) -> Result<Option<Attachment>>

Just the metadata, without reading the image bytes back off disk - what web::chat_say uses to turn an id the operator referenced into an Attachment before appending a Turn, where the bytes themselves are of no interest. None for an id this conversation never stored - including one that merely looks plausible: valid_attachment_id is checked here too, not only by the caller, the same defence-in-depth Questions::panel_asset uses for its own asset ids.

pub fn read_attachment( &self, id: &str, att_id: &str, ) -> Result<Option<(Attachment, Vec<u8>)>>

A stored attachment’s metadata and its bytes together, for serving it back on GET. None under the same conditions as Chats::attachment_meta, which this is built on.

pub fn put(&self, c: &mut Chat) -> Result<()>

Write a conversation, atomically, so a process killed mid-write leaves the previous state readable rather than a truncated file that would lose the whole interview.

pub fn get(&self, id: &str) -> Result<Chat>

Load a conversation by id or unambiguous id prefix.

pub fn list(&self) -> Vec<Chat>

Every conversation on disk: open first, then newest first.

Open first because that ordering is the product - the list exists to show the operator what is still being talked through, and a filed interview is history underneath it. Unreadable files are skipped rather than fatal: one corrupt record must not take the web UI down, and must certainly not hide the open conversation the operator came back for.

pub fn resolve_id(&self, prefix: &str) -> Result<String>

Expand an id prefix to exactly one conversation id. The short id the phone shows is a suffix, so that is accepted too.

pub fn revision(&self) -> u64

Newest modification time in the store, in milliseconds, for change detection. The web UI compares this instead of re-reading every conversation, so an idle phone on a slow link costs one stat per file.

pub fn count_open(&self) -> usize

How many conversations are still open. The badge on the phone.

Trait Implementations

impl Clone for Chats

fn clone(&self) -> Chats

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for Chats

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

Formats the value using the given formatter.