varynth 0.1.1

Varynth local coding workspace with a TUI, secure tools, MCP, goals and an operator dashboard
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57

//! Channel adapters (Telegram / Discord / WhatsApp) land in v2.
//! v1 exposes the trait and a dashboard-as-channel so the web UI
//! already speaks the same inbound/outbound contract.

use serde::{Deserialize, Serialize};

#[derive(Debug, Clone, Serialize, Deserialize)]
pub struct Inbound {
    pub channel: String,
    pub sender_id: String,
    pub chat_id: String,
    pub text: String,
}

#[derive(Debug, Clone, Serialize, Deserialize)]
pub struct Outbound {
    pub chat_id: String,
    pub text: String,
}

pub trait Channel: Send + Sync {
    fn name(&self) -> &'static str;
}

pub struct DashboardChannel;

impl Channel for DashboardChannel {
    fn name(&self) -> &'static str {
        "dashboard"
    }
}

pub fn v2_status() -> serde_json::Value {
    let cfg = crate::config::Config::load().ok();
    let tg = match &cfg {
        Some(c)
            if c.telegram_bot_token
                .as_ref()
                .map(|t| !t.is_empty())
                .unwrap_or(false) =>
        {
            if c.telegram_allow_from.is_empty() {
                "token set, pairing (empty allowlist)"
            } else {
                "live"
            }
        }
        _ => "off — set VARYNTH_TELEGRAM_BOT_TOKEN or ~/.varynth/telegram.env",
    };
    serde_json::json!({
        "telegram": tg,
        "discord": "planned",
        "whatsapp": "planned",
        "dashboard": "live",
        "note": "Telegram polls when `varynth serve` runs. Use a dedicated bot token — do not share a token with another bot or app (409 Conflict). Allowlist: telegram_allow_from in ~/.varynth/config.toml"
    })
}