context_pack
Return a ranked, cited, token-budgeted context pack so the agent can avoid broad file reads.
LABSCO SUMMARY
One call that returns cited evidence inside a token budget, instead of an agent guessing which files to open.
The context pack is the point: it comes back ranked, with citations, and sized to the budget you passed, so the cost of establishing context stops scaling with the size of the repository. The memory ledger is deliberately strict — a lesson has to carry evidence references, and when the evidence underneath it changes the memory is marked stale, which is what keeps stored notes from quietly going wrong. Nothing leaves the machine.
What it is
A local index over one workspace — SQLite with full-text search and a typed graph of files, symbols, modules and config — queried through a small tool surface, plus a memory ledger for lessons that outlive a session.
What you get
- A context pack for a question: ranked, cited evidence assembled to a token budget you set, so one call replaces a run of greps and file reads
- Search across code, docs, symbols and stored context, ranked lexically, by symbol and with graph awareness
- Graph traversal between files, symbols, modules and config nodes, along the edge types you name
- Impact analysis: the likely dependents of a file, symbol or module, and the tests that cover it
- An explanation of why something may have changed, combining the current evidence with git history
- A memory ledger searched for lessons that survived earlier sessions, and written to only with evidence references — a loose remember-this note is rejected
- A CLI, cxf, that runs the same index, search and memory operations by hand
Requirements
No account and no key — v1 is local-only: it calls no external embedding API, uploads no source, edits no files and installs nothing inside the workspace it indexes. Run it as a server with npx -y @inferensys/contextful server over stdio, from the npm package @inferensys/contextful, currently 0.1.0, which also installs the cxf and contextful binaries. The workspace has to be prepared first: cxf init --workspace <YOUR_WORKSPACE> then cxf index, with --watch or cxf daemon to keep it fresh as files change. State lives in a .contextful/ directory. The project describes itself as early alpha with breaking changes expected.
Setup effort
Follow the published steps
USE CASES
01
Starting work on an area of the codebase you do not know
Ask for a context pack on the question and read the cited bundle rather than opening files at random.
02
Finding where something is handled when you cannot name the file
Search across code, docs, symbols and stored context with the ranking doing the narrowing.
03
Working out what a change will break
Pull the likely dependents of the symbol or file and the tests that cover them.
04
Understanding how two parts of the system are connected
Trace the graph path between them along the edge types that matter.
05
Explaining why a file ended up the way it is
Combine the current evidence with its git history in one answer.
06
Not relearning the same thing next session
Write the lesson with the evidence refs behind it, and recall it at the start of the next session.
7 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
impact_analysis
Find likely dependents and tests for a file, symbol, or module.
recall_memory
Search the evidence-backed memory ledger for lessons that survived previous agent sessions.
search_code
Search code, docs, symbols, and stored context with lexical, symbol, and graph-aware ranking.
trace_path
Trace graph relationships between files, symbols, modules, and config nodes.
why_changed
Explain why a file or symbol may have changed by combining current evidence with git history.
write_lesson
Write an evidence-backed lesson to the memory ledger. Loose remember-this notes are rejected.
BEFORE YOU INSTALL
What to know first
Tools you get
7 tools when we connected.
Requires
npx on PATH
Where it runs
Both documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 7 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
Setup
TERMINAL
npx @inferensys/contextful init --workspace .npx
TERMINAL
npx -y @inferensys/contextful serverMCP Clients
Codex
CODEX · TERMINAL
codex mcp add contextful -- npx -y @inferensys/contextful serverAny MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"contextful": {
"command": "npx",
"args": [
"-y",
"@inferensys/contextful",
"server"
]
}
}
}
