Skip to main content
Shanone evolves quickly. This page tracks major, user-visible platform milestones rather than every internal change — see Integrations for the latest additions to the tool catalog.

​
August 2026

Rebrand: emma → Shanone The product formerly known as emma is now Shanone — “Command Center for Agent Harnesses.” The rebrand reflects a deliberate pivot: Shanone no longer runs its own autonomous planning/execution engine (the previous LangGraph-based orchestrator was fully removed as dead code once nothing called it anymore). Shanone’s role today is to be the tool vendor, skill vendor, and permission layer that other agents — Cursor, Claude Code, and any MCP client — call into. Added:
  • Permission Vendor: IAM-style tool and service permission management (shanone_list_services, shanone_set_user_tool_permission, shanone_set_user_service_permission, shanone_get_permission_summary, shanone_batch_set_user_permissions, shanone_list_user_tool_permissions), scoped to Root users and delegated SA2 administrators
  • Skill Vendor rewritten around a simple, DynamoDB-backed storage model (name / summary / instructions) with progressive disclosure — list calls return metadata only, full instructions are fetched on demand
  • shanone_list_service_tools meta-tool, for fully enumerating a large integration’s tools instead of relying on relevance-ranked search
  • Webhooks: inbound event sources (starting with Typeform) can automatically launch a connected agent platform (Devin, Cursor Cloud Agents, or Manus)
Changed:
  • Removed the legacy hierarchical “Skill” system tied to the old orchestrator (per-agent prompt files, excel_operator, and similar) — the term “Skill” now refers exclusively to the Skill Vendor’s user-saved workflows
  • Backend split into independently deployable services (tool execution, analytics, billing, crawling) for more granular scaling

​
June–July 2026

Added:
  • @duzzle/shanone-mcp published to npm — a local stdio MCP proxy for clients that don’t yet speak remote Streamable HTTP MCP with custom headers
  • Continued expansion of the integration catalog toward 269+ live service integrations

​
What’s next

More integrations

Continued growth toward the full 140+ integration / 10,000+ tool marketing catalog

Deeper Skill sharing

Team-level (not just per-user) Skill visibility is under consideration

​
Feedback

Have suggestions or found something inaccurate here? We’d love to hear from you.