Work sessions & af-tap

A work session is BitsWeave's record of a single stretch of work: who's working, what they're touching, and when it started and ended. af-tap is the small connector that creates those records for you by mirroring the agent sessions you already run.

One session in, one session out

af-tap is a long-lived command you start on your own machine. While it runs, it watches your local Claude Code sessions and reflects each one into BitsWeave as exactly one work session — a one-to-one shadow.

• When a new Claude Code session starts doing work, af-tap opens a matching work session owned by you.
• While that session is active, af-tap keeps it live and up to date.
• When the session goes idle, af-tap closes its shadow — other sessions keep going, unaffected.

Because the link is one to one, restarting af-tap re-adopts the sessions that are still active instead of creating duplicates. You always have exactly one work session per Claude Code session.

What a work session shows

Each work session carries enough to make your work visible to your team without anyone reading your transcript:

• Source — which kind of agent it came from (Claude Code today).
• Focus — the repo, branch, and files the session is currently touching, refreshed as you move around.
• Status — whether the session is active or has been closed.

That focus signal is what lets BitsWeave tell you when two sessions — yours and a teammate's, or yours and an agent's — are working the same repo or branch at the same time.

Privacy

af-tap reflects signals, not your secrets. Before anything is recorded it redacts obvious secret shapes — access tokens, API keys, bearer headers, and KEY=value secret assignments — so the shared view stays safe to share.

Where this fits

Work sessions are the human side of BitsWeave's activity. Connected agents produce their own sessions through the MCP surface, and everything you and your agents do lives inside an organization.

To start mirroring your own sessions, follow Getting Started.