This repository is an archive of SharpClaw modules that were split out of the main SharpClaw repository. They are kept here for reference, demos, experiments, and anyone who wants to study or revive one of the older module surfaces.
These modules are intentionally not part of the core SharpClaw build anymore. Some are polished enough to run, some are prototypes, and some are mostly useful as examples of how a SharpClaw module can be structured.
| Folder | Module | Notes |
|---|---|---|
BotIntegration |
Bot Integration | Telegram/Discord-style bot integration surface. |
ComputerUse |
Computer Use | Desktop/device/window/process oriented automation hooks. |
DangerousShell |
Dangerous Shell | Direct shell access model for trusted/admin scenarios. |
DatabaseAccess |
Database Access | External/internal database resource and query tooling. |
Http |
HTTP | HTTP request steps, webhooks, and network trigger helpers. |
Mk8Shell |
mk8.shell module | SharpClaw module wrapper around the mk8.shell command language. |
OfficeApps |
Office Apps | Office/document session experiments. |
SystemAudio |
System Audio | Local audio capture and audio processing services. |
Transcription |
Transcription | Speech-to-text jobs, live transcription, and related endpoints. |
WebAccess |
Web Access | Website/search-engine resources and gateway extension experiments. |
Whisper |
Whisper provider | Local Whisper.net STT provider for the Transcription module. |
The projects still reference SharpClaw core projects by relative path. The expected local layout is:
E:\source\
SharpClaw\
SharpClawTestModules\
or the same sibling layout wherever you clone them:
workspace/
SharpClaw/
SharpClawTestModules/
The module projects reference:
SharpClaw.ContractsSharpClaw.UtilsSharpClaw.Gateway.Abstractionswhere gateway hooks are presentSharpClaw.Providers.Commonwhere provider contracts are needed
Build an individual module from this repository root:
dotnet build .\Http\SharpClaw.Modules.Http.csproj
dotnet build .\Transcription\SharpClaw.Modules.Transcription.csproj
dotnet build .\Whisper\SharpClaw.Modules.Providers.Whisper.csprojThere is no solution file on purpose. These modules are archived as loose external modules, not as a single product surface.
SharpClaw can load modules from built output folders. A typical output folder looks like:
SharpClawTestModules\Http\bin\Debug\net10.0
Add the module output path to SharpClaw's ExternalModules configuration, or
use the module-management UI/API in SharpClaw to register and enable it.
This is an archive/supporting repository, not the canonical SharpClaw runtime. Expect rough edges:
- Some modules may need dependency or API updates as SharpClaw evolves.
- Some module manifests may reflect older IDs or demo-time naming.
- Build outputs, local env files, and generated artifacts are intentionally ignored.
These modules were split from SharpClaw and retain the same licensing intent as the original code unless a module-specific file says otherwise.