Sessions, context, memory and sharing
Resume Fulcrum Code sessions, compact long conversations, save durable preferences, review memory and understand undo and local session exports.
Resume and organise work
/history lists saved sessions. /resume opens the resume flow; use the help it displays to choose the session you need. /rename gives a session a recognisable name. Confirm the project directory and the current Git state after resuming: files may have changed since the conversation was saved.
Manage context
/context shows context usage. /compact summarises conversation history to free space. Before a long task, ask for a brief covering the objective, decisions, files changed, checks and remaining work. Compaction can lose detail, so preserve critical requirements in the project instructions as well.
/clear and /reset reset conversation history. They do not mean “revert every file change.” /files shows recently referenced files and /status shows the session's working context.
Save durable preferences
Ask the agent to remember a stable preference or project rule, such as “Remember to use this project's existing package manager.” Memory tools can save, read, list and delete entries. /memory shows the memory view; /save-memories extracts durable notes from the session.
Memory entries live under ~/.fulcrum/memory/, with a generated index. Not every entry is automatically included in every session. Tell the agent to retrieve the relevant project note when necessary. Correct or delete outdated memories, and keep passwords and private customer information out of them.
Undo and redo
/undo and /redo restore conversation and available file checkpoints. Review the files afterwards. Commands that affect external systems need their own recovery procedure; conversation undo cannot retract a sent email or guarantee recovery of deleted remote data.
Share a session carefully
/share exports Markdown and JSON under ~/.fulcrum/shares/. This is a local export. A served link, when enabled through fulcrum serve, is a separate exposure decision. Inspect both exported formats before sharing: prompts, code, paths and tool results can contain private information.
Track usage
/cost shows session token and estimated cost information. /usage reports usage information and /whoami shows the signed-in account context. Cached input and fallback models can affect the breakdown. Use the account's current billing view for subscription and allowance decisions.
Last updated