What it reads, and where it delivers

Read from

Sources

• GitHub

  Commits, pull requests, reviews, issues, comments and discussions: titles, who wrote them, and when. The text is stored too: a commit message, a pull request description, and the whole post of an issue, a comment or a discussion. Never the source code. A renamed repository keeps its history.

• Google Calendar

  Event titles, when they start and end, how many people were invited, and the description on the invitation.

• Sentry

  What broke, what was fixed, and what shipped: an incident when an error is first seen, a regression when a fixed one comes back, a resolution when it stops, and the release it was first and last seen in. The title, the culprit, the level, how often it happened and how many people it reached. Never a stack trace, and never who was assigned to it.

• Bugsnag

  The same incidents and resolutions, and a release when a version ships. The error class, the message, the context it happened in, and the counts. Never a stack trace, and never who was assigned to it. Bugsnag puts no date on a regression, so none is stored from it.

Recent work is kept event by event. Older work is compacted into a rollup, one stored summary standing for a period, so an account written about an old week stays checkable after the events behind it have gone. An event an account cites is never compacted.

Next

Planned sources

Planned, and not available yet. Until one ships, Tomwiser does not read it.

• GitLab Planned

  Read the same way GitHub is read today.

• Bitbucket Planned

  Read the same way GitHub is read today.

• Slack messages Planned

  Reading messages as a source. Today Tomwiser only posts to Slack and answers questions asked there.

Delivered to

Delivery

• Email

  One message per person, with an unsubscribe that works on the first click. See a sample

• Slack

  The account in the channel the project chooses, on its days. Ask Tomwiser in a direct message or a thread and the answer comes back there, with links. Tomwiser reads only what is asked of it; it does not read the rest of your messages. See a sample

• Notion

  One page the workspace chooses; each new account goes at the top and earlier ones stay below it. Tomwiser writes that page and reads nothing else in Notion: it sees only the names of the pages you share with it, so it can offer them to you. See a sample

• Your AI assistant

  In an assistant that connects to remote MCP servers, such as Claude, ChatGPT or Cursor, add Tomwiser with the address https://api.tomwiser.com/api/v1/mcp. Claude and ChatGPT call this adding a custom connector. The assistant opens Tomwiser so you can sign in and choose the workspace it may read. From then on it can ask about the team's work, read an account, see what is coming and open the events behind any line, with a link to each. See a sample