Leadership · Self-hostable

Company context for leadership operations.

Summarize new board memos: what was approved, what is blocked, and who owns each next action.

Try Lobu
Connects to
DiscordGitHubGmailGoogle CalendarGoogle ChatHacker NewsLinearMicrosoft TeamsPostgreSQLProduct HuntRedditRSS / AtomSlackTelegramWhatsApp CloudX (Twitter)YouTube+5 more
03/LOBU RUN ]

One company layer, in 4 steps.

See how initiatives, decisions, owners, and follow-through connect across the organization.

01

Connect your company.

Connectors stream your databases, SaaS tools, files, devices, and internal APIs into context. Your systems of record stay where they are. Models, sandboxes, and devices are independent layers, credentials gateway-side. Flip the tabs to wire each one.

Connectors ↗
Pages, decisions, and operating notes remain linked to their owners.
feed · event → shared memoryentity
pages
updateBoard memo Q4 postednow
databases
updateBoard memo Q4 postednow
02

Turn activity into governed context.

Raw events resolve into people, customers, projects, policies, and goals, with the relationships between them. Every fact from the connectors above converges on the right record, carries its provenance, and is read under the caller's permissions.

Memory ↗
memory
Executive
idPK
full_name
function
Initiative
idPK
owner_idFK
status
Decision
idPK
initiative_idFK
approved_at
Action
idPK
initiative_idFK
due_date
03

Deploy Automations that watch and act.

A trigger — a schedule, or reactive to connector events — plus a plain-language prompt. Once defined it runs unprompted: scans memory, matches the trigger, and surfaces the work with the evidence attached.

Automations ↗
automation
triggers⏱ ScheduleOn new memo⚡ On eventBoard memo Q4 posted
prompt

On every new , watch and for follow-ups on its . When an is blocked, flag it and ping the who owns the before the next review.

@ connector@ entityReferences resolve to the sources and types you defined above.
04

Use it from any agent.

ChatGPT, Claude, and Codex connect over MCP; Slack, Teams, and WhatsApp over chat; your own apps over the API. Same context, same permissions, whoever's asking. Consequential work arrives as a proposal you review, edit, and approve.

Platforms ↗
#exec-digestBoard memo Q4
lobujust now

Action needed · Board Q4

  • $4M Series A bridge approved
  • Q1 hiring freeze reaffirmed
  • Frankfurt lease counter due Apr 25

Drafted the exec digest with owners. Review before I post it:

Draft · exec digest
Board approved the $4M Series A bridge and Q1 hiring freeze. Blocked: Frankfurt lease (pending legal). Owner: Priya — counter due Fri Apr 25.
03/TWO WAYS IN ]

Bring any agent. Add shared context.

Use the agents your team already trusts. Managed agents are optional.

Start here

Bring your agents

Connect ChatGPT, Claude, Codex, OpenClaw, or any MCP client to the same company context, scoped to each user.

Connect an agent →
Optional runtime

Build a managed agent

Run repeatable work from live events or schedules under the same approval policy.

Build a managed agent →
04/UNDER THE HOOD ]

One control plane. Any agent.

Share context, permissions, approvals, and connected actions with any agent. Add Lobu's runtime only when you need it.

Halftone figure: multi-socket plug bank
Halftone figure: stacked storage drives
Halftone figure: vacuum tube in a ceramic socket
Halftone figure: sealed glovebox isolation chamber
Halftone figure: balance scale with calibration weights
Halftone figure: freight container on a crane hook
Halftone figure: oscilloscope with waveform
01·CONNECTORS

Plug into everything.

22+ connectors (Slack, GitHub, Gmail, Linear, Postgres and more) stream events in, and actions flow back out under scoped identities. Anything with an API fits the connector SDK.

For engineers

The same agent, in code.

The use case above is one project: connections, entity types, automations, and agent configuration. Inspect each piece or let your coding agent generate it.

lobu.config.tslobu.config.ts
import {
  connectorFromFile,
  defineAgent,
  defineConfig,
  defineSkill,
  defineEntityType,
  defineRelationshipType,
  defineAutomation,
  every,
  secret,
  field,
} from "@lobu/cli/config";
import type LinearCyclesConnector from "./linear-cycles.connector.ts";

const boardActionTrackerSkill = defineSkill({
  name: "board-action-tracker",
  content:
    "Track board action items: check task delivery status, blocker resolution progress, and approaching deadlines for the next board packet.\n",
});

const leadership = defineAgent({
  id: "leadership",
  skills: [boardActionTrackerSkill],
  name: "leadership",
  description:
    "Help leadership teams turn memos, decisions, and board materials into reusable operating context",
  dir: ".",
  providers: [
    {
      id: "anthropic",
      model: "claude/sonnet-4-5",
      key: secret("ANTHROPIC_API_KEY"),
    },
  ],
  network: {
    allowed: [
      "github.com",
      ".github.com",
      ".githubusercontent.com",
      "registry.npmjs.org",
      ".npmjs.org",
    ],
  },
});

// entity types and relationships defined here…

const boardActionTracker = defineAutomation({
  agent: leadership,
  slug: "board-action-tracker",
  name: "Board action tracker",
  triggers: [every("0 8 * * *")],
  tags: ["leadership", "daily", "board"],
  agentKind: "notifier",
  skills: ["board-action-tracker"],
});

export default defineConfig({
  connectors: [
    connectorFromFile<typeof LinearCyclesConnector>(
      "./linear-cycles.connector.ts"
    ),
  ],
  org: "leadership",
  orgName: "Leadership",
  orgDescription:
    "Turn memos, decisions, and board materials into reusable operating context",
  agents: [leadership],
  entities: [decision, document, region, risk, task],
  relationships: [approved, assigned, blockedBy],
  automations: [boardActionTracker],
});

Connect your first agent to company context.

Connect any agent to shared context and keep consequential actions under approval.

Status:// connecting agent…