concord
v0.6.1Continuous memory for Codex: captures each session from the rollout, ages it into tiers, and injects the relevant slice back at the next session start.
By jabworksLicense: MIT1 GitHub starsUpdated 3 days ago
Directory evidence
- Runtimes
- Codex and Claude Code
- Parsed components
- 2 skill or MCP entries
- Source updated
- Sep 20, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install concord for Codex and Claude Code
codex plugin marketplace add IchenDEV/agent-plugin-mkt
codex plugin marketplace upgrade agent-plugin-marketplace
codex plugin add concord@agent-plugin-marketplacePaste and run these commands in a terminal with Codex. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/jabworks/agentic-toolkitClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is dist/plugins/concord/.
Plugin files
├── .codex-plugin/plugin.json├── .claude-plugin/plugin.json├── skills/concord-doctor/SKILL.md└── skills/remember/SKILL.md
Included Skills2
Health check for the concord memory plugin on the host it is installed on. Probes both Codex registration paths — the hooks.json the installer writes and the plugin manifest a Codex plugin install uses — checks all three hook events resolve to scripts that still exist, that the experimental hooks feature is enabled, that the memory store is readable, and compares the installed version against the local marketplace clone. Never runs a hook: both of them write.
Continuous memory for Codex — write explicit remembers, and recall from Concord's own tiers when a question reaches past what session start injected.
Plugin manifests2
{
"name": "concord",
"version": "0.6.1",
"description": "Continuous memory for Codex: captures each session from the rollout, ages it into tiers, and injects the relevant slice back at the next session start.",
"author": {
"name": "jabworks"
},
"repository": "https://github.com/jabworks/agentic-toolkit",
"license": "MIT",
"keywords": [
"memory",
"context",
"persistence",
"session",
"codex",
"recall"
],
"skills": "./skills",
"hooks": "./skills/remember/hooks/codex-hooks.json",
"interface": {
"displayName": "Concord",
"shortDescription": "Continuous session memory for Codex.",
"longDescription": "Concord gives Codex memory that survives the session. Three hooks share one idempotent operation — sync the rollout forward from its recorded position — so capture is exactly-once regardless of hook order, and a hard-killed session is recovered at next start rather than lost. Memory ages through buffer, daily, recent, and archive tiers; explicitly pinned facts are never auto-compressed.",
"developerName": "jabworks",
"category": "Productivity",
"defaultPrompt": [
"Remember that deploys need the VPN.",
"What did we work on yesterday?",
"Search my memory for the auth refactor."
]
}
}{
"name": "concord",
"version": "0.6.1",
"description": "Continuous memory for Codex: captures each session from the rollout, ages it into tiers, and injects the relevant slice back at the next session start.",
"author": {
"name": "jabworks"
},
"repository": "https://github.com/jabworks/agentic-toolkit",
"license": "MIT",
"keywords": [
"memory",
"context",
"persistence",
"session",
"codex",
"recall"
],
"skills": "./skills"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[concord on Agent Plugins Marketplace](https://pluginsmp.com/plugins/concord)