BitsWeave for Engineers

Give your coding agents the why behind the code.

Carry architecture decisions, tickets, pull requests, and CI evidence between sessions. BitsWeave helps your agents pick up the reasoning and move the work toward review.

Try it free ▶ Play video

Decisions, tickets, pull requests, and CI evidence

Your context

TicketGitHubCIThrough your connected apps

Your agents

Claude CodeCodexGemini CLICursorZedGrok Build

The code is there. Keep the reasoning with it.

Keep the why with the code.

Tickets, pull requests, and CI tell parts of the story. The reasoning behind a change should survive the session that produced it.

Connect the whole change.

BitsWeave links engineering decisions to their issues, implementation, and test results. Your agents can find the evidence behind the code.

Get back to shipping.

Start the next session with the context already there. Your agent can explain the behavior and prepare the next action without another briefing.

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=engineers-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

Take a checkout fix from decision to review.

Follow one retry rule through an agent handoff, a pull request, CI evidence, and a release workspace.

Scripted product demonstration · sample records and connected tools

01 / 04 · Start with the behavior the team agreed.

Shared memory across agents

The reviewer should not have to rediscover the retry rule. Keep the constraint from the implementation session available to the next agent.

1/ 4

Agree on safe retries

Retry three times and reuse the payment idempotency key. That constraint prevents a second payment.

ConversationFollow here

Engineer · Claude CodeEarlier session

Retry checkout callbacks three times. Reuse the payment idempotency key.

Extracting the decision

Source: this conversation · linked to Checkout retry fix

Shared contextContext

Checkout retry fixShared memory

From Engineer · Claude Code

Retry checkout callbacks three times. Reuse the payment idempotency key.

Saving this decision…

Shared context · 3 records

Remembered decision

Retry checkout callbacks three times. Reuse the payment idempotency key.

ResultContext

Up nextA contextual answer

Follow the highlighted area. The result appears here next.

02 / 04 · Now follow the implementation.

Connected context from your apps

Linear issues, GitHub pull requests, and Buildkite builds become one live release model. Your agent can trace a fix from ticket to passing tests.

1/ 4

An app event creates the first records

Linear sends an event for PAY-143. 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, prepare the review handoff.

Tool use across your apps

Ask your agent to request a GitHub review with the ticket and passing build as context. Check the proposed handoff before it acts.

1/ 4

Request review and attach the proof

Request a review of PR #142 and include the retry test result linked to PAY-143.

ConversationFollow here

Your next request

•••Writing the request…

Connected toolContext

Connected providers Paused

RequestRequest a review of PR #142 and include the retry test result linked to PAY-143.

tools_searchFind a tool

{
  "query": "Request a review of PR #142 and include the retry test result linked to PAY-143.",
  "result": null
}

LinearConnected

BuildkiteConnected

GitHubConnected

SentryConnected

GrafanaConnected

tools_callUse the tool

Tool lookup paused

Review & resultContext

Up nextReview the change

Follow the highlighted area. The result appears here next.

04 / 04 · Finish with a view the team can reuse.

Work faster, not harder

Turn the connected issue, review, and build into a workspace for this release. Keep the retry decision within reach.

1/ 4

Reuse the work already captured

The decision, implementation links, and review action are already part of the checkout context.

Work so farFollow here

Built through the work

•••Gathering the work…

Build the viewContext

Shape the workspace

Your workspaceContext

Up nextCheckout release workspace

Follow the highlighted area. The result appears here next.

Keep engineering context attached to the change.

Preserve the tradeoff

Let the next coding session find why the team chose this behavior, alongside the implementation.

Review with evidence

Connect a ticket to its pull request and build result. Give reviewers a path back to the facts.

Work across agents

Carry the same project context between compatible agents instead of maintaining a separate briefing for each.

Start with the reasoning. Get to the code.

Connect your first engineering tool and give the next agent session a place to pick up.

Try it free