This is the standalone Context repository. It contains the local knowledge SDK, CLI, extraction packages, Agent plugin sources, and development tooling. Hosted server, storage, and web application stacks are outside its boundary.
graph TD
core["@c4a/core"]
context["@c4a/context"]
extract["@c4a/extract"]
extractTs["@c4a/extract-ts"]
tui["@c4a/tui"]
contextCli["@c4a/context-cli"]
devCli["@c4a/dev-cli"]
extract --> core
extractTs --> extract
contextCli --> context
contextCli -. build-time bundle .-> core
contextCli -. build-time bundle .-> extract
contextCli -. build-time bundle .-> extractTs
devCli --> core
devCli --> tui
- Use Bun for scripts:
bun run,bunx, andbun test. - Keep runtime code Node.js compatible; do not use Bun runtime APIs in package code unless the file is explicitly a build/test tool.
- Use ESM modules and
camelCase.tsfilenames. - Build package entrypoints through
packages/build.tswhen bundling CLI or extractor-dependent code. - Do not add hosted server, web, storage, model-download, or server-install flows to this workspace.
@c4a/contextis the SDK surface forsrc/index.tsproject entries;@c4a/context-cliis the executablecontextcommand.
bun run build
bun run typecheck
bun run test
bun run lint
bun run verify
bun run --filter @c4a/context-cli build
bun run --filter @c4a/dev-cli start- This repository is developed and released independently from any parent monorepo or downstream distribution.
README.mdandREADME.zh-CN.mdare the product entrypoints. Long-form integration case studies live underdocs/, while static replay assets live undercase-studies/and are published as documentation through GitHub Pages. They are not part of the hosted product or npm runtime.- Keep generated files out of source control:
dist/,node_modules/,.tmp/, coverage, and local caches.