763 karma · joined May 20, 2024
# skill-scopes.conf -- GENERATED from extensions_scoped.toml. DO NOT EDIT. # # extensions_scoped.toml is the single source of truth: each [[skills]] entry # lists the skill's `scopes`, and this file is derived from them -- one # `<scope> <directory> ...` line per scope, both sorted for a stable render. # # The tokens after the scope are skill DIRECTORY names, not SKILL.md names: # launch-daemon.sh resolves each against /opt/hatch/skills-scoped/<directory>. # # launch-daemon.sh reads this at cell boot and reveals only the gated skills # whose scope matches the VM's JARVIS_CD_CHANNEL. An unset/unknown channel or a # missing line reveals nothing (fail-closed). Edit the manifest, not this file. hatch-e2e ads_mcp health nutrition hatch-evals ads_mcp health nutrition internal-test ads_mcp audio_notes_read documents end-call health nutrition polymarket price-tracker prod granola notion whatsapp
Muse has a lot of cool things visible through the VM worth talking about (safety classifiers, cloud-hypervisor instead of firecracker, eager compaction, and an interesting rescue system, memory in postgres).
Just started using it today so pretty excited to put it on some harder problems and see how it goes :).
Thought this was an interesting line, though I definitely don't have enough OSS experience to understand it concretely, but seems like these type of questions are applicable beyond OSS.
in guessing the most important thing to get right for their target usecase is the computer use and from the tools i saw for that the computers they provision were requestable by the subagents so probably something cool going on there
[1] https://cursor.com/docs/configuration/tools/mermaid-diagrams