LIFEHUBBER
Choose theme

AI Resources

OpenExecutive

GitHub stars: 5.2K GitHub forks: 547 Last pushed September 24, 2026: Pushed today
Stats from GitHub

OpenExecutive is a self-hosted assistant built around management work. It answers through one executive voice while consulting specialist agents for areas such as strategy, finance, people, operations, and product.

The project connects company documents and a profile to its answers, keeps a record of past decisions, and can schedule follow-ups. It is a software system to configure and run, rather than a ready-to-use public chatbot. Use this as a first read, not a recommendation. Open the original project before trusting details like terms, limits, privacy, cost, setup, or safety.

What it is

One assistant with management specialists

An orchestrator routes questions to eight specialist agents and combines their input into one reply. The repository includes a web interface, API, command-line path, and deployment instructions.

Why it stands out

Company context carries forward

It can retrieve from uploaded company documents, retain selected decisions between sessions, and surface scheduled follow-ups. That makes it more specific than a one-off panel of AI opinions.

Availability

Code and setup instructions are public

The Apache-2.0 repository provides local and container setup paths. The project describes a managed cloud offering as forthcoming; the inspectable path today is its self-hosted code.

Why it matters

What makes it useful

OpenExecutive can bring uploaded company documents and earlier decisions into later management questions, then surface scheduled follow-ups. Its repository lets a team inspect how those pieces work together before deciding whether to host and configure the assistant.

Notable points

What stands out

The repository documents a single-instance limit for its scheduler and describes a managed cloud version as still forthcoming. Its many integration paths are configuration options, not a promise that every connection is ready in a fresh install.

Before using

What to review

Plan for a Python and Node setup, an Anthropic API key, and the initial downloads described in the repository.

Decide which company documents and work systems the assistant may access, and review its permissions before connecting real accounts.

Check the current deployment and authentication instructions before exposing its API or MCP endpoint beyond a local machine.

Keep final decisions with the people accountable for them; specialist labels describe the software roles, not the credentials of a human expert.

Reader fit

Who may find it relevant

Teams exploring a configurable assistant for recurring management questions and follow-ups.

Builders studying document retrieval, specialist routing, decision memory, and work-channel integration in one application.

Less relevant for readers who want an instant hosted service or a lightweight prompt-only decision council.

Editorial note

Why LifeHubber lists it

LifeHubber lists OpenExecutive because it brings company context, specialist routing, decision memory, and scheduled follow-ups into one inspectable application. That helps readers decide whether a persistent management assistant is worth the hosting, API, and data-access setup it asks of them.

Source links

Source materials

Reader note

Before relying on this entry

LifeHubber lists entries to help readers inspect AI projects, not to endorse them or prove they are safe, suitable, accurate, maintained, or right for a specific use. We do not verify every entry in depth. Before relying on anything listed, review the original materials, terms, privacy practices, limits, and risks that matter for your situation.

Advertisements

Advertisements

For project maintainers

Listed here? You can use the badge.

If you maintain a project with a current LifeHubber listing, you may add the optional “Listed on LifeHubber AI Resources” badge to its README, docs, or website. No introduction or permission request is needed.

See what’s moving