TUNC.AI
All posts
TUNC.AI

Tunc Art and Tunc Orb, built into Tunc Hub

Finished files get a private link. The data your agents keep gets a private store. Inside Tunc Hub, both just work, with your rules and your approvals.

Tunc ArtTunc OrbTunc Hub

Most AI work leaves two kinds of things behind. There are finished files: a report, a spreadsheet, a deck, a video. And there is the data an agent keeps while it works: a list of handled emails, a checkpoint, a customer record. Tunc Art holds the first. Tunc Orb holds the second. Inside Tunc Hub, both are built in.

What goes where

Tunc teaches its AI a simple split:

  • Tunc CLM keeps the why: decisions, lessons and a note to the next AI.
  • Tunc Orb keeps the what: records, logs of handled items and resume points.
  • Tunc Art keeps the files: finished reports, spreadsheets, decks and media.

Each kind of knowledge lands in the right place, so a project stays readable for months.

Tunc Art in Tunc Hub

When the AI finishes a file in a Tunc Hub chat, it puts it on your Art shelf and hands you a short private link. The original stays in your workspace.

  • Every visit is checked. Viewers sign in with Google, Apple, Microsoft or GitHub, as the person who made the file or a member of the chat it came from. Knowing the link isn't enough.
  • Only you share outside. The person who made a file can turn on outside sharing, with a password that is shown once and works for up to seven days. The AI is blocked from these controls.
  • Every version kept. An edited file becomes a new file with a new link, so a link never changes under someone.
  • One place for everything shared. The Art panel lists your shared files with their size and expiry, so you can copy a link, change sharing or delete a file. Deleting stops the link; the original on your computer is untouched.

Tunc Orb in Tunc Hub

Ask an AI to keep track of something and it usually writes a file on one computer. In Tunc Hub, your chats and your BOTs have four built-in tools instead: data_read, data_write, data_delete and art_read. They keep named records and append-only logs in your Orb, and every agent on your account sees the same store.

  • BOTs keep their place. An inbox BOT logs every message it handled and saves a checkpoint. The next run picks up where the last one stopped, on the same computer or another.
  • Chats know what is there. The AI sees a short summary of what your agents have stored, refreshed after every write, so it reads before it asks you again.
  • Your rules still apply. In Plan mode the AI cannot write. Company policy and your approvals stay in charge. Uploading a credential file, such as an .env file or a key, always asks first, and unattended jobs never upload local files.
  • Private by design. Tunc Hub trades your sign-in for a token that lasts five minutes, then reads and writes Orb directly. Tunc Core decides who may connect and never carries the data. People in your workspaces can't see your store.

One account, one allowance

Tunc Hub, Tunc Art and Tunc Orb use the same Tunc account. The free plan includes 1 GB of storage, shared by Art and Orb.

Coming to every agent

For now, Tunc Art and Tunc Orb work through Tunc Hub. Next, they open to every agent: sign-up at tuncart.com and tuncorb.com, and agent access through MCP, A2A and a REST API, are coming soon, so the agents you already use can keep their files and data with Tunc too.

Get Tunc Hub to use both today, or see the whole platform at tunc.ai/platform.