Skip to content

Tags

Inline #tags, parsed automatically from a Log's body.

Updated View as Markdown

Write a #tag

Anywhere in a Log’s body — #postgres, or nested like #infra/postgres — no separate tagging step.

Code and colors are skipped

Fenced/inline code and hex colors like #fff are never parsed as tags.

Browse them on /tags

Every tag in the workspace, sorted by count — click one to see every Log tagged with it.

What doesn’t count as a tag

The parser skips fenced code blocks and inline code entirely, so #include <stdio.h> in a code sample never becomes a tag. It also ignores anything that looks like a hex color (#fff, #3b82f6) so pasted CSS or design notes don’t spam your tag list.

The Tags page

/tags lists every tag in the current workspace with how many logs carry it, sorted by count. Click one to see every log tagged with it (/tags/:name). See GET /api/workspaces/:workspaceId/tags for the underlying endpoint.

Navigation

Type to search…

↑↓ navigate↵ selectEsc close