Eight parts. One system.
Tunc Hub is where people and AI work. BOTs and the CLI extend it beyond the app. CLM, Art and Orb keep what the work leaves behind. Tunc Intent tells the AI what each request needs, and Tunc Core connects all of it and applies your rules.
Tunc Hub
Tunc Hub is where the work happens. Invite people into the same AI chat, watch the AI work step by step, and approve the steps that matter. Every shared chat runs on the host's computer and the host's chosen model.
- Multiplayer chats
- Type /invite with an email and a role. Viewers can watch but can't type or press Stop; hosts can remove anyone.
- You choose how much it asks
- Three permission modes, Auto, Plan and Bypass, decide when the AI shows a plan or waits for approval.
- Real tools and helpers
- Connect mail, calendars and the tools you already use through MCP connectors. One request can fan out to helper agents that work in parallel and check the result.
- Real files
- Attach up to 12 files per message. The AI reads PDFs and Office documents, and creates PDF, Word and Excel files.
Tunc Resident
A Tunc Resident is a BOT: Tunc's engine running as a background service on a computer you choose. It works on its own while the computer is on, and reports back through Tunc Hub.
- Local or remote
- Run a BOT as a background service on your Mac, Windows PC or Linux machine, or enroll a remote Linux server with tunc login --resident. Several BOTs can join one workspace, and one BOT can serve several.
- Delegate and get the answer back
- A chat hands the job to a BOT and goes quiet. When the BOT finishes, only the chat that asked wakes up with the answer.
- Schedules in plain words
- “Every weekday at 8, brief me.” The morning Brief reads mail and calendar and never sends anything. Missed runs are skipped, not piled up.
- Stays signed in
- Each BOT keeps its own key, tied to the person who set it up and to that install, so it keeps working when people sign in and out.
Tunc CLI
The Tunc CLI connects Tunc Hub to the rest of your systems. tunc exec runs one AI turn on the same engine as the app, so scripts, schedulers and other programs get the same models, tools and memory your team uses.
- One command
- Pass a prompt as an argument or on standard input from a shell script, a cron job or another program.
- Answers programs can read
- Choose plain text, one JSON document, or a stream of JSON events.
- Lands in the right place
- Point it at a workspace and chat, or continue the last session, so a nightly report shows up where the team already looks.
- Safe for unattended runs
- It never waits for a person. Anything the rules don't allow is denied, and you can narrow the tools for each run.
- Runs your BOTs too
- tunc daemon installs and manages a BOT as a background service on the same machine.
Tunc CLM
CLM (Continuity Log Memory) is how Tunc remembers. Each workspace gets its notebooks on day one. The AI opens them when a question needs history, and saves an entry only when something durable changed.
- Ready before you are
- A new workspace creates its notebooks automatically and never overwrites one that already has content.
- A note to the next AI
- Each notebook keeps the current state, one entry per session, a handover note and a signed roll call of every AI that worked on it.
- Readable by people
- Notebooks are plain text in the project folder. Any model can read them, so changing models doesn't reset the project.
- An open format
- CLM/3.0 is a public spec with reference parsers on PyPI and npm.
Tunc Art
Tunc Art stores the work your AI finishes and shows it well. The AI puts a file on your Art shelf and hands you a short link. The original stays in the workspace.
- Built to view
- Images, video, audio and PDFs open in the page. Spreadsheets, decks and archives get an information card and a download button.
- Locked doors, not secret links
- Every visit is checked. Viewers sign in with Google, Apple, Microsoft or GitHub as the creator or a member of the chat.
- Outside sharing is yours
- Only the person who made the file can share it outside. The AI is blocked from those controls, and outside access expires on its own.
- Every version kept
- An edited file becomes a new file with a new link, so a link never changes under someone. Everything you've shared is listed in one panel.
Tunc Orb
Ask an AI to keep track of something and it usually writes a file on one computer. Tunc Orb gives that data a home in the cloud, readable by every agent on your account.
- Built into Tunc
- Your chats and BOTs read and write Orb data with built-in tools, the same way they read a file.
- Shared by your agents
- Hub chats in every workspace, your BOTs and outside agents all see the same store.
- Private by default
- Your store belongs to you. Other people, including people in your workspaces, can't see it.
- Short-lived access
- Chats, BOTs and outside agents get a 5-minute token from Tunc Core, then read and write Orb directly. Core never carries the data.
Tunc Intent
Tunc Intent is a tiny decision model we trained for business work. Before the main AI answers, it reads the request together with the earlier task and the actual results, and hands the AI a short note: what kind of work this is, which job it belongs to and which tools fit. When it isn't sure, it stays quiet and the AI decides.
- Trained on synthetic data
- Thousands of small-business scenarios, written and cross-checked by four AI model families. No customer conversation was used to train it.
- Precise when it speaks
- On fresh tests, its tool suggestions are right 93% of the time. It only speaks up when it is confident.
- Knows where you are in the work
- It tells a new request from a follow-up, a correction or a stop, so withdrawn work stays withdrawn.
- Speaks small business
- It recognizes everyday jobs such as quotes, invoices, payment reminders, review replies, staff schedules and reservations.
- Points at the right tools
- It weighs 24 capabilities, from PDF and Excel files to email drafts, calendar, research, schedules and BOTs, and suggests only tools that are actually available.
- Tiny, local, advice only
- About 5 MB, compiled into the app and run on the CPU of your computer or phone. It never sends, books, installs or grants permission; your approvals and company rules still decide.
Tunc Core
Tunc Core routes every message between people, devices and BOTs, and it is where company rules live. It contains no code that calls an AI model: the AI runs on your computers.
- Live, everywhere
- Guests' messages reach the host's app, and the AI's work streams back to everyone in the chat as it happens.
- Team rules
- Admins decide which models, tools, skills, connectors and permission rules apply across the organization. Memory tools can be switched off by policy, and sharing changes are written to the company audit log.
- Teams and invitations
- Invitations, roles and workspaces live here, so a new person lands in the right place on first sign-in.
- Previews, not originals
- Core keeps cleaned previews of shared work. The original files stay on your computers.
- Small on purpose
- Core coordinates and never runs the AI, so it stays lean: about 213 MB of memory on a normal day.
Bring your team's AI work into one place.
Tunc Hub is free to start, and guests join free. Rolling it out across a company? Tell us how your teams work and we'll help you set up workspaces, rules and BOTs.
Or write to hello@tunc.ai