Sente

Sente is teai.io's official coding agent CLI, described as a thin launcher over OpenCode (MIT, 203k GitHub stars). One curl line installs it, and every teai.io model becomes an agent in your terminal. It is built for people who work in a repository rather than a chat window: Sente reads and edits the files in your repository, runs commands, and reports back. It sits in the teai.io CLI family alongside te, which you type at, and fuseki, which watches without being called. Sente itself is free; usage is metered through teai.io credits, and the site states the limits honestly rather than promising unlimited use. The starting point is the gap between a chat app and an actual working agent. A chat interface can answer questions, but it cannot reach into the files in your repository, run commands on your machine, or report back on what changed. Sente is built to remove that gap, and to do so without a conversion layer: teai.io is natively OpenAI-compatible, and Sente, being OpenCode-based, speaks OpenAI-compatible natively, so tool calls travel through teai without a translation step — zero conversion layer, nothing to break when routing through teai. The other half of the problem is trust and cost: agents fail, retries multiply, and metered usage can feel opaque. Sente's answer is billing that ignores empty responses and refunds failed paid media jobs and failed MCP tool calls, plus a safety model that asks before anything destructive. Sente is deliberately not a fork. The install is one line — curl -fsSL https://teai.io/te | sh — which installs OpenCode if it is missing and points OPENCODE_CONFIG at a teai.io-generated config. On each launch Sente syncs the teai.io model catalog, so upstream OpenCode improvements arrive without the project having to maintain a diverged codebase. A coding discipline file, sente-rules.md, is auto-written to ~/.config/teai/ and injected into every session, mechanically enforcing rules such as read before you write and always ship a deliverable. The command is short — te — and a sente alias is also installed. Setup continues with te login using a free API key obtained at registration. Sente exposes 380+ models on a single account and makes switching a one-line affair. The daily driver is glm-5.2 at roughly ¥0.34 per task; quality-critical work routes through te lux to the Claude/OpenAI flagship (Fable 5); hard tasks use te max on Kimi K3 (2.8T, 1M); and DeepSeek V4 Pro comes in around ¥0.03 per task. One base_url decides routing, which is how the product aims to stay cheap without breaking quality, and a task is measured as approximately 1K input plus 500 output tokens. Because the endpoints are OpenAI- and Anthropic-compatible, existing tooling patterns carry over, and the API-compatible endpoints never store request bodies — only metadata, kept for 90 days. Voice is a first-class input. te talk starts a voice conversation: you say what you want done and Sente reads its reply back to you, on macOS, Linux and WSL. Enrollment takes about one sentence — roughly ten seconds — and is consent-first: the delete key is yours, and teai.io states that it never clones a voice that isn't yours. For work that outlasts a laptop session, Sente Cloud at sente.teai.io runs in your browser on a cloud workspace; you sign in with an emailed one-time code, and closing your laptop doesn't stop the work. Optional GUI apps are installed explicitly with te app install sente for a menu-bar Sente.app, te app install koe for an always-listening Koe.app, or te app install both, and they are placed in /Applications only when you run that command. Safety is expressed as a three-tier risk model shared across the family: reads run automatically, writes are treated as reversible and proceed, and anything in the delete, send, publish or pay category asks first. fuseki, the third stage of the CLI family, is in Alpha and inherits the same tiers: it keeps an eye on your board — human-gates, recent repos — without being called, and only thinks and logs plus speaks a suggestion when something actually changes. It defaults to proposing only and never executes on its own; te stop stops it. The design intent is stated plainly: the agent moves before you do, but the risky moves still need you. Privacy is handled locally and is opt-in. te privacy scrub on masks emails, phone numbers, addresses, API keys, private keys and high-entropy tokens — plus names harvested from your Contacts dictionary with te privacy scrub harvest, Japanese honorific heuristics and Apple's on-device name recognition — on this Mac before the request reaches teai.io. The cost is about 0.1 ms per request with no local LLM required, and the reply is restored before it is shown. teai.io is explicit that this is not a guarantee of complete detection: Japanese given names without an honorific or a dictionary entry are not caught, and the optional Ollama layer (--llm) exists but is slow. Enterprise concerns are covered by invoice billing and a DPA, with BYOK in preparation. Five beta skills, announced for 2026-08, are backed by a reference corpus of 748 Q&A entries searched with lightweight retrieval — semantic embedding plus a relevance cutoff — before the model answers. te legal covers Japanese law with 259 entries across 21 topics and is cross-checked against actual e-Gov statute text, returning no match rather than fabricating; te security covers secure coding with 131 entries across 13 topics such as SQLi/XSS/CSRF mitigation, auth, secrets management and dependency vulnerabilities; te freelance covers 125 entries on contract checkpoints, Japan's invoice system, tax filing and social insurance; te infra covers 117 entries on Fly.io, Docker, CI/CD, SQLite/libsql, DNS and TLS, including real gotchas teai.io hit running this exact stack; and te license covers 116 entries on MIT/Apache/GPL-family licenses and AGPL's SaaS network clause. They are callable as te legal "question" or straight from the API by passing a model such as shitate/legal to /v1/chat/completions. The practical benefits are deliberately narrow and concrete. Nothing is billed for failure: empty responses are not billed, and failed paid media jobs and failed MCP tool calls are refunded in full, so you pay for results rather than errors. Cost control is explicit — cheap models for routine work, flagship routing for quality-critical work, and a maximum-performance tier when a task is hard — all switched with one line rather than a new subscription. Work continues while your Mac sleeps through Sente Cloud, discipline is enforced mechanically through sente-rules.md, and privacy scrubbing happens on-device before anything leaves the machine. Concrete workflows follow the same pattern. In a terminal you can run te run "explain this repo" for a one-shot explanation, ask te run "refactor this function" to edit code in place, or hand an agent a file generation task; switching to te max puts a hard task on Kimi K3. Away from the keyboard you can start te talk, describe the task out loud and hear the reply read back. For work that must keep going, Sente Cloud runs in the browser on a cloud workspace while the laptop is closed. Mid-implementation you can sanity-check risk with te security "how do I prevent SQL injection?"; outside code you can ask te legal about a statutory reserve share, te freelance how to register for Japan's invoice system, te infra how to set a secret on Fly.io, or te license what to watch for when using AGPL in a SaaS. Language settings also matter for Japanese and English users: /language (or /lang) switches the language dialog and skill list, /skills searches skills by display name, description or skill ID, and the initial language follows your terminal locale. Sente itself is free, and teai.io runs on credits. The Free plan gives 100 credits on signup with no credit card required — enough for roughly 300,000 short chats on Qwen3.7 Flash or about 2,000 on glm-5.2, at 1K input plus 500 output per task. Pro is ¥4,350 per month (about $29 USD) with 30,000 credits, and Business is ¥14,800 per month (about $99 USD) with 100,000 credits. Usage is metered rather than unlimited, and you top up monthly credits if you go over; invoice billing and a DPA are available, with BYOK in preparation. It runs on macOS, Linux and WSL (Windows through WSL), is Japan-built with a Tokyo region, JPY billing and Japanese support, and the source is MIT-licensed at github.com/yukihamada/sente. Documentation lives at teai.io/docs. Sente's proposition is narrow and consistent: one line to install, one account for 380+ models, three ways to call an agent — by typing, by speaking, or by letting fuseki watch — and a billing and privacy stance that refuses to charge for failures. For developers who want an agent inside their repository rather than inside a chat window, it is a thin, updatable, honestly metered layer over OpenCode.