syne

Minimum Requirements

---

Verify Installation

syne repair     # Diagnose: DB, OAuth, Telegram, abilities
syne status     # Quick status check

---

Setup

On the server (one-time): ```bash

Gateway is built into Syne — no extra setup needed

Setup & Running

syne init # Interactive setup (fully automated) syne start # Start Telegram agent syne start --debug # Start with debug logging syne cli # Interactive CLI chat (resumes per-directory) syne cli -n # Start fresh conversation (clear history) syne cli --yolo # Skip file write approvals (auto-yes) syne status # Show status syne repair # Diagnose and repair syne restart # Restart agent syne stop # Stop agent

🚀 Quick Start — 3 Commands

git clone https://github.com/riyogarta/syne.git
cd syne
bash install.sh

That's it. install.sh is fully automated:

When install finishes, Syne is running.

Example: allow public to search Al-Quran and Hadith memories

Set config memory.public_categories to ["alquran","bukhari","muslim","fiqih"] ```

When a public user searches memories, results outside the allowed categories are silently filtered — they appear as if they don't exist.

No Runtime Config Files — Just Talk

Most agent frameworks require editing SOUL.md, AGENTS.md, or CONFIG.yaml to change behavior. Syne has none of that — all runtime behavior lives in PostgreSQL, and you change it through conversation:

Fresh install comes with sensible defaults. Override anything through conversation — no SQL, no files.

---

Configuration Reference

All configuration lives in the config table. Change via conversation or update_config tool.

Provider Settings

Memory Settings

Session Settings

Claude OAuth (Optional)

Exec & Web Settings

Sub-agent Settings

---

Node CLI Commands

syne node init           # Pair with server
syne node start          # Start node daemon
syne node stop           # Stop node daemon
syne node restart        # Restart node daemon
syne node status         # Show connection status

---

Ability Interface

class Ability:
    name: str
    description: str
    version: str
    permission: int = 0o700  # 3-digit octal (owner/family/public)

    async def execute(self, params: dict, context: dict) -> dict: ...
    def get_schema(self) -> dict: ...
    def get_guide(self, enabled: bool, config: dict) -> str: ...
    async def ensure_dependencies(self) -> tuple[bool, str]: ...

CLI Commands

```bash

Document Workflows

The pdf and office abilities together cover most document workflows. Both auto-extract content when a user uploads a file via Telegram — the LLM sees the document content as plain text without needing any tool call.

Examples (LLM-callable):

office(action='create_docx', title='Laporan', content='# Ringkasan\n\nIsi paragraf.')
office(action='create_xlsx', sheets='[{"name":"Q1","headers":["Item","Total"],"rows":[["Gaji",10000]]}]')
office(action='create_pptx', title='Proposal', slides='[{"title":"Slide 1","bullets":["A","B"]}]')
pdf(action='make_from_text', title='Doc', text='...')
pdf(action='read_from_url', url='https://example.com/file.pdf')

---

Auto Capture vs Manual

With Ollama as both evaluator and embedding provider, auto-capture costs $0 — both run locally.