Shinkai

Enables rapid AI agent scaffolding through a React-based form interface (agent-form.tsx) that abstracts agent configuration complexity into visual controls. The system captures agent metadata, model selection, system prompts, and tool bindings, then serializes this configuration into a structured format that the Shinkai Node backend consumes. This eliminates the need to write YAML or JSON manually, reducing agent creation from hours to minutes.

Provides an interactive tool development environment (tool-details-card.tsx, tool-card.tsx) where developers can define tool schemas, test execution with sample inputs, and validate outputs before binding to agents. The playground integrates with the Shinkai Node's tool execution engine, allowing real-time invocation of tools with arbitrary parameters. Tool definitions are stored in a registry accessible to all agents, enabling reusable tool libraries.

Manages application-wide settings (settings.ts) including LLM provider credentials, default agent selection, UI preferences, and node connection details. Settings are persisted to local storage (encrypted for sensitive data) and synchronized across application restarts. The system provides a settings UI (settings.tsx) for user-facing configuration and programmatic APIs for application code to read/write settings.

Integrates with the Galxe platform for credential verification and reputation tracking, allowing agents to access user credentials and reputation scores during execution. The system implements OAuth-style authentication with Galxe, caches credential data locally, and exposes credentials to agents through the tool execution context. This enables agents to perform reputation-aware actions or access Galxe-protected resources.

Exposes all created agents and tools as an MCP (Model Context Protocol) server, enabling external clients (Claude, other LLM applications, custom scripts) to discover and invoke agents/tools via standardized MCP endpoints. The system implements MCP resource and tool definitions that map to internal Shinkai agent/tool registries, with request routing handled by the Tauri backend (main.rs, deep_links.rs). This allows Shinkai agents to be consumed by any MCP-compatible client without custom integration code.

Provides a real-time chat UI (chat-conversation.tsx, message-list.tsx) that maintains conversation history, manages context windows, and routes messages to selected agents. The system implements a message system that tracks sender/receiver, timestamps, and message types (user, agent, system), with context set via set-conversation-context.tsx allowing users to bind specific agents, tools, and knowledge bases to a conversation. Messages are persisted and streamed through WebSocket connections to the Shinkai Node backend for real-time response generation.

Manages a vector file system (vector-fs-context.tsx, all-files-tab.tsx) where documents are indexed and embedded for semantic search. Users can upload files, organize them into knowledge bases, and search using natural language queries (search-node-files.tsx). The system integrates with the Shinkai Node's embedding and vector storage layer, enabling agents to retrieve relevant context from the knowledge base during conversations. Files are chunked, embedded, and stored in a vector database accessible to all agents.

Provides a settings interface (ais.tsx, default-llm-provider-updater.tsx) for configuring and switching between multiple LLM providers (OpenAI, Anthropic, local models via Ollama, etc.). The system stores provider credentials securely, allows per-agent model selection, and implements a default provider fallback mechanism. Model availability is queried from each provider's API, and the system validates model compatibility with agent requirements before execution.

Enables scheduling of agent tasks to run on a recurring basis (via task scheduling in the backend), with support for cron-like expressions and event-based triggers. The system integrates with the Shinkai Node's scheduler to execute agents at specified intervals, capture results, and optionally route outputs to other agents or external systems. Workflow state is persisted, allowing complex multi-step automation sequences.

Provides a Tauri-based desktop application (shinkai-desktop) that runs on Windows, macOS, and Linux, with a companion browser-based interface for remote access. The system uses Tauri's native bridge (main.rs, windows/mod.rs) to expose Shinkai Node functionality to the UI layer, with deep linking support (deep_links.rs) for protocol-based agent invocation. The monorepo structure (NX-based) enables code sharing between desktop and web frontends.

Implements WebSocket-based real-time communication between the Tauri desktop frontend and the Shinkai Node backend, enabling streaming responses, live agent status updates, and bidirectional message flow. The system uses the shinkai-message-ts library to serialize/deserialize messages, with automatic reconnection and message queuing for offline resilience. This allows agents to stream responses character-by-character and tools to report progress in real-time.

Provides automated Shinkai Node management (shinkai-node-manager-client.ts) that handles local node startup, shutdown, and health checks, with support for both local and remote node connections. The system can download and manage Shinkai Node binaries, configure node settings, and expose node management APIs through the Tauri backend. Users can toggle between local and remote nodes without restarting the application.