Reuse instructions and files
Keep the brief, the spec and the brand guide in one named folder.
A context bundle is a named folder of background reading. You put the documents in once — the brief, the spec, the brand guide, last quarter's notes — give the folder a name, and then list, read and edit it by that name.
The point is one place for the material: the same documents, the same wording, under one name.
A bundle has two parts:
- a handle — a three-part name like
team/ctx/spec, in the shapenamespace/collection/name - one or more items — each item is a file, with a short label you choose (
design,brand,notes)
Make a bundle
In the console this is the Context section: create a bundle, name it, add the documents, and describe what it is for.
Find it again
The console lists your workspace's bundles and shows what is in each one.
An App that declares a bundle is refused: a bundle is found by its name, not handed to an App's steps.
Look at what you have
The console's Context section lists your bundles and what is in each one.
Bundles are scoped to your workspace. You cannot see, or test for the existence of, another workspace's.
Change one item
In the console, open the bundle to replace a document, drop one, or change the description.
Removing a bundle unbinds the name. The uploaded files themselves stay where they are.
Two properties worth understanding
These two are the reason bundles behave predictably, and they are worth reading even if you never go past the commands above.
A bundle's identity
A bundle's own identity is derived from its handle and its items, in order: writing the same items to the same handle again is reported as a no-op.
Editing an item cannot rewrite history
A reference always points at exactly the file it pointed at when it was made. It never changes meaning underneath you.
The consequence: the old file is still stored under its old reference, so anything that recorded that reference still reads the same bytes.
Where to go next
Search your documents
Give Kortecx your documents so your Apps answer from them: add text and files to a named dataset, then search it in plain language.
Keep memory between runs
Give an agent a notebook that survives between runs — remember a fact once, recall it by meaning later, and forget it when you want it gone.