TesseractEngineering
Tesseract དྲ་དེབ་ནང་ ༢༠ བརྩམས་ཡིག་ཡོད།
- How an AI agent decides a command is too risky to run How Tesseract checks an agent's shell commands and file writes on 14 frameworks: 13 rules, a second opinion that can only raise, and what happens next. · ལྷག་ནི་ལུ་ 15 སྐར་མ།
- How AI agent tasks survive an app restart What happens to an agent's turn when the app restarts mid-task: liveness clocks, an on-disk turn record, dev server cleanup and conversation recovery. · ལྷག་ནི་ལུ་ 13 སྐར་མ།
- How one chat drives 14 AI agent frameworks the same way The agent contract behind Tesseract: three integration routes, 32 capability flags, tools the app serves itself, one event stream, and how each tool reaches the model. · ལྷག་ནི་ལུ་ 15 སྐར་མ།
- Updating an app without stopping its AI agents How Tesseract ships updates in kilobytes and applies them only when nothing is running: risk tiers, signed deltas, idle checks and automatic rollback. · ལྷག་ནི་ལུ་ 10 སྐར་མ།
- How an AI agent builds a PowerPoint deck: our design How Tesseract turns one sentence into a researched deck with speaker notes and a PowerPoint download: the pipeline, the tricks, the numbers and the results. · ལྷག་ནི་ལུ་ 12 སྐར་མ།
- How an AI makes a real font, and a brand kit around it How Tesseract turns a style prompt or your handwriting into an installable font, and one logo into a full brand kit: the pipeline, the checks, the kit. · ལྷག་ནི་ལུ་ 11 སྐར་མ།
- How Tesseract edits a PDF without breaking it Tesseract's PDF editor annotates, retypes, fills, signs and redacts. How saves keep the original bytes, why redaction rewrites, and what the agent can do. · ལྷག་ནི་ལུ་ 10 སྐར་མ།
- How an AI agent edits Word and Excel files in Tesseract Tesseract's Word and spreadsheet editors run every click, key and agent request through one command table. How that works, what it saves, and how it checks itself. · ལྷག་ནི་ལུ་ 10 སྐར་མ།
- How an AI game maker builds a game you can play at once Inside Tesseract's game maker: a design you approve, a browser game or an engine project, played beside the chat and tested by a headless checker. · ལྷག་ནི་ལུ་ 10 སྐར་མ།
- How an AI data analyst shows every change to your data Inside Tesseract's data maker: a first look at your file, a plan you approve, a re-runnable script, charts from its output and every change listed. · ལྷག་ནི་ལུ་ 10 སྐར་མ།
- How an AI research agent plans, cites and checks its work Inside Tesseract's research maker: a plan you approve, a checklist the agent ticks, a citation ledger, a coverage check and a report written from evidence. · ལྷག་ནི་ལུ་ 11 སྐར་མ།
- What is inside an AI assistant you make in Tesseract How Tesseract's assistant maker turns one sentence into a charter, a schedule, a first brief with no sign-in and rules that hold on every run. · ལྷག་ནི་ལུ་ 10 སྐར་མ།
- How the app maker checks a real app against its demo How Tesseract's app maker turns a tappable demo into Flutter, React Native or SwiftUI, then reads every built screen to prove it matches what you approved. · ལྷག་ནི་ལུ་ 9 སྐར་མ།
- How the website maker keeps, checks and publishes a site What happens to a site after Tesseract's website maker drafts it: the files it lives in, how edits reach the code, how it is checked and how it goes out. · ལྷག་ནི་ལུ་ 11 སྐར་མ།
- Present a deck live: notes, a phone remote and an AI How Tesseract runs a live talk: a presenter view with notes and a timer, your phone as the remote with no pairing, and an assistant that moves slides. · ལྷག་ནི་ལུ་ 11 སྐར་མ།
- How Tesseract generates images, transparency included How the agent makes pictures in the chat: your provider setting, four at a time, files kept with the session, and a real transparent PNG from any model. · ལྷག་ནི་ལུ་ 9 སྐར་མ།
- How a team chat app on your phone decides when to buzz How Atrium on the phone notifies only for messages you haven't seen, rings like a real phone call, and catches up after a lost connection. · ལྷག་ནི་ལུ་ 8 སྐར་མ།
- How a phone app steers AI agents on your computers Why the Tesseract phone app never runs an agent itself, how it stays connected through sleep and network changes, and which events reach your phone. · ལྷག་ནི་ལུ་ 10 སྐར་མ།
- How the Tesseract apps connect: one system map Desktop, web, CLI, Companion, Atrium, Remote Desktop and Mesh: which runs agents, what goes through the server, what goes direct, and what syncs. · ལྷག་ནི་ལུ་ 11 སྐར་མ།
- We make complex things simple. Here's what's underneath Five things that take one sentence in Tesseract, and the engineering behind each: 14 agents in one chat, memory, computers by name, agent teams, decks. · ལྷག་ནི་ལུ་ 12 སྐར་མ།