Group: Mindconnect Semantic UI

Sort by:Popular▼

✓Popular✓Newest

Shared value objects and base types — pure Java, no framework

The shared vocabulary of the agents area, package ai.mindconnect.agent: Namespace (the tenant), NamespacedId (the shape every tenant-owned id has), UserId and AuthenticationInfo. A type belongs here only when two modules that ...

Semantic UI core — model classes and default TypeScript renderer in one module

Core workflow engine: steps, execution, variable scopes, expression resolution

What a tool IS and how it gets bound: Tool, ToolFactory, ToolRegistry, ToolAdvisor, ToolEnvironment plus the ServiceLoader-based registry. Extracted so the eight mc-agent-tools-* modules depend on this instead of on the whole ...

The agent runtime's core: agent and session domain, the ports around it (chat, tools, token counting, memory strategies, repositories) and the use cases — the turn loop, prompt assembly, tool dispatch. Free of storage, HTTP, ...

Document-aware built-in agent tools — PDF/Word/text parsing via Tika+PDFBox+POI

The LLM gateway's core: chat/streaming types and the ports (LlmChat, LlmGateway, LlmConfigRepository). Light enough to be a compile dependency of anything — the implementation with its HTTP clients lives in mc-llm-gateway.

The file counterpart of mc-jdbc: JSON documents in a directory tree, read without locking and written atomically, one writer per file at a time across the whole JVM. FileRepo (one per data directory), Documents (one document ...

The filesystem adapter of the file store (ports in mc-file-store-core):Id-addressed file storage (OpenAI-Files-API-style): upload once, reference the id from chats and vector stores. Backend SPI via ServiceLoader — filesystem ships built-in, ...

A very small JDBC helper for repositories that store domain objects as JSONB documents next to a few queryable columns: Sql (query/update/ transaction on a DataSource), Row/RowMapper, Json, and DocumentTable (upsert, find, ...

LLM server — domain, ports, service, LM Studio (OpenAI-compatible) adapter

The message repository's core: conversations, participants and messages as plain domain types, the ports around them (ConversationManager, ConversationRepository, MessageRepository) and the ConversationService use case. No ...

Web built-in agent tools — HTTP fetch, search, HTML-to-Markdown (future Playwright home)

Message repository adapters — file-backed and in-memory implementations of the ports declared in mc-message-repository-core.

Task queue ports (TaskQueue, TaskStore, TaskWorker) with a local virtual-thread implementation. Payloads are data-only, delivery is at-least-once, cancellation is cooperative — the contract is written for the cluster path (DB ...

Agent tools around the vector-store SPI — vector_upsert / vector_search / vector_delete_file (group "knowledge"), embedding inside the tool so workflows and agents only ever handle text. The ingestion pipeline itself is a workflow ...

JSON (de)serialization of workflow definitions

Agent REST controllers and DTOs — library, no Spring Boot main class

Agent runtime adapters — file and in-memory repositories, the local in-process runtime, the Pebble prompt renderer and the tokenizer-backed token counters. The domain and use cases live in mc-agent-runtime-core.