Busabase x Knowledge Base for CrushKnowledge Base for Crush
Crush brings models, project context, LSP, Skills, and MCP into a terminal workspace. Its power comes with a trust boundary: crushrc is executable configuration, MCP can carry credentials, and a session result is not automatically a durable project decision.
MAP
A terminal agent is only as trustworthy as the configuration and evidence around each tool call.
Crush brings models, project context, LSP, Skills, and MCP into a terminal workspace. Its power comes with a trust boundary: crushrc is executable configuration, MCP can carry credentials, and a session result is not automatically a durable project decision.
Project, model, LSP, conversation state
Shell-like provider, model, permission, and MCP config
stdio, HTTP, SSE, OAuth
Source, scope, owner, tested result
BOUNDARY
Crush supports stdio, HTTP, and SSE MCP transports
A terminal agent is only as trustworthy as the configuration and evidence around each tool call.
| Session context | Project, model, LSP, conversation state | Operational context for one workspace |
|---|---|---|
| crushrc | Shell-like provider, model, permission, and MCP config | Trusted executable configuration |
| MCP transport | stdio, HTTP, SSE, OAuth | Capability and authentication boundary |
| Reviewed decision | Source, scope, owner, tested result | Durable project knowledge |
SCOPE
OAuth can use dynamic registration or explicit client credentials
Crush brings models, project context, LSP, Skills, and MCP into a terminal workspace. Its power comes with a trust boundary: crushrc is executable configuration, MCP can carry credentials, and a session result is not automatically a durable project decision.
Operational context for one workspace
Trusted executable configuration
Capability and authentication boundary
Durable project knowledge
EVIDENCE
Skills are discovered from global and project paths and loaded on demand
Crush supports stdio, HTTP, and SSE MCP transports OAuth can use dynamic registration or explicit client credentials Skills are discovered from global and project paths and loaded on demand
| Session context | Project, model, LSP, conversation state | Operational context for one workspace |
|---|---|---|
| crushrc | Shell-like provider, model, permission, and MCP config | Trusted executable configuration |
| MCP transport | stdio, HTTP, SSE, OAuth | Capability and authentication boundary |
| Reviewed decision | Source, scope, owner, tested result | Durable project knowledge |
ACCEPTANCE
A terminal agent is only as trustworthy as the configuration and evidence around each tool call.
Crush supports stdio, HTTP, and SSE MCP transports OAuth can use dynamic registration or explicit client credentials Skills are discovered from global and project paths and loaded on demand
Verify Project, model, LSP, conversation state before accepting Operational context for one workspace.
Verify Shell-like provider, model, permission, and MCP config before accepting Trusted executable configuration.
Verify stdio, HTTP, SSE, OAuth before accepting Capability and authentication boundary.
Verify Source, scope, owner, tested result before accepting Durable project knowledge.
FAQ
Knowledge Base for Crush: practical questions
A terminal agent is only as trustworthy as the configuration and evidence around each tool call.
Is crushrc just a settings file?
No. Crush documents it as trusted code and it can execute shell expressions. Review it like code.
Does OAuth make an MCP result trusted?
No. OAuth authenticates the connection. Claims returned by the server still require validation.
Should Skills be copied into project policy?
Only when the team reviews the Skill version, scope, and expected tool effects.
Can session context be canonical?
A session is useful evidence, but durable knowledge needs a source, owner, and review state.
NEXT
A terminal agent is only as trustworthy as the configuration and evidence around each tool call.
Crush brings models, project context, LSP, Skills, and MCP into a terminal workspace. Its power comes with a trust boundary: crushrc is executable configuration, MCP can carry credentials, and a session result is not automatically a durable project decision.