Bm Status

OrganizationPopular

basicmachines-co

bm-status

Report the Basic Memory for Codex configuration, reachability, hook expectations, recent Codex checkpoints, and active tasks.

Overview

Publisher	basicmachines-co
Repository	`basic-memory`
Skill name	`bm-status`
Stars	4K
Forks	283
Bundled files	2
License	AGPL-3.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
2 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by basicmachines-co on GitHub. Read the source before you install it.

Installation

Install the Bm Status AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/basicmachines-co/basic-memory/tree/main/plugins/codex/skills/bm-status

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/basicmachines-co/basic-memory.git /tmp/basic-memory
mkdir -p .claude/skills
cp -r /tmp/basic-memory/plugins/codex/skills/bm-status .claude/skills/bm-status

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Bm Status in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Bm Status on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Bm Status is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Basic Memory For Codex Status

Gather a concise diagnostic. Do not over-investigate.

Gather

CLI reachability:
- basic-memory --version
- fallback bm --version
- fallback uvx --prerelease=allow basic-memory --version
Keep going if no launcher resolves. The plugin hook scripts can still use their uv-managed environment; report hook health as unavailable instead of claiming the hooks cannot work.
Plugin config:
- read ~/.codex/basic-memory.json, then the nearest project .codex/basic-memory.json; project keys override user keys
- report the resolved primaryProject, secondaryProjects, teamProjects, captureFolder, rememberFolder, recallTimeframe, focus, sessionProfile, repository, checkpointOnCompact, and captureEvents
- resolve omitted Codex defaults as rememberFolder=codex/remember, and checkpointOnCompact=true
Core hook health:
- with the first available launcher, run basic-memory hook status --harness codex --project-dir <repo-root>
- report the shared inbox path, pending envelopes, archived envelopes, last flush, settings state, resolved primary project, capture state, capture folder, checkpoint-prompt state, Basic Memory version, and uv version from that command
- inbox counts are global across supported harnesses; do not attribute a backlog solely to Codex
- treat the command's settings resolution as canonical for hook behavior; if it disagrees with the manually read config, show the mismatch
Hook files and launcher visibility:
- check uv --version in the current environment independently of CLI reachability; uv is a required hook prerequisite
- distinguish "uv missing from this shell" from "Desktop hook runtime verified"; shell success does not establish the Desktop hook process's PATH
- when Desktop/WSL hooks fail while TUI works, inspect the actual hook launch error and PATH; uv: command not found occurs before the Python script can emit a diagnostic
- consult ../../README.md under "Troubleshooting Desktop hooks on WSL" for the default-location probe and conditional symlink workaround
- only report Desktop hook execution as verified when startup context and a post-compaction checkpoint note were observed; otherwise label it unverified
- confirm plugins/codex/hooks/hooks.json exists if running from this repo
- remind the user that Codex plugin hooks must be reviewed and trusted before they run
Basic Memory queries:
- query recent type=codex_session; when sessionProfile=coding, also query type=coding_session with repository=<configured repository>, then merge, deduplicate, sort newest first, and keep the newest five; never run an unscoped coding-session query when the repository is missing; these are agent-authored checkpoints, while lifecycle envelopes remain local operational trace
- active type=task, status=active
- open type=decision, status=open

Present

Use this shape:

text
Basic Memory for Codex
- CLI: <version or missing>
- Project: <primaryProject or default>
- Reads from: <secondaryProjects or none>
- Share targets: <teamProjects or none>
- Capture folder: <captureFolder>
- Remember folder: <rememberFolder>
- Recall timeframe: <recallTimeframe>
- Session profile: <general | coding>
- Repository: <owner/name or none>
- Checkpoint on compact: <enabled | disabled>
- Event capture: <enabled | disabled>
- Shared hook inbox: <path or unavailable>
- Shared pending envelopes: <count or unavailable>
- Shared archived envelopes: <count or unavailable>
- Last flush: <timestamp, never, or unavailable>
- Hook runtime in this environment: basic-memory <version>; uv <version or missing>
- Desktop hook execution: <verified from context and checkpoint | unverified>
- Recent checkpoints: <count across coding_session and codex_session>
- Active tasks: <count>
- Open decisions: <count>
- Hooks: installed; trust review required in Codex

List recent checkpoints by type, title, and permalink when available. Warn when event capture is enabled and pending envelopes are accumulating or the last flush is never, while noting that another harness may contribute to the shared counts. Do not warn about an empty inbox when capture is disabled.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

agents/openai.yaml1 KB
assets/icon.svg1 KB

Frequently asked questions

What does the Bm Status AI skill do?

Report the Basic Memory for Codex configuration, reachability, hook expectations, recent Codex checkpoints, and active tasks.

Why use Bm Status on TypingMind?

Because you install it once and use it with any model. Bm Status is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Bm Status in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/basicmachines-co/basic-memory/tree/main/plugins/codex/skills/bm-status. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Bm Status?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Bm Status?

As many as you like. As long as a model supports skills, you can use Bm Status with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Bm Status AI skill free?

Yes. It is published on GitHub by basicmachines-co under the AGPL-3.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Code Review

mattpocock

CommunityPopular

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what…

Codebase Design

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or…

Diagnosing Bugs

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

Implement

Implement a piece of work based on a spec or set of tickets.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Basic Memory For Codex Status

Gather

Present

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now