/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Slack launches Botkit, an open-source framework for building apps for Slack, after working closely with Howdy

Slack Is Releasing Botkit To Make Bots Easier To Build  —  Slack, the increasingly popular team-messaging software, wants more developers to build apps that hook into its work-chat software.

ReadWrite Owen Thomas

Context & Ripple Effects

Botkit lands on the same day Slack opens its third-party App Directory alongside an $80M developer fund at 2M daily active users — the framework is the tooling half of that ecosystem play, built with bot-maker Howdy so developers have a starting point beyond raw API docs.

The pattern holds afterward: Slack's Slack Fund puts $2M into 14 Slackbot startups, then backs 11 more bot makers, while interface layers like Block Kit and interactive buttons standardize how those bots look and behave. A decade later the endpoint is Salesforce shipping an AI-powered Slackbot in general availability — the bot framework era maturing into assistants inside the work-chat surface.

First-order effects

  • Slack developers gain an open-source, Howdy-tested scaffold for building chatbots against the newly launched App Directory, lowering the cost of the first wave of integrations.
  • Howdy gets its bot-building approach validated and distributed as Slack's official starting point, positioning it inside the ecosystem rather than competing with it.

Second-order effects

  • A funded bot startup pipeline emerges: with Slack Fund capital flowing into Slackbot-focused companies within months of the launch, Botkit becomes the common substrate those portfolio startups build on.
  • Competing team-messaging platforms face pressure to match the developer-fund-plus-framework package if they want comparable third-party app catalogs.

Third-order effects

  • If the arc from Botkit through Block Kit to the AI Slackbot holds, the durable structure is a chat client evolving into a work surface where third parties — and eventually agents — are the product layer, with Slack owning the distribution and interface standards.
  • Open-sourcing the framework sets the template for how platform owners recruit builders without owning every integration: free tooling up front, monetized platform access behind it.

The trend: Team-chat platforms are turning themselves into extensible work surfaces by subsidizing developer ecosystems whose endpoints evolve from scripted bots into embedded AI assistants.