← All posts

Write the spec like a regular doc. Free to start, no credit card.

By continuing, you agree to the Terms of Use and acknowledge the Privacy Policy. Analytics choices are separate.

the specgit blog

Introducing Canvas: your whole team on the board

· the specgit team

A Q4 roadmap board in specgit. A spec opens beside the board and gets a new requirement, Ask Agent adds a card for it and connects it to the specs it affects, and the board and its specs go to review together from the Status panel, with a reviewer picked on the way.

Keep the spec next to the code

Write like a normal doc in GitHub, and specgit handles the Git for you. Free to start.

By continuing, you agree to the Terms of Use and acknowledge the Privacy Policy. Analytics choices are separate.

See plans & pricing

Free to start, no credit card. Zero Content Retention: we never keep a copy.

Get started · See pricing

Canvas brings your Obsidian Canvas boards into specgit. Open a board in the browser, click any note to edit it beside the map, and review the board and every note on it together. Everything saves straight to your GitHub repo, in the exact format Obsidian wrote.

Boards are how a lot of teams think: a roadmap laid out as specs, a research map of interview notes, an architecture sketch with arrows between services. Until now, working on that map meant opening Obsidian, which left out everyone on the team who doesn't use it. With Canvas, the whole team can open the board, edit the notes on it, comment on any card, and publish changes, and every change still goes through review in GitHub.

Ask Agent works on boards too. It reads every card, group, and arrow on the board, along with the notes behind them, and proposes changes for you to approve.

Canvas is available today on every specgit plan, including Free. Ask Agent on boards is included with Pro and Pro Plus. Today we're also releasing Repo context for Ask Agent, comments that carry across every revision of a document, and a folder tree for getting around your repo.

Your board, in the browser

Boards work the way you expect from Obsidian. Drag cards, draw labeled arrows, group related notes, color-code them, and edit text cards in place. Paste or drop an image and it lands on the board. Starting from scratch? Lay out a folder turns every note in any folder of your vault into a card, with each subfolder as its own group.

Click a note card and the note opens beside the board with everything specgit's editor has: autosave, comments, properties, and Changes. A link in the note to another card pans straight to that card. On a phone, the note opens full screen with Back to board.

specgit writes the board back in Obsidian's own format. Cards you didn't touch stay exactly as they were, and moving a card changes a single line in the file. Teammates who live in Obsidian keep working there, with no reformatted files.

Boards are built for teams. Teammates edit together live, with cursors and a marker on whoever is editing each card. Comments attach to cards and are saved in GitHub as review threads on the pull request, so technical teammates see them there too. When the work is ready, the board's Status panel publishes the board and its notes together: the notes first and the board last, so the published version (the main branch in GitHub) never has a card pointing at a note that isn't there yet.

A roadmap board with Now, Next, and Later groups. Each spec is a note card showing a preview of the note, with review status pills and labeled arrows between dependent specs.
Every note on the board is a card with a live preview of the note behind it.

What teams do with Canvas

Plan a roadmap on one board

You're a product manager, and your roadmap lives on a board: each card is a spec note, grouped into Now, Next, and Later, with arrows showing which specs depend on which. On Tuesday, sales brings in a new requirement. You open the board and click the spec it changes. The full note opens in a panel beside the board, so the map stays in view while you edit. Then you ask the agent to add a card for the requirement and connect it to the specs it affects. The new card shows in violet until you apply it. When it looks right, you open Status, add your tech lead as a reviewer, and submit the board and every spec you touched in one step. Each file goes to review on its own, as its own pull request in GitHub. Your tech lead gets a GitHub notification, follows the link into specgit, reads each change, and approves. If they'd rather review in GitHub, it's all there too. If you've turned on Publish when approved, the whole set goes live right then. If not, either of you can click Publish.

The board's Status panel after submitting: the board and two specs listed under In review, each waiting on the same reviewer, with Publish 3 in the footer and a Submitted for review notice offering Undo.
The board and the specs you changed go to review as one set, each file reviewed on its own.

Make sense of research

You're a researcher with a folder of interview notes. Lay out a folder puts every note on a board, grouped by subfolder. Ask Agent where the interviews disagree, and it puts the disagreement on the board as a card connected to the interviews behind it. Teammates comment right on the cards, and each thread stays tied to its card as the board changes.

Onboarding interview notes laid out as a board grouped by Shippers, Carriers, and Warehouse teams. Ask Agent adds a card for where the interviews disagree, and a teammate's comment thread rings that card.
Lay out a folder, ask where the interviews disagree, and discuss the answer on the card.

Keep an architecture board current

You're an engineer, and the board maps your services with a note behind each one. Turn on Repo context with All files and ask the agent to check each note against the code. It reads the code and proposes an edit in every note that has drifted. You approve them one at a time, each note opens beside the board with the change in place, and you send both notes to review from Status.

A system map board of service notes. With Repo context set to All files, Ask Agent reads the service code, proposes edits to the Notifications and Pricing notes, each approved edit opens the note beside the board, and both notes go to review from the Status panel.
Ask Agent reads the code, finds the two notes that drifted, and proposes the fix in each one.

Review a spec over several rounds

You're a tech lead reviewing a spec that goes through three revisions. The comments you leave stay open into the next revision, still attached to the text they were about. Resolved threads stay visible by revision, and View in that version shows the spec exactly as it was when someone commented.

A spec's comments sidebar with a conversation carried from an earlier review, resolved threads grouped by revision, and the spec shown as it was when a comment was made.
Conversations carry from one revision to the next, and earlier versions are one click away.

Ask Agent works the board with you

Ask Agent reads the board the way you do: every card, group, and arrow label in reading order, plus the notes on the board. Ask it to add cards, connect ideas, or regroup a section, and the proposed change shows up as ghost cards on the board until you apply or dismiss it. Ask it to fix something across several notes, and it proposes each edit in the note where it belongs.

With Repo context on, Ask Agent can also read other files in your repo for background, from other docs to code and config.

Ask Agent's board change card listing the cards and arrows it proposes, with the new cards drawn as ghost cards on the board until the change is applied.
A proposed board change shows on the board as ghost cards until you apply or dismiss it.

You're always in control

Every change is yours to approve

Ask Agent runs only when you ask it to. By default, every board change and every note edit arrives as a proposal, and nothing changes until you approve it. On a board, Ask Agent proposes changes as ghost cards until you apply them. When you ask, it can add, connect, group and remove cards and arrows: it deletes text and link cards and takes note cards off the board, and it never deletes a note file.

specgit never keeps a copy

Your boards and notes live in your GitHub repo, and specgit never keeps a copy. That's our Zero Content Retention promise. When Ask Agent reads notes or repo files, it reads them from GitHub for that request only. Repo context is off by default, and Documents keeps code out of reach. The model providers never train on the inputs or outputs of Ask Agent requests. The details are on privacy and security.

Access follows GitHub

Everyone signs in with their own GitHub account, and every save is recorded in GitHub under their name, as a commit. People without permission to edit the repo get a read-only board. Reviews and approvals follow your repo's review rules, the same as code.

More in this release

Status, one click away

The Status button in the top bar shows where a document or board stands: In progress, In review, Waiting on review, Ready to publish, or Conflicts. Click it to see the files in the review, what changed, and the next step. Submit lets you add reviewers, and GitHub notifies them. Changed your mind? Undo right after you submit, or Move back to draft any time before it's published. On a board, every file in the set has its own row and state, and the footer acts on the files you check.

Ask Agent, Status, and Comments now open as separate panels, side by side, and each one resizes and remembers its width. Share shows the link it copies, along with a README badge and links to the file and its review on GitHub.

Available on all plans.

A board's Status panel beside the Ask Agent panel: two service notes under In review, each waiting on a reviewer, with Move back to draft and Add reviewer for the checked files and Publish 2 in the footer.
Status lists every file in the review, who has it, and the next step.

Replies read more like a teammate's review

Ask Agent now leads with the finding, in plain prose, the way a teammate's review would.

Available wherever you use Ask Agent.

Repo context

A new setting in the Ask Agent panel lets Ask Agent read other files in your repo for background. Choose Documents for your other docs, or All files to include code and settings files. Type @ to point it at a specific file.

Available on Pro and Pro Plus. Learn more

Comments that carry across revisions

Open conversations carry forward to each new revision of a document, still open and still anchored to the text they were about. Resolved comments stay visible, grouped by revision. View in that version opens the document as it was when the comment was made, and Resolve all closes every open conversation in one step.

Available on all plans.

An earlier version of a spec beside today's text, showing the line a reviewer commented on and how it changed since.
Changes since then compares the version a reviewer saw with the text today.

A folder tree for your repo

Repos with more than one folder open as a folder tree beside the folder's contents. Press Cmd/Ctrl-K or t to jump to any file, filter by Has changes, Mine, or HTML, and create new docs right in the folder you're looking at. A link to a heading in another doc, including [[Note#Heading]], opens that doc at the heading.

Available on all plans.

Get started with Canvas

Canvas is available today for every specgit account. Sign in with GitHub, connect a repo, and open any .canvas file, or create one from New document → Board. The Free plan includes one repository and 5 publishes a month with unlimited collaborators. Publishing a board together counts one publish for each file in the set.

Ask Agent on boards and Repo context are included with Pro at $8 per seat per month, with pay-as-you-go agent usage and a one-time $10 credit. They're also included with Pro Plus at $16 per seat per month, which comes with $10 of agent usage per seat each month. Annual billing saves 20%. See pricing

Drawing, shapes, and embedded web pages aren't supported on boards yet. On phones you can add, move, and edit cards and leave comments. Resizing, drawing arrows, and grouping are desktop only.

If your team has a board that only one person can edit today, open it in specgit and tell us what's missing. We'll keep improving Canvas as we learn how teams use it.

More from the blog