copulse is a local-first component workspace for building, testing, combining, and deploying software components from one source of truth.
The extension connects VS Code to the copulse local runtime so you can inspect a component graph, run connector tests, simulate API flows, and generate deployment output without leaving the editor.
Vision
copulse treats an application as a graph of small components. Each component can define:
- A manifest.
- Dependencies.
- Runtime environment.
- Connector tests.
- Resource profile.
- Deployment contract.
The same workspace can start as one small API, grow into API + PostgreSQL + Redis, and later split into optimized deployment targets for Docker Compose, K3s, or Kubernetes.
Commands
Open the Command Palette and search copulse.
Available commands:
copulse: Open Studiocopulse: Start Local Agentcopulse: Graphcopulse: Build Docker Composecopulse: Build K8s YAMLcopulse: Test Allcopulse: Simulate Full Flow
Studio
copulse: Open Studio opens a lightweight workspace panel with:
- Component graph actions.
- Docker Compose and Kubernetes build actions.
- Connector test actions.
- API simulation selector.
- Output panel for runtime feedback.
Runtime Behavior
- If the local agent is running, extension commands call the agent API.
- If the local agent is not running, commands fall back to the bundled CLI runtime.
- The installed extension includes a bundled MVP runtime and examples.
Quick Start
- Install the extension.
- Open a workspace that contains copulse examples or manifests.
- Run
copulse: Open Studio. - Run
copulse: Graph. - Run
copulse: Test All. - Run
copulse: Build Docker Compose.
Local Development
From the repository root:
cd copulse
.\install-extension.cmd
This builds a fresh VSIX, validates the package metadata, removes older local installs, and installs the latest local build.
Repository
Source code:
https://github.com/votrongdao/co-pulse
Current MVP Scope
This release is an MVP for validating the workflow:
- Component graph.
- Local agent.
- CLI fallback.
- Docker Compose generation.
- Kubernetes YAML generation.
- Connector sandbox tests.
- API flow simulation.
Future releases will improve the visual editor, plugin model, runtime isolation, templates, deployment validation, and platform API integration.