Features
Everything AWMate Beta can do — and how you stay in control.
Each capability is designed to be transparent and reviewable. AWMate acts on your machine only with your approval.
Project understanding
- What it does
- AWMate analyzes the structure and files of the folder you select.
- Why it is useful
- You get grounded answers about a real codebase, not generic advice.
- Typical workflow
- Select a project folder → open a chat → ask about structure, entry points or specific files.
- User control
- Only the selected folder is read. You can switch or remove projects at any time.
File awareness
- What it does
- AWMate can inspect relevant source files and understand relationships between components.
- Why it is useful
- Answers reference the actual code, imports and call graph in your project.
- Typical workflow
- Ask about a symbol or file → AWMate opens the files it needs → cites them in the response.
- User control
- You can view every file AWMate accessed for a given response.
Code modification
- What it does
- AWMate can propose and apply scoped changes across one or many files.
- Why it is useful
- Refactors, fixes and small features can be prepared as a reviewable set.
- Typical workflow
- Describe the change → AWMate proposes a diff → you approve, edit or reject before it lands.
- User control
- No file is written without your explicit approval.
Command execution
- What it does
- AWMate can run approved development, build and testing commands in your project.
- Why it is useful
- You can hand off routine commands without leaving the chat.
- Typical workflow
- AWMate requests a command → you review and approve → output is captured for reasoning.
- User control
- Every command needs approval. You can deny or edit any request.
Conversation context
- What it does
- Chats retain the project state, open files and prior turns.
- Why it is useful
- Follow-up questions stay grounded in what you were just doing.
- Typical workflow
- Continue a chat → AWMate reuses context → ask a new question in the same thread.
- User control
- Delete or start new chats at any time. Each project keeps its own history.
Git assistance
- What it does
- Help with branches, diffs, commit messages and recovery of local work.
- Why it is useful
- Keeps git operations transparent and reversible.
- Typical workflow
- Ask AWMate to summarize a diff, draft a message or explain a merge conflict.
- User control
- Destructive git commands still require explicit approval.
Background activity
- What it does
- Long-running tasks report progress in the interface.
- Why it is useful
- You always know what AWMate is doing on your machine.
- Typical workflow
- Kick off a task → watch progress in the activity panel → stop it whenever you want.
- User control
- Tasks can be cancelled at any point.
Updates
- What it does
- AWMate ships regular updates through signed releases.
- Why it is useful
- You get bug fixes and new capabilities without manual patching.
- Typical workflow
- Updates are announced in the changelog and installed on your schedule.
- User control
- You decide when to install a new version.