create_and_activate_intent
Create and activate a new intent for the current session after user confirmation, tracking AI-generated code and avoiding conflicts by allowing forced override when needed.
Instructions
Create a new intent from the user's request and mark it as active for THIS session.
Call this when check_active_intent returns no active intent for your session. Before calling:
Summarize what the user is asking for
Ask the user to confirm the intent details (title, description, type)
Then call this tool with the confirmed details
This ensures all AI-generated code gets properly tracked and attributed.
Multi-active model: many intents can be active on a repo at once (one per session/teammate). Creating + activating one only sets YOUR session's current focus — it never blocks or displaces another session's active intent, so there is no lock conflict to resolve.
If the tool returns conflicts (action="conflict"), it found an existing team-member intent that overlaps semantically or in files. Present the conflict details to the user and ask whether to proceed. If yes, retry with force=true to bypass conflict detection.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| force | No | Bypass conflict detection. Set to true after the user has reviewed detected conflicts and chosen to proceed anyway. | |
| title | Yes | Short, descriptive title for the intent | |
| repoPath | Yes | Local path to the repository root | |
| forkAuthor | No | Fork attribution; usually resolved by Muninn automatically — pass only for override / testing. | |
| repoOrigin | No | Git remote origin URL. Auto-detected from repoPath via git if not provided. | |
| constraints | No | Requirements or constraints for this work | |
| description | Yes | What this intent accomplishes | |
| workspaceId | No | Workspace identifier; usually resolved by Muninn automatically — pass only for override / testing. | |
| templateType | No | Type of work |