Tickets - vibe coding issue tracker & management
A text based Ticket tracking system. A lightweight, fast, and local ticket management system designed for solo, indie, and hobbyist developers. It is built to optimize vibe coding and AI-assisted development, providing instant visual cues and structured workflows when pair-programming with AI agents (like Antigravity, Cursor, Claude Code, and others).
No complex databases, servers, or configurations required. Simply keep a .tickets or .tkt file in your workspace, and let the color-coded highlighter keep you and your AI assistant perfectly aligned.
- 100% Offline & Local: Files stay in your project directory.
- AI Agent Friendly: Includes a built-in prompt to teach any AI coder how to read and update your tickets automatically.
- Case Normalization: Automatically converts lowercase tags (like
[b], [ft], [epic]) to uppercase badges as you type.
- Fully Customizable: Change default colors via settings or add your own custom prefix/tag rules with ease.
📬 Contact / Feedback: jihad.k.m@gmail.com
🎨 Default Rules
This extension applies highlighting to lines starting with the following prefixes:
$- ➔ Completed (Finalized / Green)@- ➔ In Progress (Working on it / Orange)#- ➔ Fixed / Ready for Test (Needs testing / Cyan)*- ➔ Planned for Later (Backlog / Muted Gray)!- ➔ ~~Cancelled / Irrelevant~~ (Strikethrough Gray)^- ➔ Failed Testing / Rework (Needs fixes / Bold Red with Red background)~- ➔ Epic / Undecided (Needs discussion / Purple)
[BUG] or [B] ➔ Red badge[FT] or [F] ➔ Violet badge (auto-normalizes from [ft] or [f])[ENH] or [E] ➔ Blue badge (auto-normalizes from [enh])[EPIC] or [EP] ➔ Purple badge (auto-normalizes from [epic])// Comments and /* Block Comments */ ➔ Muted italic slate
📋 Example Ticket File (sample.tickets)
Below is a complete sample showing how you can organize tasks in your project. If you save it as tasks.tickets or tasks.tkt, it will be highlighted automatically:
================================================================================
TICKETS - BUG & SUGGESTION TRACKER
================================================================================
RULES & CONVENTIONS:
--------------------------------------------------------------------------------
Prefixes:
@- : Working on it
#- : Fixed and ready to test
*- : Planned for later
!- : Irrelevant or cancelled
$- : Completed / final / no testing required
^- : Fails testing / needs rework
~- : Read but not decided / needs further development (e.g., Epic)
Tags (inline):
[B] or [BUG] : Bug
[F] or [FT] : Feature
[E] or [ENH] : Enhancement
[EPIC] or [EP] : Epic / Milestone
Notes/Comments:
Use // at the end of the line for notes or details.
================================================================================
~- [EPIC] Phase 1: Authentication & Layout
$- [FT] Initial user registration and password hashing // Complete
$- [FT] Responsive dashboard panel with glassmorphism theme // Complete
@- [FT] OAuth integration with Google & Github // Currently working on config
#- [BUG] Fix login spinner hang on slow network connections // Ready to test!
^- [BUG] Profile avatar upload exceeds memory limit on large files // Failed
~- [EPIC] Phase 2: Billing & Subscriptions
*- [FT] Integrate Stripe payment gateway
*- [ENH] Add support for recurring monthly subscriptions // Backlog item
!- [FT] Legacy XML data parser migration // Cancelled
/*
Block comments like this are fully supported.
Use them for general notes, release logs, or design drafts.
*/
⚙️ Custom Configurations (Settings)
You can customize all the default colors or add your own custom highlighting prefixes and tags directly in VS Code Settings!
Open your settings.json file in VS Code and add configurations under agentTicketHighlighter:
{
// Customizing default prefix colors
"agentTicketHighlighter.colors.completed": "#10b981",
"agentTicketHighlighter.colors.working": "#fb923c",
"agentTicketHighlighter.colors.failed": "#f43f5e",
// Adding completely new custom rules
"agentTicketHighlighter.customRules": [
{
"prefix": "?-",
"color": "#eab308",
"bold": true,
"description": "Highlights lines starting with '?- ' (e.g., questions) in gold."
},
{
"regex": "\\[CRITICAL\\]",
"color": "#ffffff",
"backgroundColor": "#ef4444",
"bold": true,
"border": "1px solid #ffffff",
"description": "Highlights any '[CRITICAL]' tag with a red block badge."
}
]
}
You can choose to highlight either just the prefixes (e.g. $-, @-) or the entire line with the status color:
Option A: Prefix Only Highlighting
Option B: Full Line Highlighting
- Status Bar Toggle: When editing a
.tickets or .tkt file, a status bar item will appear in the bottom right corner (e.g., Tickets: Prefix Only or Tickets: Full Line). Simply click it to toggle!
- Command Palette: Open the Command Palette (
Ctrl + Shift + P) and run Tickets: Toggle Full Line Highlighting.
- Configuration Settings: Set
"agentTicketHighlighter.highlightFullLine": true in your global settings.json to enable full line coloring by default.
🤖 System Prompt for AI Agents
Copy and paste this prompt when starting a chat with any AI assistant (like Antigravity, Claude Code, or Copilot) to ensure it handles your ticket tracking files correctly:
You are working on a project that utilizes a custom ticket/bug tracking format stored in files with extension '.tickets', '.tkt'(e.g. 'bugtracker.tickets').
Please adhere to the following rules when reading, analyzing, or modifying these files:
1. Always read the '.tickets' file at the start of your turn to review issues, features, and logs before making changes.
2. Update the status prefixes at the start of lines to reflect your progress:
- Use '@-' as prefix if you are currently working on an issue/feature.
- Use '#-' as prefix when you have completed a fix/feature and it is ready for testing.
- Use '*-' for items planned for later.
- Use '!-' for cancelled or irrelevant items.
- Use '$-' for items that are completed, final, and require no further testing.
- Use '^-' if an item has failed testing and needs rework.
- Use '~-' if an item is read but not yet decided on, or needs further epic-level planning.
3. Use inline tags in your descriptions:
- Use '[BUG]' or '[B]' for bug fixes.
- Use '[FT]' or '[F]' for new features.
- Use '[ENH]' or '[E]' for improvements/enhancements.
- Use '[EPIC]' or '[EP]' for epics/milestones.
4. Add notes or comments at the end of lines using '//' or wrap multi-line text blocks with '/* ... */'.
5. Once your task or a subtask is complete, update the relevant ticket line with the appropriate prefix and tag before ending your turn.
📄 License
This extension is licensed under the MIT License.
