Tag

Your personal assistant, in Slack.

Everyone brings their own Tag. Everyone works in the same conversation.

Read the Tag guide at hover.team/tag →

Get started · Join the Slack community · Capabilities · Issues

Work through it together

The context is already there: a question, a few links, a decision buried in a
thread. Mention your Tag where the discussion is happening. Teammates can add a
missing detail, question the answer, or take on the next step. Everyone can
follow how you got there.

Turn discussion into action. Pull together decisions, owners, and deadlines;
save a checklist or draft a document in your working folder.
Bring the missing context. Find earlier discussions in approved, indexed
Slack history, or use connected tools to find an email or inspect a repository.
Make it yours. Tag runs on a computer you control using your Codex setup,
files, skills, and connected accounts. Your teammates can see the results in
Slack.

Your Tag runs from your own agent environment, and only you can invoke it by
default. Teammates can bring their own Tag with their own setup. You share the
conversation and results; each assistant stays personal.
Learn how personal access works →

Runs locally, with clear boundaries

Tag's Slack bridge and Codex agent run on a computer you control, using the
files, tools, skills, and accounts you choose to make available.

Hover does not host your conversations or working files. Your agent
workspace and the files Tag creates remain on your computer.
Your files stay useful outside Tag. They are ordinary files in your working
folder, so you can open, edit, move, or reuse them with other tools.
External services are still external. Slack carries the team conversation;
Codex processes agent requests; and optional connected services process the
information required to use them, each under its own data policies.

Tag is local by design, not offline.
See how Tag works →

Bring your Tag to work

Start with a Mac or Linux computer that can stay awake and online, a working
Codex CLI login, and permission to install a Slack app. Agent-guided setup also
requires Node.js and npm.

Install the setup skill:

npx skills add klovr-co/hover-tag --skill hover-tag-setup -a codex -g

Open a new Codex session and ask:

Use the hover-tag-setup skill to set up Tag for me.

Codex checks prerequisites, proposes the setup with recommended defaults, and
drives installation locally. If Slack login is needed, it gives you a one-time
connection to approve in Slack and return in one reply, with a private clipboard
handoff available instead. Then bring your Tag online:

tag start
tag status
tag stop

Follow the setup guide and try your first Slack task →

Prefer installing from a source checkout? Run ./install.sh; the same guide
covers the full manual path. For Windows installation details and qualification
status, see installation.

More than a reply

What you want to do	Explore
Turn attachments and discussions into useful files	Working with files
Find context in conversations and approved sources	What Tag knows
Bring your tools, skills, and connected accounts	Adding integrations
Find an email and share the relevant details in Slack	Use Gmail from Slack

Tag connects Slack → your local agent → your files and permitted sources.
Optional MFS indexing makes approved history
and other sources searchable. Tag does not automatically remember every
conversation. See how it works →

Early, open source, yours to run

Tag is an early project for experimentation in a trusted environment. Codex is
the supported path; Claude Code is experimental. Your agent runs with local
account permissions and inherited bot/MFS credentials; Tag is not a hardened
sandbox. Connected services process requests under their own data policies.
Read the security model before connecting
sensitive accounts or files.

Tag includes privacy-bounded CLI telemetry for setup and reliability. It never
collects prompts, Slack messages, agent output, workspace paths, files, source
code, logs, credentials, configuration values, or command arguments. Use
tag telemetry status, tag telemetry on, or tag telemetry off to manage it,
or set TAG_TELEMETRY=off for an immediate process-level stop. Read the full
telemetry and privacy reference.

Documentation ·
Join the Slack community ·
Troubleshooting ·
Source ·
Contributing · Changelog ·
Releases ·
Security policy

Tag began with the Open Tag example
from Zilliz MFS, inspired by
Claude Tag.
Licensed under the Apache License 2.0; see NOTICE for
attribution.

Tag

Work through it together

Runs locally, with clear boundaries

Bring your Tag to work

More than a reply

Early, open source, yours to run

Yorumlar (0)