BitsWeave for Operations

Know what’s blocked. Know who owns it.

Keep projects moving without chasing every update. BitsWeave gives your agents the plans, decisions, and handoffs they need to find blockers and help your team clear them.

Try it free ▶ Play video

Plans, checklists, vendor updates, and owners

Your context

Project planChecklistEmailThrough your connected apps

Your agents

Claude CodeCodexGemini CLICursorZedGrok Build

Less chasing. Clearer handoffs.

Stop chasing the latest update.

The plan says Monday. The vendor says done. The checklist says otherwise. You should not have to reconcile every update yourself.

See how the work fits together.

BitsWeave connects project updates, owners, and requirements. Your agents can see what is finished and what still blocks the handoff.

Turn loose ends into next steps.

Give your agent the context to find the missing check and prepare the assignment. Hand over the work with an owner and the evidence attached.

Start with the agent you already use

Connect your agent. Bring your context.

Add BitsWeave to your agent, then finish setup. You can create your account when you connect.

Connect your agent

Open ChatGPT, Cursor, or Claude. Other hosts are under More agents.

Set up BitsWeave to connect with your agent and teach it to use shared context for better memory and performance.

Setup with CLI. Copy this command and run it in your terminal.

Setup with skill. Copy these instructions into your agent. It asks before installing.

# Finish BitsWeave setup

First decide whether this is a desktop environment (a laptop or workstation with a terminal, not only a phone browser or a web chat).

If it is a desktop, ask the person if they want you to install af-tap. Do not run the installer until they say yes.

If they say yes, follow the skill below.

# Install af-tap and connect BitsWeave

You are setting up BitsWeave on this machine for the person you are talking to. Run the commands in order. Do not mint a PAT. Do not edit MCP config or instruction files yourself. Report what you did at the end.

## 1. Install af-tap

Download and run the installer. It places the `af-tap` binary on the PATH:

```bash
curl -fsSL 'https://get.bitsweave.com/install.sh?utm_source=homepage&utm_medium=website&utm_campaign=agent-install&utm_content=operations-skill' | bash
```

## 2. Authenticate

Run the command below. It prints a URL — open it in the browser yourself if you can, otherwise give the URL to the user and wait.

```bash
af-tap login
```

## 3. Run af-tap setup

Run `af-tap setup`. It discovers supported agents and writes the Bitsweave MCP server after two yes passes. The endpoint is:

```text
https://bitsweave.com/api/mcp
```

Do not edit host MCP files or instruction files yourself. `af-tap setup` owns those writes.

```bash
af-tap setup
```

## 4. Start af-tap

Start the daemon. Offer persistence (LaunchAgent or systemd). Do not install a login/boot service without a yes.

```bash
af-tap start
```

## 5. Report back

Tell the user: whether af-tap is installed and logged in, what `af-tap setup` wrote, and whether the daemon is running. If a step failed, say which one and what the error was.

One story · four connected demos

The office opens Monday. Are we ready?

Follow one opening from a go-live condition to an assigned blocker and a readiness view the whole team can use.

Scripted product demonstration · sample records and connected tools

01 / 04 · First, agree what “ready” means.

Shared memory across agents

The site coordinator needs the opening conditions, not another briefing. BitsWeave carries the decision from the operations lead’s session into theirs.

1/ 4

Set the opening condition

Monday is the target. Passing the access check is the condition. Both belong in the handoff.

ConversationFollow here

Operations lead · ClaudeEarlier session

Open the East office Monday. Jordan must complete the access check before staff arrive.

Extracting the decision

Source: this conversation · linked to East office opening

Shared contextContext

East office openingShared memory

From Operations lead · Claude

Open the East office Monday. Jordan must complete the access check before staff arrive.

Saving this decision…

Shared context · 3 records

Remembered decision

Open the East office Monday. Jordan must complete the access check before staff arrive.

ResultContext

Up nextA contextual answer

Follow the highlighted area. The result appears here next.

02 / 04 · Then, check the evidence.

Connected context from your apps

Plans, checklists, and vendor replies arrive separately. BitsWeave builds a live project model so your agent can trace what still blocks the opening.

1/ 4

An app event creates the first records

Notion sends an event for Opening plan. BitsWeave adds it to the model.

App eventsContext

Event stream 0

Business data modelFollow here

Records 0 records

Incoming app events0 received

Listening for updates from your apps…

Waiting for the first app event…

New records join the existing model

ResultContext

Up nextA contextual answer

Follow the highlighted area. The result appears here next.

03 / 04 · Next, put an owner on the work.

Tool use across your apps

Ask your agent to assign the badge test with its deadline and supporting evidence. Review the handoff before it reaches your tracker.

1/ 4

Name the owner and deadline

Assign the badge test to Jordan for Friday. Include the vendor’s installation update.

ConversationFollow here

Your next request

•••Writing the request…

Connected toolContext

Connected providers Paused

RequestAssign the badge test to Jordan for Friday and link the vendor update.

tools_searchFind a tool

{
  "query": "Assign the badge test to Jordan for Friday and link the vendor update.",
  "result": null
}

NotionConnected

CalendarConnected

AsanaConnected

SlackConnected

AirtableConnected

tools_callUse the tool

Tool lookup paused

Review & resultContext

Up nextReview the change

Follow the highlighted area. The result appears here next.

04 / 04 · Finally, make readiness easy to review.

Work faster, not harder

Keep the gate, owner, and vendor evidence together. The next status check starts with the project’s records.

1/ 4

The opening history is already here

The condition, installation update, and badge-test assignment came from the work you just watched.

Work so farFollow here

Built through the work

•••Gathering the work…

Build the viewContext

Shape the workspace

Your workspaceContext

Up nextEast office readiness workspace

Follow the highlighted area. The result appears here next.

Keep the work moving between teams.

Find the real blocker

Connect status updates to dependencies so “installed” does not quietly become “ready.”

Make ownership explicit

Keep the assignee, due date, and reason for the work together when responsibility changes hands.

Keep the evidence close

Bring the vendor update and checklist into the same view. Answer readiness questions without another status round.

Your next handoff should come with answers.

Bring one project into BitsWeave. Give your agents the context to help move it forward.

Try it free