The @shake AI Engineer
@shake is Shake's built-in AI engineer. It is not a chat assistant — it is a team member with a card queue, a mention handle, and growing project memory.
How to trigger @shake
Assign a card to @shake
Open any card and assign it to @shake from the assignee dropdown. @shake will review the card, read its description and timeline, check the project context, and post a response in the card timeline. If it can take action (create a file, propose a PR plan, break down subtasks), it will.
Mention @shake in a message
In any card timeline message, type @shake followed by your question or request. @shake will respond to your mention directly.
What @shake can do
@shake has access to a set of tools scoped to your workspace:
| Tool | Description |
|---|---|
read_card | Read a card's full context including its timeline |
create_card | Create a new card in the board |
update_card | Update a card's name, description, priority, or column |
list_cards | List cards in a project with optional filters |
search_cards | Search cards by keyword |
read_file | Read a file from the linked GitHub repo |
list_files | List files in the repo (supports path filter) |
create_file | Create a new file in the repo |
update_file | Update an existing file in the repo |
create_pull_request | Open a pull request with proposed changes |
post_timeline_message | Post a message on a card timeline |
AI credits
Each @shake run consumes AI credits from your workspace's monthly allowance. Credit usage is proportional to the number of tokens consumed.
- Free plan: 500 credits/month
- Team plan: 5,000 credits/month
You can monitor your credit balance in Settings → Billing.
@shake's memory
@shake builds persistent memory about your project over time:
- The languages, frameworks, and conventions used
- Key architectural decisions and their rationale
- Rejected approaches and why they were rejected
- Team member names and roles
- Naming conventions and code style
This memory compounds. After several weeks of @shake participation, it becomes a senior engineer on your project specifically — not a generic assistant.
Privacy and safety
- @shake can only access files in the GitHub repos you have connected
- It operates with your OAuth token scopes — no elevated permissions
- @shake never merges to protected branches without explicit approval
- All @shake actions are recorded in the card timeline, auditable by any workspace member