Open-source enterprise agent platform

Lynxus

A release-driven platform for governing agents, connecting business systems, running recoverable workflows, and observing every session as it happens.

View source Quick start

Status: Alpha · v0.1
License: Apache 2.0
Runtime: Temporal + JVM/Python
Console: Vue + Spring Boot

Demo videos

Take a walk between the console and runtime.

Session demo

A minimal session running through the console.

Console tour

A tour of business domains, assistants, agents, knowledge bases, resources, and release snapshots.

Why Lynxus

Enterprise agents need more than prompts.

Governance

Business domains, scenarios, assistants, agents, playbooks, knowledge bases, and resources are modeled as first-class governed objects.

Integration

Tool connectors and channel providers sit behind a protocol boundary, keeping vendor auth, signing, vendor SDKs, and long-lived connections out of agent logic.

Operations

Sessions, events, playbook runs, handoffs, and shared state are persisted and projected into a runtime view built for tracing real work.

Core model

A governance tree that reaches runtime.

Domain
- Scenario
  - Assistant Release release-anchored
    - Owner Agent
    - Playbook
    - Resource tool · skill · llm · knowledge

Lynxus treats configuration as contract. Draft objects can evolve, but running sessions are anchored to an assistant release that freezes the owner agent, policies, resource versions, knowledge bindings, and playbook definitions.

Release snapshots prevent runtime configuration drift.
Resources carry stable version anchors across tools, skills, LLMs, and knowledge.
Agents decide; playbooks execute structured business flows.

Runtime architecture

Session-first execution with recoverable workflows.

Control plane
Release assembly

Spring Boot APIs assemble releases, govern catalogs, and expose session-runtime views.
Spring Boot · PostgreSQL
Workflow worker
Durable orchestration

Temporal hosts session and playbook workflows with waits, resumes, handoff, and shared state.
Temporal · JVM worker
Agent runtime
Decide & act

Python executes owner turns, tool tasks, privacy policy handling, and knowledge calls.
Python · LLM providers
Knowledge
Retrieval surface

URL and file sources become chunks, index snapshots, and release-scoped retrieval.
Python · vector index

Extension Plane

One boundary for tools and channels.

Tool Connector

Business capability access

Extension services expose tool operation schemas through manifests, while Lynxus routes agent-runtime tool calls to the selected connector.

Channel Provider

Conversation channel access

Channel providers normalize IM, ticketing, and service desk inbound events through the channel gateway and consume outbound frames.

Protocol + SDK

Contract-first extension work

OpenAPI, JSON Schema, examples, canonical fixtures, and JVM/Python Extension SDKs keep extension services aligned with the platform boundary.

Developer entry points

Start from the public contracts.

01 Quick start Run the local control plane, runtime, knowledge service, and console. 02 Architecture App split, runtime flow, and current implementation boundary. 03 Extension integration Build tool connectors and channel providers against the Extension Plane. 04 Extension protocol OpenAPI, JSON Schema, examples, and fixtures as the source of truth.

Project status

Alpha, built for evaluation and local integration.

Lynxus has the core control-plane → release-snapshot → Temporal worker → Python runtime path in place. Interfaces, data structures, and configuration may change across minor versions while production hardening continues.

Star on GitHub Releases Discussions