emergent-company

Full Memory CLI command reference with all subcommands and flags. Use when you need exact command syntax, flag names, or usage examples for any `memory` CLI command.

Full Memory CLI command reference with all subcommands and flags. Use when you need exact command syntax, flag names, or usage examples for any `memory` CLI command.

Create a versioned release — commit, tag, push, and deploy to servers. Use when the user wants to release, deploy, publish, or push a new version.

Analyze and dump OpenCode sessions from any project. Use when the user asks to read a session, find a session by title, list sessions for a project, dump session content, or show usage stats (skills, tools, tokens, cost) for any project directory.

Read from the knowledge graph — natural language questions, semantic search, or hybrid search over objects and documents.

Create and manage graph branches — isolated workspaces for staging changes before merging to main. Use for what-if analysis, planning, or any work that should not immediately affect the main graph.

Install, list, or remove schemas (object and relationship type definitions) in an existing project. Use after onboarding when managing or updating the type registry.

Diagnose a problem with the Memory platform (server, CLI, or agents), gather environment and log diagnostics, and file a GitHub issue with structured context. Use when something is broken, behaving unexpectedly, or producing errors.

Manage Emergent runtime agents and agent definitions — create, trigger, monitor runs, respond to questions, and manage agent configurations. Use when the user wants to run, inspect, or configure AI agents in an Emergent project.

Apply and export Emergent Blueprints — declarative directories of template packs, agent definitions, and seed data applied with `memory blueprints`. Use when setting up a project from a blueprint, seeding graph data, or exporting an existing project's graph as re-applyable seed files.

Full Memory CLI command reference with all subcommands and flags. Use when you need exact command syntax, flag names, or usage examples for any `memory` CLI command.

Manage MCP (Model Context Protocol) servers in an Emergent project — register, inspect, sync tools, and delete servers. Use when the user wants to add, configure, or troubleshoot MCP servers connected to their Emergent project.

Onboard a project into Memory — understand what the project is, choose or create a Memory project, design and install a schema (template pack), then guide on creating objects and relationships. Use when setting up Memory for a new project or codebase for the first time.

Manage LLM provider credentials and browse available models in Emergent. Use when the user wants to configure API keys, set up Vertex AI, check which models are available, or review LLM usage and costs.

Query an Emergent project knowledge base using natural language or direct hybrid search. Use when the user wants to search, explore, or ask questions about content in an Emergent project.

Manage Emergent schemas (template packs) — discover, install, and remove reusable sets of object and relationship types in a project. Use when the user wants to configure what types of knowledge objects a project can contain.

Add a component to the project's go-daisy gallery. Use whenever the user says "add a component to the gallery", "register this component in the gallery", "show this in the gallery", "add a gallery entry for X", "add a story for X", "add variants for X", "preview this component in the gallery", or "gallery-add-component". Covers editing gallery/components.go, GalleryComponent fields, Category constants, HTML snippets, Templ components, named Variants/stories, DesignToken controls, and running the gallery to verify.

Install the go-daisy component gallery into any Go module. Use whenever the user says "install the gallery", "set up gallery in this project", "add go-daisy gallery", "init gallery", "run gallery install", "gallery-install", or "how do I get the gallery running". Covers running the installer, what files are created (gallery/main.go, gallery/components.go), Taskfile patching, port configuration, skill installation, and next steps.

Use the `codebase` CLI to populate, audit, and explore the Memory knowledge graph for a codebase. Use when the user wants to onboard a project, sync routes, check API quality, analyze domain structure, manage graph objects, manage constitution rules, track competitors and market trends, or install skills.