agent

const (
	ToolSetCoreRO   = "core_ro"
	ToolSetSlackRO  = "slack_ro"
	ToolSetNotion   = "notion"
	ToolSetGitHub   = "github"
	ToolSetWebFetch = "webfetch"
	ToolSetJira     = "jira"
	// ToolSetCore is the FULL action toolset (create / update / archive), as
	// opposed to the read-only core_ro handed to investigation sub-agents. Only
	// the channel-mode case agent asks for it: a thread-mode workspace manages
	// no Actions at all.
	ToolSetCore = "core"
	// ToolSetMemo is the Case-scoped memo toolset (memo__*). Built only when a
	// memo mutator and a memo schema are configured for the workspace.
	ToolSetMemo = "memo"
	// ToolSetKnowledge is the workspace knowledge toolset INCLUDING the write
	// tools. The read tools are always available to every agent regardless of
	// what it requested (see Resolve); this ID is what additionally grants
	// create/update, and a host withholds it while processing a private case so
	// that case's contents cannot leak into workspace-wide knowledge.
	ToolSetKnowledge = "knowledge"
	// ToolSetCaseWrite is the writer toolset for the single case the turn is
	// pinned to: the full casewriter set (case__update_case, case__assign,
	// case__unassign, and the mode-appropriate case__update_case_status /
	// case__close_case). Every mention-driven host grants it, so a sub-agent can
	// carry out any case edit the user asked for. Note that a mention turn's
	// terminal `materialize` decision replaces title / description wholesale, so
	// a host offering both must tell the planner to pick one path per turn (see
	// threadcase's system prompt).
	ToolSetCaseWrite = "case_write"
	// ToolSetCaseMulti is the cross-case ("workspace-scoped") toolset used by the
	// workspace-channel agent. Unlike core/case_write (pinned to one case),
	// its tools take case_id as a call-time argument so a single turn can operate
	// across every case the requesting user can access. Advertised only via
	// KnownToolSetIDsWorkspaceChannel (never the default lists) so it is not
	// offered to the per-case mention / proposal planners.
	ToolSetCaseMulti = "case_multi"
	// ToolSetSlackWrite is the read-only Slack set PLUS slack__post_message,
	// pinned to the channel of the case the run is on. Like ToolSetKnowledge it
	// REPLACES the read-only set rather than adding to it, so no tool is offered
	// twice. Only the assist agent asks for it: assist exists to write its
	// findings back into the case channel, whereas a mention turn's reply is
	// posted by its host, not by a tool the model may call at will.
	ToolSetSlackWrite = "slack_write"
	// ToolSetCoreJob is the action toolset an UNATTENDED run gets: the read tools
	// plus create / update / status / assignee / steps, but NOT archive,
	// unarchive or delete_action_step. Those three are withheld because a Job
	// acts on its own judgement with nobody reviewing it, and a wrong archive is
	// work the team can no longer see.
	ToolSetCoreJob = "core_job"
	// ToolSetSlackPost is the channel-pinned poster (slack__post_to_case_channel).
	// A Job's output reaches people only through it, which is why an unattended
	// run has it while an interactive turn — whose reply its host posts — does not.
	ToolSetSlackPost = "slack_post"
	// ToolSetWSMeta is the workspace-metadata read set (list_workspaces /
	// get_workspace). It is what the case-draft planner picks a workspace with:
	// that flow is not pinned to one workspace, so it must read the candidates'
	// field schemas and configured sources before it can propose anything.
	ToolSetWSMeta = "wsmeta"
)