Task types: Code vs Office

Zagens separates engineering and document workflows with a task type. When you start a session, choosing Code or Office loads a different system prompt and tool surface.

Which to pick

Casual chat and document work belong in Office; refactors, debugging, and repo tooling belong in Code.

Switching rules

Changing task type starts a new session — do not mix types in one chat, so the model context prefix stays stable.

Pick the type again in the composer or new-session flow.

Tool differences (summary)

Code tools include grep_files, exec_shell, Git, edit_file / batch_edit / apply_patch, explore_codebase / edit_and_check, browser_* (desktop), symbol index, sub-agents, and more.

Office keeps read_office, write_office, load_office_payload, glob_files, file_search, load_skill, optional web tools, and describe_image. No shell, Browser control, or patch-style engineering tools.

See Agent tools and Office I/O.

Settings differences

Office sessions hide routing, topic memory, symbol index, and LHT settings in the sidebar. Usage, MCP, skills, and API key remain available.

Next steps