Skip to main content
Fella can use context you write and vocabulary it learns from explicit corrections. Context can guide interpretation, but it is not evidence and cannot grant a tool or permission.

​
fella.md

1

Open the context editor

Type /context, or create fella.md at the workspace root.
2

Describe stable conventions

3

Ask with the new context

Fella reads the file at the start of each question. It can use the conventions to interpret a request, but figures still need tool evidence from workspace data.

​
Folder memory

Folder memory lives as human-readable Markdown in Fella’s application data directory, separate from the workspace. It is keyed to the folder path and re-read for each question.
Automatic learning is deliberately narrow: an ordinary question teaches memory nothing. A follow-up recognized as a correction can add, update, or deduplicate a vocabulary note, using the active model to reconcile it with existing notes. Fella also records a bounded local episode log, but does not read that log back as memory or cache old query results as facts.
A correction may trigger an additional model request to reconcile vocabulary. With a hosted provider, that correction and the existing vocabulary notes are sent to the provider.

​
Context is not permission

fella.md and memory can influence how the model interprets a question, but they cannot grant it a new tool or a write capability. The read-only boundary comes from the registry and engine.

​
When to use which

Experimental MCP

Read the inert extension boundary for future forks.

The model prompt

See where context enters the reasoning loop.