steeldb/agent/
types.rs

1//! Neutral message/tool types the agent loop speaks. Each provider translates these to/from its own
2//! wire format (Bedrock Converse blocks; OpenAI/Paddock chat messages).
3
4use serde_json::Value;
5
6#[derive(Clone, Copy, Debug, PartialEq)]
7pub enum Role {
8    User,
9    Assistant,
10}
11
12#[derive(Clone, Debug)]
13pub enum Block {
14    Text(String),
15    /// model asked to call a tool
16    ToolUse { id: String, name: String, input: Value },
17    /// our result for a prior tool call
18    ToolResult { id: String, content: String, is_error: bool },
19}
20
21#[derive(Clone, Debug)]
22pub struct Msg {
23    pub role: Role,
24    pub blocks: Vec<Block>,
25}
26
27impl Msg {
28    pub fn user_text(s: impl Into<String>) -> Msg {
29        Msg { role: Role::User, blocks: vec![Block::Text(s.into())] }
30    }
31}
32
33/// A tool the model may call — a JSON-Schema `input_schema` plus a name/description.
34#[derive(Clone, Debug)]
35pub struct ToolSpec {
36    pub name: String,
37    pub description: String,
38    pub schema: Value,
39}
40
41#[derive(Clone, Copy, Debug, PartialEq)]
42pub enum Stop {
43    EndTurn,
44    ToolUse,
45    Other,
46}
47
48/// One provider response.
49#[derive(Clone, Debug)]
50pub struct Turn {
51    pub text: String,
52    /// (id, name, input) per requested tool call
53    pub tool_uses: Vec<(String, String, Value)>,
54    pub stop: Stop,
55}
steeldb/agent/types.rs

steeldb/agent/
types.rs
