Skip to main content

Home, Needs you and Activity

Press Home in the sidebar to see which sessions need a person and how pull requests are moving across your projects. The sidebar lists every project and its live sessions, and marks each one where the agent is waiting on your answer. Press ⌘K (Ctrl+K on Windows and Linux) to find a session by title. For a record of what changed and who changed it, open Settings > Workspace > Activity.

Home​

Home shows your own work at first. Use the filters at the top to widen or narrow it:

FilterOptionsStarts on
AssigneeOne or more members, plus Kosuke, Assigned and Unassigned. Clear every choice for All Assignees.You
ProjectAll projects, or one project.All projects
Date rangeThis month, 7d, 30d, 90d, or two dates that span up to 366 days, counting both.Last 30 days

Kosuke remembers your filters for each workspace.

Figures and chart​

FigureWhat it counts
PRs openedPull requests from sessions created in the date range.
mergedPull requests merged in the date range.
merge rateOf the sessions created in the range, the share merged rather than archived with a pull request.
median to mergeThe median time from a session's creation to its merge.
building nowSessions with the agent working right now.

The chart below shows pull requests opened and merged per day. Hover over a day to see its numbers. Days are in UTC.

Needs you​

The Needs you card lists live sessions that are waiting on you. Only Active and Under Review sessions count. It holds your own sessions, sessions booked to Kosuke, and the pull requests a teammate asked you to review. Each session appears once, under its most severe reason:

OrderThe row readsWhy the session is waiting
1Checks failing on "title"Its pull request's checks failed.
2Turn failed 2h agoThe agent's last turn failed.
3Agent asked a question 2h agoThe agent asked a question and is waiting for an answer.
4/kosuke:ship stopped for you 2h ago/kosuke:ship stopped on a prototype to approve or a failure, or on a ready it could not prove.
5"title" is approved and ready to mergeIts pull request is approved, its checks passed, and it is not in the Merge Queue yet.
6Your approval is asked on "title"A teammate's pull request asks you for a review. Only you see this row, not its author.
7Behind mainIts branch is behind the Target Branch.
8Open 3 days, untouchedIt has an open pull request and no activity for more than 3 days.

Rows are sorted by that order, then by most recent activity. Click a row to open the session. Messages, Up next and steering explains answering the agent, and Sync with the Target Branch explains a branch that is behind.

The Assignee and project filters narrow the card. The date range does not. The same list is available from the CLI with kosuke sessions all --needs-you --viewer me.

By repository and Recently merged​

With All projects selected, the card beside Needs you is By repository. It shows one row per project, with sessions building, pull requests open and merged, merge rate, and sandbox spend or hours.

With one project selected, the card is Recently merged. It lists that project's last six merged sessions. Press View all to open the project.

Share your numbers​

Press Share at the top of Home to turn the current filters into an image you can post. Pick one of four cards:

CardWhat it shows
StreakThe longest run of working days, Monday to Friday, with at least one merge. A day with nothing merged ends the run; a weekend does not.
Player cardA level, one for every ten pull requests merged, with the longest streak, merged of opened, median to merge and best day.
Trophy caseSix badges, each unlocked by a number on the Player card, such as 100 merged or a median to merge under a day.
LeaderboardMembers ranked by pull requests merged in the project and date range, with you highlighted. It ignores the Assignee filter.

The Streak, Player card and Trophy case follow the Assignee filter, so with All Assignees they show the whole workspace. The dialog opens on the Streak card when the longest streak is three working days or more, and on the Player card otherwise. The numbers come from the same figures Home shows for the same filters, and days are in UTC like the chart.

To post the card:

  • Post on X and Post on LinkedIn open a new post with a line of text and a link to the card. X and LinkedIn show the link as the card image.
  • Copy link copies the same link, for Slack or anywhere else that shows link previews.
  • Share image opens your device's share sheet with the image attached. It appears on phones and in browsers that can share files.

Post on X, Post on LinkedIn and Copy link publish the card at a public address, such as app.kosuke.ai/cards/.... Anyone with the link can see the card, so it shows what the card shows: the names, the project and the numbers on it. Search engines are asked not to list it. Sharing the same card again gives the same link. A card is published with the latest numbers. If they changed after the dialog drew the card, nothing is published: Kosuke draws the new card and asks you to check it before you post again. The card page links to app.kosuke.ai/sign-up, and so does the footer of every card.

Once you have published a card, Published cards appears under the buttons. It lists the cards you published from this workspace, newest first, each with an Open, a Copy link and a Delete icon. In a workspace with no projects, where there is nothing to draw a card from, Published cards sits at the top of Home instead of Share. Deleting a card takes down its page and both of its images, so its link stops working. X and LinkedIn may keep showing the preview they saved on posts made earlier, until they check the link again. Only you can delete your cards. They are also deleted when you leave or are removed from the workspace, when you delete your account, and when the workspace is deleted.

The sidebar​

The top of the sidebar holds New session, Home and Crons, plus Lead in workspaces with the Lead beta. Under Projects, each project lists its sessions.

A project row can carry a badge:

Badge or iconMeaning
DEPLOYINGA deploy is running.
Warning triangleThe deploy agent is waiting for your input.
Red circleThe last deploy failed.
SETUPThe project has never deployed. The row opens its settings.

Each session shows at most one status mark, in this order:

MarkMeaning
Merge or archive iconThe session is Completed or Archived.
Green dotThe branch was merged.
SpinnerThe agent is working.
Pulsing amber dotThe agent is waiting on your answer. Shown only to the session's Assignee, or to every member while the session is Kosuke's.
Red dotThe last turn failed.
Solid dotUnread. The agent finished, or the session was reassigned to you, since you last looked. Shown only to the Assignee, or to every member while the session is Kosuke's.

A PR badge marks a session whose pull request has not merged, including an Archived session whose pull request was closed. Its color says whether the pull request needs attention, is waiting on checks, is ready to finish, or is under review. Hover over it for the checks and conflicts. A sandbox icon appears while the session's sandbox runs. Press it to stop the sandbox.

Press Filter Sessions next to Projects to choose what the lists show. The sidebar starts on Active and Under Review sessions. You can also filter by Assignee and priority. Right-click a session for Open chat, Share, Rename, Priority, Assignee, View on GitHub, Archive and Delete. See Chat sessions and the board.

Search sessions​

Press ⌘K (Ctrl+K), or the Search button next to the workspace name.

  1. Type part of a session's title. With nothing typed, the palette lists the 10 most recently active sessions.
  2. Pick a result. It opens the session, or the details of a Backlog session.

Results are grouped by project. The search covers the workspace you are in and leaves out Archived sessions. For every shortcut, see Keyboard shortcuts.

Workspace Activity​

Activity is the workspace's log of what changed and who changed it, kept for 30 days. Every member can read all of it.

  1. Open Settings > Workspace > Activity.
  2. Pick a project to narrow the list, or leave All projects.
  3. Pick All, Changes or Member actions.
TabWhat it lists
ChangesStates Kosuke observed. Checks fail or pass, a pull request merges, a branch falls behind, a pull request goes stale, the agent waits for an answer, or a Cron run succeeds or fails.
Member actionsWhat a named member did. They started, sent to, archived, deleted, assigned or moved a session, or changed its priority. They created, paused, resumed, edited or deleted a cron. They invited or removed a member, or changed a role.

Sending to a session is recorded once per member, session and day. Each event shows its time: how long ago for today, then Yesterday or the date. Press the Open session icon on a row to go to its session.

A dot marks each event that is new since your last visit. Your own actions are never new to you. Opening the page marks everything in the workspace as seen, and the dots stay until you close it.

To read Activity from a script, use kosuke activity list. kosuke agent summary prints what needs you and your new Activity in one digest. See Kosuke CLI.

Next steps​