Team

A team space like Slack, separate from AI chat. Sign-in is required.

One team per project. The Team tab shows only the team attached to the current project; switch to another team’s project to see it. A project without a team is just for you — keep material you won’t share with a team in a project without one.

Messages and files are not kept on the server

The original of every message and file stays only on the writer’s device; the server only remembers order and addresses. To receive a message, the writer’s app (or the app of a teammate who opened that room and holds a copy) must be online. While it is offline you see “The author is offline”, and it fills in once they come online.

Getting started

In a project without a team, open the Team tab → “Create or join a team” → “Create team” or “Join with a code”. The team is attached to the current project; a project that already has a team can’t take another.
Owners and admins make invite codes in the Team panel (only the owner gets the Admin/Member role picker); a code is shown only once.
At the bottom of the Team panel are “Connection status” (a team connection check) and “Leave team” (everyone but the owner); member rows show “Remove” if you have the right.
Exchanged pictures and files are saved in the team’s project Files tab under team/channel name/ (team/전체/ for All). A channel named “전체” or market gets the folder “전체 채널” or “market 채널” — team/market/ is the team market (units and workflows). Files received earlier stay under chat/room name/. “This team’s project” in the Team panel moves the team to another project that has no team.

Dashboard and All

“Dashboard” at the top left is the team announcement room “All”. It isn’t a channel and each team has one. Only owners and admins post — members see a note instead of the input box. No threads or tags.
Channels with new messages gather at the top of the dashboard; click one to go there.
“Online now” at the bottom left lists members whose app is on (you first). Click one for the profile. The team-shaped button on that line opens the team panel (members, invites, you in this team).

Channels and threads

Create a channel with “+ Channel” on the left. “Start thread” on a message starts a side conversation (thread) from that point; move between them with the path at the top. The speech-bubble button “New thread” on the header opens one without a message. Threads can have threads of their own.
The list on the left shows channels only. “Threads N” in the channel header lists every thread in the channel where the chat was, most recent first — search by title or message (Enter opens the top one); deeper threads show their parent threads in front. Click one to open it. A channel row shows the head count when a meeting is on anywhere in it.
You can edit or delete your own messages and tag any message. Hover a message for “More” → “To to-do” (one line in “My to-dos” in the To-do tab; long text goes into the note) · “Ask in chat” (a new chat input quoting that message).

AI threads (#ai)

Put #ai in a message (typing # shows a roster that includes “ai” — not inside a meeting) and an AI thread starts from it with the AI’s answer. The answer is made on the sender’s device and account.
The AI reads the message, the thread before it (last 30 messages) and the AI thread itself, and searches and reads documents or the web when needed (say “put ‘X = Y’ in the team glossary” and it adds it to the team glossary team/전체/용어집.md) — within the asker’s Settings → Secure share “Files the team AI may read” (default: team files only), because the answer is posted to the team channel.
Anyone can ask follow-ups in an AI thread — each message is answered by its sender’s device. AI threads can’t have threads under them.
When something is worth keeping, the AI writes a note (md) in the channel folder (team/channel/) as a team file and updates it with later answers (new versions). Click “Note” under an answer to open it. If someone has the note open for editing, the AI leaves it alone.

Meetings

The camera button “New meeting” on a channel or thread header → enter a name to create a meeting under it and join right away. Meetings can’t have threads under them, and can’t be made under All or an AI thread.
Opening a meeting shows “In a meeting · n min · who is here” and “Join” (“Start meeting” when nobody is there). On the left, meetings appear under their thread row with a dot and head count while a meeting is on.
You join with only the mic on. The left side is the meeting (people, shared screen, mic, camera, screen share, leave); the right side is that meeting’s chat as usual — messages and files from the meeting stay in it.
The meeting continues when you switch tabs. Click the meeting bar in the header (name, time, people) to come back; you can also mute or leave from the bar. Closing (hiding) the window keeps it going; quitting the app leaves.
A meeting holds up to 6 people. Audio, camera and screens go device to device and are never stored. Only the “Meeting started” and “Meeting ended · duration · attendees” lines remain.
After a meeting, “Write minutes” has the AI write minutes from the messages exchanged in that meeting and keep them as a team note (md) in the channel folder. Audio is not transcribed.
The first time you join, macOS asks for the microphone (and the camera when you turn it on). If you decline, you can only listen.

Writing

Enter sends, Shift+Enter adds a new line.
# person — typing # shows the team roster; picking someone inserts #name. That person sees the message marked and gets a notification in the header bell.
@ file — typing @ finds a Files tab document and attaches it right away (fully private files are refused — mark them shareable in the Files tab first). The “Attach” button attaches files from disk, and pasting attaches pictures. Dragging a file from the files drawer onto the input attaches it the same way as @.

Unread messages

The dashboard and channel list show unread counts and the sidebar Team icon shows the total; a different color means someone mentioned you. Whatever you are looking at is marked read. Clicking a notification from another project’s team switches to that project first. Read positions are kept per device.

Team files

The Files tab “Team” is the team file list. A personal file moved with “Move to team files” shows up in every teammate’s list, and each person downloads it when they open it. Not even the person who moved it can take it back as a personal file.

When your edits are not on the team yet, the file row shows “Needs sync”. Team files you edit in the app (as the co-editing host) go up as a new version of the same file during a short pause and when you close them. Edits that didn’t make it because the app quit go up the next time you open the file; for changes saved in another program (AutoCAD, Excel, etc.), right-click → “Sync”. The true version of a team file is the one from whoever edited it last (the host). If the team got a different newer version in the meantime (you edited an older one), opening the file or “Sync” fetches it and tries to merge your edits in — text formats (md, txt, json, yaml, csv, …) line by line; if both changed the same lines, they aren’t merged. If the merge fails, you are the next host, so your version becomes the new one. But if someone already has the file open and is editing it, you follow their version and your edits are overwritten. To upload a separately edited file as a new team file, right-click → “Version up…” (name_v2; teammates are asked to delete the old one).

Team files are copies on each person’s device, so you cannot delete them on someone else’s device. Right-click a file row → “Delete…” → “Only on this device” or “Delete and ask the team”. Each teammate then answers yes or no in the To-do tab, and the file is deleted only on the devices of those who say yes. When everyone says yes, the file also leaves the team file list (once the asker’s app is running). Deleting again sends a new request. Sent requests and their answers are in the To-do tab too (“Waiting” column).

Posting a team file to a channel again doesn’t copy it. Pick a team file with @ or “Attach” in the composer, or right-click a file row → “Share to channel…”, and a chip pointing to that team file is attached. The chip shows whether your copy is Latest, Old version, Needs sync or Not here yet; clicking it gets and opens the team file’s current version. File rows also show “Old version” when a newer one exists — right-click “Get latest”.

“Team files not received yet” lists only what you actually need: files you already have under another name, old files replaced by a version-up, and files you asked to delete or said yes to deleting are left out.

Profile

Click an author’s face or name, or “View profile” on a member row in the team panel, to open a profile (photo, name, role, online). On your own profile you can change or remove your photo and change the name you use in this team. One photo per account, so it shows in every team you’re in. Without a photo, the first letter of the name shows.

Editing together (pptx · Excel · text files)

When you open a team pptx, Excel (xlsx, csv) or text file (md, txt, json …), the device that opened it first becomes the host; people who open it later each see the same file on their own screen and edit it (on different slides if they like). Edits are applied on the host’s device and reach everyone right away. The editor header shows a HOST tag (my device holds the file) or GUEST (joined someone else’s device) and a team button. The button turns on when someone is editing with you; click it for the list of faces (click one for their profile).

When the host closes it, the person who has kept up the most takes over; if the host drops off suddenly, someone still editing takes over within about a minute.
While editing together you can’t insert pictures from a file (pasting works), and “restore the original” is blocked.
In a pptx, undo (⌘Z) and redo only touch your own edits — other people’s stay. If someone changed the same slide after your edit, it isn’t undone and you’re told that someone else changed that slide afterwards. Edits you made alone before others joined can’t be undone while you’re editing together.
In Excel and text files your edit shows on your screen first and is lined up in the host’s order. If two people change the same Excel cell at once, the sheet is re-synced to the host’s copy a moment later.
The host’s device saves automatically. In a text file, people who joined later see “Edits are saved on the host teammate’s device” instead of a Save button.
Hangul (hwp) files and PDF stamps are edited one person at a time. While someone is editing you see “X is editing” and editing is blocked. Saving makes a new version and others see “A newer version is available · Reopen”. After 10 minutes without activity the lock is released for others.
If your copy differs from the team version, there is nothing to choose — an old copy gets the new version and reopens; if it has your edits, you are the next host when you start editing, so your version becomes the new one (if someone else is editing, wait until they finish).
The AI doesn’t edit team files (it writes only the team notes its AI threads made and the team glossary).

Receiving files

Pictures up to 20MB arrive with the message automatically. Larger pictures and other files have a “Download” button.
A file is asked from the writer first; if they are offline, a teammate who already downloaded it sends it. If one source drops, the next one continues from where it stopped. A copy someone has edited is never used. If everyone who has it is offline you see a failure message. Open a received file with “Open” in the Files tab.