Core concepts
A practical vocabulary for understanding how a task is organized, what can act on it, and what still needs your judgment.
Session: the context of the task
A session brings together the conversation and context used for an assignment. Keep a clear objective in it. When the objective changes substantially, make the change explicit rather than assuming earlier instructions no longer apply.
Example: “Compare the two supplied notes” is one assignment. “Email the result to the team” is a new external action, not an implied next step.
Tools: actions, not instructions
A tool gives the agent a way to perform an operation. Availability depends on the configured environment and permissions. Naming a tool in a prompt does not install it or authorize every operation it supports.
Before use: decide whether the task needs read access, write access or an action affecting another system. Prefer the narrowest access that can accomplish the task.
Skills: reusable working instructions
A skill packages instructions for a recurring kind of work. It is different from a tool: instructions explain an approach, while a tool performs an operation.
Example: a review skill might require source references and an uncertainty section. It does not by itself grant access to a document or permission to publish the review.
Memory: context to check
Memory can contribute information beyond the immediate exchange. Treat remembered details as context, not proof. If a decision depends on a current fact, check the original source or ask for confirmation.
Example: a remembered delivery preference may be useful; an old budget or deadline should be rechecked before it drives a new decision.
Workspace: the intended working material
Workspace files provide material for the task. Include only what is necessary and preserve the original when asking for edits. File availability should not be interpreted as permission to change or distribute it.
Example: use copies of two fictional notes for an initial comparison. Define the output filename and whether overwriting an existing file is allowed.
Model configuration: the reasoning service
The model configuration determines the model connection used for requests. A configured model is not the same thing as a configured tool. Validate the connection in your deployment and consider what data may be sent to that provider.
No universal provider support, price or data-retention policy is established by these concept pages.
Approvals and recovery: preserve the boundary
The development design includes approval and continuation flows. Their exact availability depends on the operation and version; this page does not promise an approval checkpoint for every possible action.
After an interruption, inspect what actually completed before retrying. Do not repeat a potentially external action merely because the conversation stopped. Ask for confirmation when the result is uncertain.
Putting the concepts together
Provide two notes in the workspace, state the objective in a session, use a skill if relevant, and allow only the tools needed to inspect the inputs. Review the resulting brief against the notes. Neither memory nor a successful tool response substitutes for that final check.