Improve Developer Journey for Modules & Apps Development §

https://github.com/logos-co/logos-workspace/issues/44

completion target: Testnet v0.2

Resources Required for 2026H1:

• 3 Engineers

Make it easier to build, iterate on, and ship Logos modules and applications. This milestone covers three fronts: enabling agent-assisted development workflows through CLI and MCP support; rolling out the module builder build system and a test framework across all projects; and improving the builder itself with better configuration, daemon mode, and developer tooling.

The goal is that a developer (or an automated agent) can scaffold a module, build it, test it, and debug its interactions with other modules — all with minimal friction and a single coherent toolchain.

FURPS §

• Developer Module
• Logos App

Deliverables §

Facilitate Agentic Workflows §

Owner: Logoscore Team

Feature: Developer Module (supportability, usability)

Improve tooling and integration points so that automated agents (and humans) can scaffold, modify, and validate modules with fewer manual steps. This includes language-server support for IDE integration, MCP support for agent tooling, and debug tooling for tracing module interactions.

Tasks:

• Add MCP support — enable Model Context Protocol integration in Basecamp for agent-assisted workflows
• Support debug tool to log calls between modules in dev mode — add tracing of inter-module communication for debugging
• CLI support
• Developer Module: output selective or global tracing and logging of module interactions — configurable tracing output at the developer module level
• Investigate LSP server support — evaluate feasibility of a Language Server Protocol implementation for Logos module development or some other method to improve developer experience using an IDE

Update Apps and Modules to Use Test Framework §

Owner: Logoscore Team

Feature: Logos App

Roll out the module builder’s test framework across all existing modules and apps. Each module gets integration tests that validate its behavior within the LogosCore runtime.

Sub-tasks (13 modules):

• logos-package-manager-module (duplicate)
• logos-blockchain-module
• logos-blockchain-ui
• logos-lez-wallet-ui
• logos-lez-module
• logos-wallet-module
• logos-wallet-ui
• logos-accounts-module
• logos-accounts-ui
• logos-chat-module
• logos-chat-ui
• logos-delivery-module

Improve Logos Module Builder §

Owner: Logoscore Team

Enhance the builder itself — configuration, developer experience, and runtime modes — based on dogfooding feedback.

Tasks:

• Unify configs into a single metadata.json file — replace the current split of metadata.json + module.yaml + manifest.json with a single configuration source
• Update module builder to handle different edge cases — harden the builder against real-world module structures encountered during rollout
• Daemon mode — run LogosCore as a background daemon, enabling faster iteration cycles during development
• Implement a logos shell command (like nix develop) — drop developers into a pre-configured shell environment with all dependencies available
• Lock versions used in tutorial — pin dependency versions in the tutorial to prevent breakage as the stack evolves

Generalize Logos Apps §

Owner: Logoscore Team

Tasks:

• Generalize LogosApp and Standalone Apps — make the app shell reusable beyond Basecamp so third-party developers can build standalone Logos applications
• QML inspector in standalone app — add a built-in QML inspector for debugging UI modules during development