trackslash

The open issue tracker your coding agents can actually use.

trackslash is a fast, self-hostable issue tracker built as a single Go application backed by PostgreSQL. Its HTTP API, built-in MCP server, and project context give developers and coding agents access to the same project work.

Warning

trackslash is under active development and is not ready for production or commercial use. Interfaces, migrations, and deployment requirements may change. If you run it yourself, you are responsible for backups, upgrades, and recovery.

What it does

• Tracks projects, issues, sub-issues, comments, links, tags, priorities, due dates, and sprints.
• Keeps project and issue context addressable from the UI, HTTP API, and MCP.
• Exposes MCP tools, resources, and prompts for issue work, planning, context, attachments, users, and tokens.
• Supports project membership, read-only roles, public project views, passkeys, password login, and API tokens.
• Streams realtime changes through PostgreSQL-backed events.
• Stores attachments locally or in S3-compatible object storage.
• Ships as one Go application plus PostgreSQL, with frontend assets and migrations embedded in the production image.

Development preview

The trackslash project is publicly readable as a development preview. It demonstrates the current product while trackslash remains experimental; it is not a hosted product offering or a production-readiness claim.

Connect a coding agent with MCP

Create an API token from Tokens in the trackslash UI, then put it in an environment variable rather than a committed configuration file:

export TRACKSLASH_TOKEN='<your-token>'

The MCP endpoint is https://<host>/mcp. For a local instance, use http://localhost:8080/mcp.

Codex

codex mcp add trackslash \
  --url https://<host>/mcp \
  --bearer-token-env-var TRACKSLASH_TOKEN

Claude Code

claude mcp add-json trackslash \
  '{"type":"http","url":"https://<host>/mcp","headers":{"Authorization":"Bearer ${TRACKSLASH_TOKEN}"}}'

Cursor

Add this server to .cursor/mcp.json for one project or ~/.cursor/mcp.json globally:

{
  "mcpServers": {
    "trackslash": {
      "type": "http",
      "url": "https://<host>/mcp",
      "headers": {
        "Authorization": "Bearer ${env:TRACKSLASH_TOKEN}"
      }
    }
  }
}

Restart the client after changing its MCP configuration. Keep the token out of source control and revoke it from Tokens when it is no longer needed.

Self-hosting

trackslash can be self-hosted under the MIT License with PostgreSQL and either local or S3-compatible object storage. For a local source-based instance, you will need Go 1.26.3, Node.js 20 or newer, and Docker:

cp .env.example .env
make up
make run

The app will be available at http://localhost:8080. Run make seed to add demo data.

Readiness caveat

Self-hosting is available for development and evaluation, not as a production-readiness promise. Interfaces, migrations, storage behaviour, and deployment requirements may change. Back up both PostgreSQL and object storage, test restores, review migrations before upgrades, and keep your own recovery plan.

Development commands

Useful commands:

make test
make build
make assets
make assets-check
make down

Frontend dependencies are pinned in package-lock.json. Generated CSS and JavaScript are committed under internal/server/static so the Go binary and Docker image do not need Node.js at runtime. Run make assets after changing templates, Tailwind source, or frontend dependencies; CI runs make assets-check to catch stale output.

Deployment reference

The deployment notes document the current container image, migration job, origin and proxy settings, session limits, development-preview terms flag, request limits, and object-storage configuration. Treat them as an evolving operator reference, not a production support commitment.

Security and legal

• Report vulnerabilities through the security policy, published for the preview at trackslash.com/security, not a public issue.
• The Bad Bundle-operated development preview is governed by its Preview Terms and Privacy Notice, published at trackslash.com/terms and trackslash.com/privacy. Those documents do not govern independent self-hosted installations.
• Use of the trackslash name and branding is described in the trademark policy.

License

MIT

Issue tracking

Issues are tracked in the public trackslash development preview, not GitHub Issues.