karass.devsession: anon·last compile: 2026-04-18

  ##  ##    ####    #####     ####    ######  ######
  ##  ##   ##  ##   ##  ##   ##  ##  ##      ##
  ## ##    ##  ##   ##  ##   ##  ##  ##      ##
  ####     ######   #####    ######   ####    ####
  ## ##    ##  ##   ## ##    ##  ##      ##      ##
  ##  ##   ##  ##   ##  ##   ##  ##      ##      ##
  ##  ##   ##  ##   ##  ##   ##  ##  ######  ######

an AI employee that grows with your data

connect your data streams — notion, linear, gmail, github, claude code, call transcripts, slack. karass reads, learns the shape of your work, and becomes addressable through any channel as a single self. the longer it runs, the more it knows.

## how it works

[01] connect

link your data sources. oauth where possible, hooks and webhooks where richer. bulk import on connect — karass starts with context, not from zero.

[02] hatch

events flow in. a knowledge graph grows in the background. karass boots from a living identity snapshot, not a static prompt.

[03] earn trust

karass climbs the trust ladder. listener → planner → coordinator → initiator. scope expands only when you say so.

## trust ladder

┌──
[phase 3]initiator
proposes and acts on its own. regression possible on override.
┌──────┘
[phase 2]coordinator
spawns ephemeral sub-agents. you still merge the work.
┌──────┘
[phase 1]planner
drafts loops and plans. you approve before execution.
┌──────┘
[phase 0]listener
reads everything. answers questions. no side effects.
──

phase transitions require demonstrated reliability — not a subscription upgrade. regressions happen when karass gets something wrong. it is supposed to.

## integrations

  • [x] claude code hooks
  • [x] notion
  • [x] linear
  • [ ] github
  • [ ] gmail
  • [ ] google drive
  • [ ] slack
  • [ ] tactiq / read.ai
  • [ ] crm (hubspot / salesforce)
  • [ ] jira
  • [ ] dropbox
  • [ ] + more

[x] = shipping · [ ] = on the build queue

## request an invite

karass is invite-only during the incubation period. tell us what you want karass to do for you — it helps us prioritize which integrations ship next.

$