Skip to main content

​
TL;DR

  • Tasks can run on any available computer. Cogno picks a free teammate’s computer when needed and hands the run off if that computer stops responding.
  • Cogno starts working when added to a channel. In Slack, Discord, and Microsoft Teams, no setup or mention is required.
  • Approvals happen in the conversation. Tools set to Ask now work in everything Cogno does, including work it starts on its own.
  • Microsoft Teams can be set up from Settings.
  • Cogno can change settings on request. You choose how much it may change, per kind of change.
  • Meeting recording settings have changed. The workspace-wide switch is removed and video is off by default.

​
Automatic computer selection and handoff

Tasks that Cogno starts can now run on any member’s computer that has the Project’s folder ready, not only the assignee’s.
  • Cogno uses the least busy computer, and prefers the assignee’s computer when they are equally available.
  • If the computer running a Task does not respond for 10 minutes, the run continues on another computer with its in-progress changes.
  • Work sent to an offline computer is kept until that computer comes back, instead of being dropped.
A Task running on another member’s computer shows This task is running on {owner}‘s {machine} (or This task is running in the Cloud environment). To bring it to your computer, send a message from the box at the bottom and select Continue on my machine. The run on the other computer stops, and your inbox notes that the run was moved to your machine. The default for Turns at once is now 10 per computer.

​
Automatic start when added to a channel

When Cogno is added to a Slack or Discord channel, or to a Microsoft Teams team, it starts working without further setup.
  1. It posts a one-line note on what it will take on.
  2. It reads the channel history to understand its purpose, who owns what, and which threads are unanswered.
  3. It takes on stalled items and reports progress and results in each thread.
Anything that would be sent outside your organization is left as a draft.

​
In-conversation approvals

Tools set to Ask under Agent tools previously worked only in conversations you had open. They now work everywhere, including replies to mentions and work Cogno starts on its own.
  • When a call needs approval, Cogno asks in the thread or chat and continues with work that does not.
  • Approve by replying in the thread, or with Approve / Decline on the card.
  • Pending approvals no longer time out. A tool approval lasts for the rest of the conversation and survives an app restart. An approval for a command or file change applies to that single call.
Supported for both Claude Code and Codex.

​
Microsoft Teams setup

The Microsoft Teams page under Settings → Integrations now includes the Add Cogno to Microsoft Teams steps.
  1. Select Download Teams app and upload it in the Teams admin center (Open Teams admin center). It may take a few hours to reach all users.
  2. In Microsoft Teams, add Cogno to the team you want to connect and to any group chats.
  3. Connect the team in Cogno and choose which channels to import.
Once connected, the page follows the same layout as Slack.
  • Each team shows Cogno app added, or Cogno app not added to this Team with steps to fix it. Without the app, messages are still imported, but Cogno cannot reply to mentions or post.
  • Channels and chats are toggled with switches. Search channels appears for teams with many channels.
  • Refresh channels and chats and Download Teams app are in the ⋯ menu.
In Teams, Cogno posts a welcome message when added to a team or chat. @Cogno help returns the setup steps, even before the team is connected.

​
Settings changes through Cogno

You can now ask Cogno to change settings. Changes are made with the requesting member’s permissions, and the request is recorded. This covers workspace, member, Project, personal, integration, meeting recording, and your own computer settings. For actions Cogno cannot take, such as billing, deletions, connecting an integration, or loosening permissions, it points you to the right place. Control what Cogno may change under Settings → General → Agent tools and Settings → Members → Agent tools, choosing Block, Ask, or Allow for each kind of change. Invite and remove members and Import GitHub issues as Tasks default to Ask. Cogno can only tighten tool permissions, connectors, and computer access, never loosen them.

​
Meeting recording changes

  • The workspace-wide recording switch in Settings → General has been removed. Whether the Notetaker joins a meeting is set by Allow meeting recording under Settings → Recording and by each meeting’s own setting.
  • Video is now off by default. Audio and transcripts are still saved. Turn on Save video recording for meetings that need video. Upcoming meetings switch once to audio and transcript only.
  • Tasks created from a meeting now show their status: Running, Queued, Run failed, Not started, or Done.

​
Other changes

  • Sidebar: a Task stays marked as active while its agent is working, and the unread dot appears once work finishes. Hidden Projects are grouped under Hidden projects at the bottom of the sidebar.
  • Stopping work: asking Cogno to stop in a thread now also stops related runs and scheduled work for that thread.
  • Multiple pull requests: after a Task’s pull request is merged or closed, a new one can be opened from the same branch.
  • Sign-in prompts: when Claude Code’s sign-in expires, the Task shows Claude Code needs you to sign in again with the command to run. Cloud Project owners see Claude Code needs to be reconnected (or the Codex equivalent).
  • Removed: the Slack /task and /implement commands and the From Slack option in Create Task. Mention Cogno in Slack instead. Workspace instructions are now in Memory as instructions.md.