Kairo Crew, a new sidebar, and Coline Sites

This release covers everything since Coline 0.6.0 on web, Coline Desktop, and upstream.codes.

• Kairo Crew: Named agents with their own job, instructions, tools, and character. Give a crew member an ongoing goal or a routine, and it keeps the work going and comes to you only when it needs a decision.
• A new sidebar: Your crew, what needs you, and what’s in motion at the top, then pinned items, channels, and DMs. Apps live in a dock at the bottom.
• Kairo sees what you have open: Ask about the email, doc, file, or selection in front of you without pasting anything in. A chip above the composer shows what it will see.
• Kairo in Messages: Mention Kairo or a crew member in any channel, thread, or DM. Agents answer messages meant for them, work in the open, and hand code work to Coline Code.
• Integrations: Crew can work with Linear, GitLab, Sentry, PostHog, Vercel, Stripe, Shopify, Notion, Figma, and more, or any API you describe. Admins choose which crew may use each account.
• Memory and notebooks: Kairo keeps short, dated notes you can search, edit, and forget. Each crew member keeps its own notebook of decisions and unfinished work.
• Coline Sites: Any Coline app can publish a public website at its own coline.space address or on a custom domain, with sign in with Coline for visitors.
• Team trials: New team workspaces get 14 days free with no card, for up to 5 people.
• Coline for Startups: Six months of Workspace Pro + AI for up to 25 seats for eligible startups.
• Drive, tabs, and settings: A redesigned Drive with a folder tree, tab groups, and every workspace-wide setting in one place.
• Tab autocomplete everywhere: Inline suggestions in Docs, Notes, the message composer, task descriptions, and Calendar.
• Upstream: Much faster Git, a full diff viewer with no size limits, Kairo Review that follows the code across the repository, and a public API in alpha.
• Desktop for Windows and Linux: Windows, .deb, .rpm, and AppImage builds join the Mac build, and Meridian gets more of the browser basics.

The four sidebar tabs (Messages, Inbox, Kairo, and Apps) are replaced by one sidebar built around what is happening now.

• Kairo and your crew sit at the top. Open Kairo to start a chat or get to its chats and goals, or open a crew member to message it or view its profile. Add to crew is next to them.

• Needs you lists mentions, questions from crew, and notifications until you deal with them. Mark items read, save them for later, or open the full Inbox.

• In motion shows the conversations and chats where someone is working right now.

• Pinned items, channels, and DMs follow, with the same actions they had before.

• Apps live in a dock at the bottom of the sidebar.

Command-K now starts with Jump to, so you can go to a person, crew member, channel, or Kairo chat by name. The first time you hide the sidebar, a tip shows how to bring it back: press Command-B, or rest the pointer on the left edge to peek at it. A short tour walks through the new sidebar the first time you open 0.7.

Kairo now knows which app, item, and selection you have open when you message it. A “Looking at” chip above the composer shows what it will see; dismiss it to leave that item out.

• Open the Kairo sidebar with Command-period next to any app. On narrower windows it slides over the page, and side sheets such as task details open beside it instead of covering it.

• It works in Mail (including text you select in an email), Inbox, Drive, Notes, Docs, Sheets, Messages, Tasks, Calendar, Home, Meridian pages, Coline Code (the open file and selection), and apps built with the Coline SDK.

• Kairo checks that you can still open the item before reading it, and it never uses what you have open in shared conversations or background work.

• The sidebar suggests prompts for what you have open. On the full Kairo page, “Attach what’s open” in the + menu adds it to your message.

• Turn it off with “Share what you’re looking at with Kairo” in Account settings.

Mention Kairo in a channel or group conversation, or open a direct message with it. It can use Coline tools to help with the work you ask for, with a conversation that continues across follow-up messages.

• Agents answer messages meant for them even when nobody mentions them by name, including follow-ups and short answers to their own questions. People talking about an agent’s reply don’t wake it. A message to the whole room, such as “how’s everyone doing, including the crew”, gets an answer from every agent listening.

• Kairo answers where you asked. A question in the main chat gets its answer there; a question in a thread stays in that thread. Replies under the question or answer continue the same session.

• While an agent works, it shows as typing. Open the typing indicator to see its current phase, elapsed time, reasoning summary, and recent steps. Its answer appears as a normal message when it finishes. Follow-up messages can steer work already in progress.

• Stop a run from the agent’s Activity panel or with /stop. Use /status to check its state, or /aside to send a message the agent should leave out of its work and learning.

• Agents carry out requested actions without a separate approval prompt, unless a crew member’s owner has turned on a Never without asking rule. Sign-ins still need you, and Observe checks keep their read-only limits.

• Runs can recover after an interruption, and failed runs have a retry action. Longer runs you started pause at their limit and ask before continuing; routines and background checks finish at their limit instead.

• Workspace admins can pause Kairo, change its instructions, and review usage in Settings > Crew. Pause agents for a single channel from that channel’s settings.

When an agent links a doc, note, sheet, file, task board, task, event, channel, repository, issue, Change Request, goal, crew member, or email, the link shows as a card under the sentence that mentions it. Things an agent creates during a run show as cards even when the reply doesn’t link them. Cards only appear for things you can open. Agent replies can also include interactive charts and controls, and they remember where you left them.

Code work started from a thread shows as a card with its status and Open in Code; replying in the thread steers it. When one agent hands work to another, the thread says so, and an agent that needs a person posts a question card with choices. Channel settings can name a team crew member as the channel’s lead for thread work.

Any member can add team crew to a public channel by mentioning it. When asked to post or work in a public channel, a team crew member joins it on its own; a private channel still needs someone to add it. Posts, replies, reactions, tasks, and issues made during a crew run are credited to that crew member.

Kairo has an agent identity in the workspace and does not count as a paid member seat. Its work uses the workspace’s Kairo allowance, with notices to admins as usage reaches 75% and 95%.

In conversations shared with another organization, only members of the host workspace can ask Kairo to act. Its replies use context available to the people in that conversation.

The conversation work panel is gone. Discussions and Scheduled moved into the side panel, with a chip above the composer when messages are scheduled, and Pause agents moved to channel settings.

Add a crew member for a particular job, with its own instructions, tools, character, color, and writing voice. Start from scratch or from a template: Inbox chaser, Channel triage, Release notes, Customer follow-ups, Standup collector, or Research digest. Choose Just for me for private work or For the team for shared work. Kairo can also prepare a draft that stays a proposal until you confirm creation. A new crew member opens on its own conversation.

Your crew appears at the top of the sidebar, and each member opens in its own tab. The Crew page lists everyone, with All, Mine, Team, and Paused filters. A crew member greets you in a new conversation and asks what’s taking up your time, following up one question at a time about work it could take on.

Crew conversations read like a messaging app. Replies arrive as chat bubbles with a typing bubble while the member works, the conversation stays on the newest message, and you can start typing anywhere to reply. The header floats over the conversation and opens the profile as a panel beside it. Messages you send appear immediately, and your text comes back if sending fails. Older messages show their date, and reading a crew conversation marks it read. One-to-one DMs with a crew member can include charts and other visuals.

• A crew member’s profile brings together Goals, Activity, Computer, Memory, and About. Activity includes routines and recent check-ins. Open About to change its instructions, Always on, and the integrations it can use. Team computer controls require manager access. Kairo’s own profile has Activity, Routines, and About.

• Choose how a team crew member replies: Reply when addressed, Reply when useful (it also joins in when a reply would help), or Only when tagged.

• Never without asking lists actions a crew member must check with you first: emailing or messaging people outside the workspace, posting in channels, spending money or changing billing, and deleting or overwriting files. All are off until the owner turns them on.

• Start a DM from New conversation, or manage crew in channel settings. Removing a crew member from a channel stops its work and routines there. Private crew stays out of channels and the workspace roster.

• Tasks, agent threads, and Change Requests show who owns the work. Use Take over or Reassign when you need to change that. Mentioning a second agent on work another agent owns routes the request to the existing owner.

• Team crew has an owner and monthly budget. Choose the workspace default of 30% of the Kairo allowance, or a custom limit. The limit stops scheduled work; direct mentions and DMs can continue until the workspace allowance runs out.

• Crew members can work with much longer context on models that support it. When repository work comes up, such as release notes from merged work, a fix, or a review, a crew member hands it to a Coline Code session.

Ask an agent in a Messages channel, thread, or DM to set up a routine. It can run on a schedule or respond to matching messages, task changes, Change Request activity, checks, incoming mail, calendar events, completed agent runs, or events from connected integrations.

The confirmation shows what it will do, when it runs, and where it posts. Open the routine panel to edit its instructions, schedules, and destination, run it now, pause it, or delete it. Customize > Routines lists routines you created.

Schedules respect the selected time zone and have a minimum interval of 15 minutes. Schedules include a delay of up to 20 minutes. Old occurrences are skipped after downtime. Each person can have up to 20 active routines in a workspace.

Routine posts in channels explain why they ran and who set them up. Background runs default to Observe, which can read and prepare internal findings. Act allows tools to change things; Computer also allows computer work. Failed runs notify the creator; three consecutive failures pause the routine. A routine also pauses if its creator leaves the workspace.

Existing active workspace personas become team crew, and active automations become routines. Converted routines that cannot safely retain their old schedule or destination stay paused for review.

Ask a crew member to get something done or keep watching for changes. It starts a goal from your request, filling in success criteria, notification rules, and an optional end date, and writes a plan before it starts working. Watching, tracking, and weekly checks become goals rather than routines. Requested changes to a goal also apply without a separate confirmation. Any crew member can take a private goal in your DM; team goals need a For the team member in a channel it belongs to and where you can post.

Kairo can start ongoing work with an eligible crew member. A started-goal card shows its title, Goal or Tracking kind, and who is on it, with a link to the goal. A new goal shows as its card right away. If nobody can take the work, a setup card lets you add crew and then review the goal; adding crew alone does not start it. Suggestions the crew raises itself still arrive as drafts you can review and start. Background checks cannot start goals themselves.

• The crew conversation shows goal cards that open their coordinator threads beside Plan, Agents, Outputs, and Memory. Keep going and Try again appear inline when available. While work is running, the empty composer offers Stop; send a follow-up message to steer it. Follow the checklist, inspect a helper’s conversation, ask it a question, stop it, or open its Code session. Outputs link to the work produced.

• Goal status lines shimmer while a goal is working, and “checked 5 minutes ago” keeps counting. Goal tabs are named after the goal.

• Pause or resume a goal, edit its instructions, mark it done, or cancel it. Listening shows the checks attached to a goal, with controls to remove them. Live goals also appear under Kairo with their status and items waiting on you.

• Questions, sign-ins, missing connections, manual handoffs, and blocked work go to Needs you. A missing account comes with a Connect button, and answering resumes the goal.

• A tracking goal keeps checking: if a check ends without booking the next one, a daily check is booked for it.

• The profile’s Goals and Ideas lists are specific to that crew member; Activity shows its runs and routines.

Helpers keep independent conversations and share findings through goal memory. Open the goal’s Memory panel to inspect those findings. Scheduled checks can stay quiet when nothing meaningful changes. Customize > Crew includes the daily digest and Stop everything. Private crew and its notebooks are visible only to you.

Your private crew reuses one computer in each workspace, keeping files and logins across conversations. The crew home shows it beside the conversation on larger screens; the profile also has a Computer tab, and Coline Code lists crew computers in its sidebar. Take over to interact with its screen or sign in, then return control. Recording is off while you have control. Saved site logins, Recover, and Reset are available. Recover keeps the saved disk; Reset asks for confirmation and clears its files and logins.

Earlier ongoing goals assigned to built-in Kairo are cancelled during the Crew transition, and its old background checks are removed. They are not transferred to crew. Start new ongoing work with a crew member.

Computers stop after 15 minutes idle and archive after seven days stopped. Stored disks have no storage charge; active computer use still uses Code credits. Workspace admins can manage team agents’ separate service computers and stop a member’s computer while retaining its disk, without opening its private files or logins.

Crew and goal conversations no longer show action-approval cards or old approval notices. Sign-ins and manual handoffs still need your input.

Stop everything pauses goals and schedules, turns off Always on for your crew, cancels pending personal work, and puts your computer to sleep. Goals also pause after 14 days without owner activity or three consecutive failures. Completed actions stay completed.

Crew members can now work with services outside Coline. Admins connect team services in Settings > Integrations, and you can connect your own accounts in Account > Connections.

• The catalog includes Linear, GitLab, Sentry, PostHog, Vercel, Neon, Cloudflare, Stripe, Shopify, Notion, Asana, monday.com, Todoist, Figma, Resend, Exa, Firecrawl, and Context7. Add any other service as a custom API from an OpenAPI or GraphQL description or a remote MCP server, and review its tools before crew can use them.

• Each connected service shows its accounts, health, events, and tools. Destructive tools stay blocked until you allow them.

• Team accounts are off for every crew member until you choose which crew can use them. A crew member’s profile has a switch for each team account.

• Your own accounts are used only when you ask, and you choose which workspaces’ crew may use each one. In shared places a crew member asks you first.

• When a crew member needs a service that isn’t connected, it posts a private “Connect this service” card that connects in place. If the account already exists, it asks you to turn it on for that crew member instead.

• Run details list every integration call with its outcome and a link to what it touched.

Some services, including Google and Microsoft 365 apps, appear once they are configured for your workspace. Gmail and Outlook are listed only where Coline Mail can connect them.

Agents can ask another agent for help and receive its reply asynchronously. Exchange cards show who asked whom, the request, current state, and reply or failure reason. Each receiver works in its own conversation and keeps its own notebook. In a shared channel thread, exchanges appear in that thread when the receiving agent is already in the channel.

Exchanges must start from a person’s request. They retain that person’s access and the participating agents’ tool limits. An agent cannot message itself or another member’s private crew member. Observe-only checks cannot start exchanges.

Crew is Always on by default for new crew relationships. Creating a crew member, opening its conversation, or first opening its Always on setting starts background checks if no setting exists for you yet. Each crew member has its own setting for you, including team crew. A saved Off choice stays off when you reopen the conversation.

Use the Always on switch under About on the crew member’s profile. Background checks run roughly every 30 minutes, and every two hours while you’re quiet. They read your open goals, pending decisions, and information available through the crew member’s read tools. They cannot use the computer or make external changes. Turning Always on off stops these checks; messages and existing goals can still start work.

A post needs source links and a meaningful change or a decision from you. Quiet results stay in Activity as “Looked around · nothing new”. In channels, delivered posts say “Noticed on its own” and include sources and a Turn off control; in DMs they read like any other reply. If people keep ignoring a crew member’s posts, it slows its check-ins. Background checks stay out of routine lists.

Checks skip missed occurrences and busy conversations, and your messages take priority. Always on pauses after 14 days away or three consecutive failures. The profile explains the pause and lets you turn it back on. A crew member can also offer a confirmation card to re-enable it.

Ideas appear below Goals on a crew member’s profile as private suggestions with a reason and supporting evidence. Start prepares a goal draft for your review; Dismiss removes the suggestion. Team Ideas need a writable channel shared with that crew member before they can become a draft. Each crew member can add up to three Ideas for you per UTC day. Similar open or dismissed suggestions are suppressed, and open Ideas expire after 14 days. Ideas do not send notifications. Earlier Ideas from built-in Kairo expire during the Crew transition.

Crew members keep their own notebook of job knowledge, decisions, preferences, and unfinished work. Open the agent’s Memory tab to browse Ongoing, Decisions, Preferences, and How it works.

For workspace agents, owners and agent managers can add and edit lines, mark open work done, and forget entries. Other members see entries supported by places they can read. Private crew notebooks are owner-only. Recall checks the note’s source places against the audience of the current conversation. Personal reply preferences stay in the person’s memory.

Long agent sessions save useful information to the notebook before shortening their working history. Main channel and DM sessions can start a fresh working history after 24 hours idle, while keeping the visible conversation. When available, the previous session’s summary helps the agent continue. Agents also get context about their unfinished work in other threads of the same conversation.

Kairo’s memory now holds short notes with dates, sources, and a history of changes. It keeps separate notes about you, about you in a particular workspace, for the team, for a channel or group conversation, and for a Connect room.

Ask Kairo to remember something, or add a note yourself. When learning is enabled, it also saves useful facts, decisions, preferences, and instructions after a conversation goes quiet, including facts it finds when you ask it to look into the workspace’s own files, docs, or repositories. Background Dreaming reviews those notes, merges duplicates, updates them, and retires temporary information that has expired.

• Open personal memory in Account settings or Kairo Customize, team memory in Workspace Settings, and conversation memory in channel settings or group DM details.

• Search notes, inspect their sources, edit them, or forget them. Hover over a readable message source to preview the original message. Recent changes show what was added or changed, with Undo where available. Earlier versions remain accessible below the current notes.

• Notes save without a review step. Kairo only learns from people who can change that memory: what guests, outside participants, or other agents said on their own is not saved.

• Turn learning on or off for each supported scope. Private channels, group DMs, and Connect rooms save only when asked by default; public channels and personal Kairo chats learn by default.

• Workspace admins can disable automatic learning or the use of account memory, and control who can read, write, or manage shared memory through roles.

Personal notes load in private conversations with Kairo. Shared replies filter memory and supported read tools against the conversation’s audience. Connect room memory stays in that room. Run details show the memory Kairo consulted or used. Conversations that read mail, the web, or other agents can’t change memory, so outside content can’t plant notes.

Forgetting a note also suppresses it from future learning, and removes it from the change history. Deleting a source message or chat removes notes supported only by that source; notes with other sources lose the deleted reference. Deleting a channel or group conversation removes its memory.

Existing active Kairo memories move into the private “You in this workspace” notes. Agents save notes quietly without posting a saved-memory notice into Messages.

The chat thread has new message layouts, turn navigation, and scrolling that follows a response while keeping your place when you read earlier messages. The composer floats over the conversation, which scrolls underneath it.

• Choose how much Kairo asks before acting. Default asks before sending, deleting, sharing, buying, or running commands. Auto has a quick check review risky actions and asks only when something looks off. Full access does everything without asking.

• Kairo draws interactive answers on its own when they help: numbers you can change, options to compare, data, steps, or status. Their state is saved, so they come back as you left them. The older visual and chart tools are replaced; visuals in older chats still open, share, and export.

• Select part of an answer and choose Reply to quote it in your next message. Click the quote later to jump back to the passage.

• Questions about public people, places, and organizations get a photo next to the first paragraph and inline source chips.

• Every delete Kairo makes can be undone. It can now delete tasks, which go to a trash it can restore from with the same number. Deleted Code projects go to Recently deleted for 30 days.

• When Kairo hits a Coline bug or something Coline can’t do, it can offer to send feedback to the Coline team, and files it only after you agree.

• Suggestion chips on an empty chat now come only from things waiting on you: a chat where Kairo asked you a question, or items from today’s brief it can help with. On a quiet day there are none.

• Long chats show a divider when Kairo condenses earlier context to keep going.

• Links to Coline pages open in app tabs. Links outside Coline ask before opening.

• Models with low, medium, high, and extra-high reasoning show how many requests each level counts as in the reasoning menu.

Reasoning summaries appear beside the step they belong to, with live headings and elapsed time. They fold away after the step finishes unless you choose to keep them open. Sent messages rise into the thread, and streamed words fade once as they arrive. The thinking indicator hands off to the reply without restarting or flashing a final Working state. Attachment removal no longer squashes the composer, and chat tabs show when their title is being named.

Goal, crew setup, agent draft, and routine cards appear in both Kairo chat and crew conversations. Started goals have their own card. Crew and goal conversations use the same composer as Kairo chat, expanding from a pill as text wraps. A paused crew member says so in the composer.

Chat errors now show what actually went wrong, with Try again. This release also fixes replies being cut short at the end of streaming and conversations remaining marked as streaming after the reply finished. Activated skills show their name directly on the tool row.

The daily brief leads with your own day from your calendar, tasks, mail, and messages, and adds what your crew found, made, or needs from you. Newsletters, promotions, and notifications are left out. A finding several crew members reported is written once. This release also fixes briefs that came back with no items.

Waiting on you can be answered in place: crew questions, thread questions, Code sessions waiting on you, and commitments from the last week. The Crew strip shows each crew member with its status, tinted when it needs you, next to Code runs.

New workspaces get a getting-started checklist: ask Kairo something, import or share a note, and invite a teammate.

Use Tidy tabs to gather related tabs into named groups. Fold a group, rename it, choose its color, move it as a group, or ungroup it while keeping its tabs open. You can also create and manage groups yourself. Pinned tabs stay outside groups.

Optional automatic grouping lets new tabs join an existing group when there is a clear match. Existing accounts get an offer beside the tab strip once grouping would be useful. You can accept it, dismiss it, or change the choice in Settings. New accounts get automatic grouping enabled by default.

• Opening a page that already has a tab switches to that tab instead of opening a copy.

• Tabs shrink further before the tab strip starts scrolling.

• Shift-Command-A searches every open tab, Coline’s and Meridian’s, with tabs that need you or have an agent working in them first.

• Pages Kairo opens for you join a folded group named after the chat, instead of landing among your own tabs.

• Crew and goal tabs show the crew member’s name and avatar, and group names are easier to read.

• Switching tabs, opening apps, and moving between channels is much faster and no longer steps through loading placeholders. A conversation you return to keeps its scroll position.

Offers for optional features wait for a quiet moment and remember your choice across the account.

The active-tab highlight follows your selection, and groups animate as they fold or unfold. New tabs pop in, and dragged tabs lift and settle into place. Settings links reuse an open Settings tab.

Every workspace-wide admin control now lives in workspace settings, on one design, grouped as Workspace, Access, Communication, Kairo, Apps and data, and Billing. Search the list to find a setting, and sections you can’t open are hidden. Pages you can only read say so, and Danger zone is visible to the owner only.

• Members, guests, and invites are one list with filters, search, and roles you can change inline. Invite people as members or guests, copy an invite link, or extend an invite by seven days.

• Roles and permissions shows the role editor and the private channel and drive exceptions together. The Audit log can be filtered by action and date, and includes crew activity.

• Team mail settings moved here from the Mail app, with their pages listed under Mail. Old links redirect.

• External sharing holds the Connect rules: who can share channels, whether outside people can bring colleagues, and allowed or blocked domains.

• Apps sets who can install apps (any store app, admins only, or an approved list) and which permissions apps may never use.

• Plan, seats, and invoices are on one page. API keys, Import, Teams, Custom emojis, Memory, Crew, and Code credits each have their own page.

Delete your account from Account settings. It shows what will be deleted, asks you to confirm it’s you, and waits 14 days before deleting, so you can cancel. If you own a team workspace with other members, transfer it first. Content you made in team workspaces stays there under “Deleted user”.

New team workspaces start with a 14-day free trial with no card required: up to 5 people and 1,500 Kairo requests shared for the trial. After creating the workspace, you’re asked to invite your team. You can also pay up front instead.

• A banner tracks the trial for everyone in the workspace. Add a card any time to move to the paid plan when the trial ends, or start the paid plan right away.

• If the trial ends without a card, the workspace becomes read-only until someone adds one. Nothing in it is deleted.

• Change the number of seats in billing settings and see the cost before you confirm.

• When you hit a limit on Kairo requests, storage, publishing, or integrations, one upgrade prompt suggests the right next step for your role. A usage meter appears above the Kairo composer from 80% of the allowance.

• Workspaces with an unpaid bill can no longer send invites.

• Workspace Pro + AI can be bought from billing settings.

Invite links now work when you’re signed out: create an account with the invited email or sign in. Signed in with a different account, you get a way to switch. Expired, withdrawn, and already used invites explain what happened. Sign-up shows the password rules as you type.

Eligible startups can apply for six months of Workspace Pro + AI for up to 25 seats. Verify a work email and choose an eligible team workspace you own, or create one through the application. A valid partner code can approve the application after email verification. Each company domain can receive one startup grant.

Program members get clearer renewal and expiry notices. Eligible graduates of the Students, Open Source, and Startups programs can receive 50% off their first 12 months on a paid plan. The offer opens 30 days before the grant ends and remains available for 60 days afterward.

Team workspaces show a banner before their free period ends. If it expires without a paid subscription, the workspace stays in the switcher and opens a paused screen where the owner can subscribe. An active paid subscription takes priority over a program grant.

Students and Open Source applications also get rebuilt forms, clearer verification and delivery states, and a way to resubmit when more information is requested. School-email and GitHub student verification are tracked separately. Open Source maintainers can verify repository access through GitHub. Eligible renewals extend the current grant rather than cutting its remaining time short.

Admins gain a searchable, paginated application queue with verification evidence and partner-code management. Approval and verification handling also prevent duplicate identity claims, conflicting admissions, and repeated code attempts from bypassing limits. Signing in or completing onboarding returns applicants to their program page.

Paid team plans no longer have a storage cap.

Any Coline app can now publish a public website at its own coline.space address, or on a custom domain with Workspace Pro. Sites replace the public pages from 0.6.

• Visitors can sign in with Coline. A site can be open to everyone, require sign-in, or admit only visitors your team approves.

• Sites keep their data in your workspace, with rules for what visitors can read and change, and can accept file uploads from visitors.

• Sites are built from Coline’s own components and follow the visitor’s light or dark setting. A site can pick one accent color.

• Deploy without an account to try something out. Unclaimed sites last 72 hours; claim one to keep it and move it into a workspace.

• npx coline-app login signs in with your Coline account in the browser, or with a code on another device, instead of an API key.

• Kairo, crew members, and Coline Code can build and deploy sites. New Code projects can start as a site.

• Site settings in the developer console show visitors, files, and custom domains. Installed apps show their own icon, and an app that is only a website opens to its address and settings.

Apps, documentation, and the workspace console now share navigation, a workspace switcher, named breadcrumbs, and your Coline theme. Use the command menu to find an app, jump to a console tool, switch workspaces, or open a guide.

• The overview brings together recent apps, console shortcuts, and a quickstart with commands you can copy. Creating an app starts with a template picker and the corresponding setup command.

• The apps list adds search, Listed and Private filters, latest upload details, and review status.

• App details include a 30-day run chart, a setup checklist based on recorded activity, and section navigation that keeps visited forms mounted when you switch panels.

• Workspace-internal apps show controls that apply to them. Listing, distribution, and monetization controls stay out of their management page.

• API key and OAuth client creation use dialogs that show the new secret once, with a request example. Revocation asks for confirmation.

• Request logs can filter by request type and path. The Tab playground displays completions as ghost text.

• Documentation is split into focused guides with an on-page index, previous and next links, and highlighted code you can copy. The interactive HTTP API reference is available without signing in.

docs.coline.app has been rewritten for the current product and now includes Sites. Old page addresses redirect to their replacements, and every page is also available as Markdown for coding agents.

The message API now only reaches channels and DMs the person behind the request can open, and posting needs the new messages.write scope.

The composer has a simpler raised panel, a send button that follows the theme, and quieter transitions for attachments, mentions, scheduling, and sending. Formatting sits behind a toggle that remembers your choice, and the emoji button opens the picker. With Liquid Glass on, the composer and the message hover toolbar use it too.

One-to-one DM tabs show the other person’s photo or initial, or the agent’s character. Agent DMs keep a paused note in the header when needed. Crew members show their own avatar and color in conversations, and removed crew members leave your DM list. Character expressions reflect idle and working states, and large avatars follow the pointer.

Agent citations to Coline pages now open inside the app. Task links from agent Activity, Kairo tools, apps, and Upstream issues open the selected task correctly. Sidebar previews show agent messages as plain text. The More button on a message opens its menu instead of the thread.

Drive is redesigned. The sidebar has Recent, Starred, and each drive with a folder tree that opens to where you are. Drag files onto any drive, folder, or path segment to move them, with Undo; moving to trash has Undo too.

• Large folders scroll and open quickly. A link to a folder shows its files right away, and opening a folder is near instant.

• The grid shows image thumbnails and page covers. Filter the current folder, sort it, and use one action bar for selections and copied items.

• Starred is its own view, and Recent hides files you can’t open.

The attachment picker combines a compact Drive list with Upload from computer. Drop files onto the picker to attach them. Folder paths, file dates, selection limits, and loading or error states stay visible as you browse.

Inline replies now sit in the thread like the next message. The header includes your avatar and sender picker, recipients align with the message, and attachments have their own row. Open Cc and Bcc independently, edit the subject through More options, or reveal the compact formatting controls when you need them.

Reply and discard transitions are smoother and respect reduced motion. Quoted text stays collapsed when you start typing, and newly added recipients no longer flash out and back into the field. The search toolbar and empty states animate instead of snapping.

Switching folders, split tabs, or searches keeps the open thread open. Lists you’ve already seen come back instantly and refresh in place, and folders start loading when you point at them.

Mail classification now selects a category, priority, and intent from fixed choices. Billing and marketing mail from real senders is no longer tagged as spam; spam now means impersonation, fraud, or requests for credentials or money. Marking a message as spam moves it to Spam, and unmarking moves it back.

Mail refreshes quietly when you return to its tab.

Tab suggestions now appear inline in every editor: Docs, Notes, the message composer, task descriptions, and Calendar. Suggestions follow your formatting and line wrapping instead of floating over the text, stay on one line, and stop at the end of the sentence or list item. They show only when there is a good one.

Git on Upstream is much faster. Pushes finish several times sooner, many agents pushing to the same branch no longer wait in a long line, and repeat clones of the same repository are served from a cache. Partial clones (--filter=blob:none) now work, and a bug that could make repeated git ls-remote calls hang is fixed.

• Change Requests, commits, and comparisons show every changed file with no size limits. The new diff viewer has a file tree with review progress, sticky file headers, and comments on any line. Very large and generated files start collapsed.

• Change Requests gain labels, assignees, reactions, and locking, and lists can be filtered by label. Issues and Change Requests share one numbering, so each number is unique.

• The new Change Request form shows the branches on one line with a live summary of commits, files, and lines. Generate has Kairo write the title and description from the diff.

• Kairo Review reads every changed file and follows the code across the repository. While it works, the review shows what it’s reading and how many files are done; finished reviews include a walkthrough of the change. Maintainers can reply to push back on a finding, and anyone can report a harmful one.

• Push a folder without an account: upstream push creates a temporary repository and prints a link to claim it within seven days. Claimed repositories move to your account with their history.

• Webhooks for repositories and organizations, with a delivery log and redeliver. Personal access tokens are managed in Tokens settings, and you can register apps that people sign in to or install on repositories.

• Release downloads can be added after a release is published. Authors of a fork’s Change Request can comment on lines. All repository settings sections sit in one row of tabs. Repository transfers work again.

• Clone URLs copied in the Coline app now point at the right address, and Open in Code opens the project.

• upstream.codes is labeled alpha.

Developer profiles can include the linked GitHub account’s contribution calendar, with a switch in profile settings. Each day uses the higher of its Upstream and GitHub counts instead of adding both. Upstream’s activity breakdown stays separate.

Kairo pricing on upstream.codes changes: Free includes Review Lite on public and unlisted repositories, Team includes 300 review units per seat, deep reviews count as six units, and extra usage is priced at $0.20 per review unit and $0.08 per question.

Upstream has a public REST API at api.upstream.codes. It covers repositories, files, Change Requests, reviews, checks, Issues, releases, Actions, webhooks, notifications, and organizations. The API is in alpha, so endpoints, fields, and limits can change before it is stable. Send feedback to support@coline.app.

• There is a native API and a GitHub-compatible one, so tools written for GitHub’s REST API work after changing the base address. Other gh commands that need GraphQL do not work yet.

• Personal access tokens have scopes, an optional list of repositories, and an expiration. They also work as a Git password. Create them in Tokens settings on upstream.codes.

• A person’s tokens share 15,000 requests per hour. Requests without a token get 1,000 per hour per IP address. Unchanged responses, rate-limit checks, and some public file reads do not count.

• Each repository and organization has an event feed you can read from any point. Webhooks deliver the same events as they happen.

• Apps can sign people in or be installed on repositories as a bot.

• The docs on upstream.codes cover authentication, GitHub compatibility, and building apps.

• Start a new project from an empty Upstream repository, an Upstream or GitHub repository, a Drive folder, a Coline App or site, or another connected forge.

• Removing a project is now “Remove from Code”: the repository stays as pushed, the project waits in Recently deleted for 30 days, and Undo brings it back. Its computer stops and keeps its files.

• Computers come in Medium (2 CPUs, 4 GB memory) and Large (4 CPUs, 8 GB memory) sizes.

• Every model is available in Code again, and the model picker only lists models your workspace allows.

• Ports and End session are back in the editor’s title bar.

• A running preview no longer blocks stopping a computer. Previews give dev servers more time to start and say why a check failed.

• Long agent runs show a divider when earlier context is condensed.

This release fixes many problems found in testing. New and empty repositories now work for agents, and new Coline Apps set up and build. Pushing, Source Control, and terminals work reliably, and idle terminals keep their connection. Large repositories clone and open, and computers no longer stay stuck on Starting. Publish waits until an app has code. Projects with Kairo history can be deleted. Failed commands show their real error.

Global search works again after the editor’s search response format changed. Source Control gets a compact branch switcher, clearer Changes and History controls, quieter sync actions, and staging checkboxes that appear on hover or stay visible for staged files. Untracked files show their line counts. The editor also gets larger activity controls, tighter tab spacing, a narrower line-number gutter, session titles in the agent header, and shortcut hints in empty panes.

Desktop now opens its window once the page is fully loaded, on the tab you had selected, instead of showing a saved copy and catching up on screen.

Windows and Linux build support joins the Apple Silicon Mac build. Windows uses a per-user installer; Linux offers .deb, .rpm, and AppImage packages. Both new platforms have x64 and Arm64 build targets. The download picker chooses a package for your computer.

After you choose Install Update, Windows and AppImage installs check the download before replacing Coline and restarting. Other Linux packages open a download for your software manager. Browser imports, external-link choices, local Code paths, and menus now work on Windows and Linux.

Swipe two fingers left or right to go back or forward, through tab history in Coline and page history in Meridian.

Meridian gets more of the browser basics:

• Tabs are saved with your desktop profile and come back after a crash.

• Mouse back and forward buttons, middle-click to close, pinch to zoom, and a link preview when you hover a link.

• Right-click or hold Back and Forward to see their history. Save page, view source, copy the page address, Close tabs below, and Copy Link to Highlight.

• Chrome’s tab shortcuts work, plus the usual Windows and Linux shortcuts.

• Pages follow Coline’s light or dark theme, so site icons show up on the sidebar.

• Downloads ask for a destination one at a time, Coline Drive or this computer, and “Always save here” answers the rest. The downloads panel no longer opens on reload.

Liquid Glass now covers channel and DM headers, floating message dates, Jump to latest, menus, selects, popovers, tooltips, dialogs, sheets, the Kairo and crew composers, the titlebar search, and the tab strip. It takes its tint from the selected theme, with a stronger tint in dark mode. Frosted remains available, and reduced transparency and forced colors use fallback styling.

The glass now follows iOS 27: a darker edge so light glass shows on white pages, glints along its rim, and more blur behind menus and dialogs so text underneath doesn’t show through. Buttons on glass light up under the pointer and when pressed. With Liquid Glass on, the selected pill tab is a glass lens that lifts and slides between tabs as you switch.

On upstream.codes, Appearance settings let you choose Frosted or Liquid Glass for the Ask dock. The choice is remembered in the browser.

This release also fixes rendering issues that could make text, icons, or whole panels disappear during movement.

Workspace and app loading do less repeated work. Tasks, Mail, Calendar, Docs, Sheets, Notes, and channels open with their data ready, Home renders its brief and Waiting on you with the page, and Inbox counts share their loading work. Server-rendered pages and Home content stay visible while the app loads, without replaying their entrance animation.

Workspace search removes deleted files and disconnected mail accounts from its results, recovers from interrupted indexing, and no longer gets stuck on large or malformed uploads. Private agent notices and internal agent transcripts stay out of shared search.