Operational

$Exybit AI Engine

An agentic AI engine for software development — API-first, CLI on top.

The engine behind everything I build — a proprietary agentic layer over a frontier language model that powers my own systems through a REST / WebSocket API and a published CLI client. Built for multi-step reasoning with real tool execution, not just chat completion.

#Capabilities

Agentic core

Multi-step reasoning with tool and action execution — the engine plans, calls tools, and acts on results.

Dual surface

REST + WebSocket API, plus a Model Context Protocol (MCP) server for device and tooling integration.

Semantic response caching

pgvector + fastembed embeddings for fast, meaning-aware cache hits.

Session persistence

Redis-backed sessions keep conversational state durable across requests.

Published CLI

@exybit/cli — a TUI chat client on npm that talks to the engine over WebSocket.

~Running in production

>

AIDA

The first-person AI persona on exybit.org — the portfolio assistant — is powered by this engine.

>

@exybit/cli npm

Terminal chat client, npm i -g @exybit/cli, published and live.

>

Fission

An autonomous R&D pipeline whose workers (fission-worker, on npm) execute tasks in isolated Docker containers.

>

Lotus Commercial — in-app AI assistant

Powers the AI chat inside the Lotus Commercial operations portal, answering inquiries across jobs, scheduling, attachments, invoices, and more.

>

Personal AI assistant in dev

A conversational personal assistant (Telegram + web) that tracks todos, reminders, expenses with receipt-photo capture, and notes — surfacing daily digests and spending insights, and extending itself with new skills on demand.