Work, Code, and Plan

Work style shapes how KeenKind approaches a task. Conversation mode determines how the current turn proceeds. You can combine them.

Work styles

• Work: writing, questions, research, organization, and office tasks.
• Code: project reading, code changes, diagnostics, tests, and builds.

Code style does not mean the terminal is preferred. Ordinary reads and edits use file capabilities. Commands are used for running, building, testing, and process diagnostics.

Agent mode

The default mode. KeenKind chooses available capabilities and acts within the current permissions.

Plan mode

Use it for complex requirements, broad changes, or tasks where you want to discuss before editing.

1. Switch to Plan.
2. Describe the goal, constraints, and acceptance criteria.
3. Answer the key questions.
4. Review the final plan.
5. Confirm before implementation begins.

Tip

A useful plan includes the goal, scope, key steps, risks, and verification method.

Persistent goals and plans

Two modes support longer tasks:

• Persistent goal: continue toward one clear goal without splitting it into a plan.
• Persistent plan: divide the goal into ordered tasks, then execute and verify each one.

Both modes organize newly discovered information as the task continues. You can still update the goal, constraints, or completion criteria in later messages.

In Settings > Persistent tasks, you can choose separate models and reasoning levels for the goal planner and verifier. If unset, they use the current chat’s model.

Image mode

After configuring an available image model, choose image mode to generate or edit images. Results appear at the end of the reply and can be referenced or processed again.

Modes and permissions

Modes do not increase permissions. Protected actions still follow current permission settings, including in Code style or Agent mode.