TabTin is live · free plan; paid plans on request · last verified 4 Nov 2026 · viability healthy

TabTin

TabTin

TabTin is an open-source team agent harness where sub-agents and people share one task surface for code, docs and spreadsheets.

75/100Safe BetFree plan · paid plans on requestFreemium

The team layer is why to look: shared task surfaces, checkpoint-before-write, approval gates and per-member token quotas in one admin panel, a combination still rare next to solo coding agents. Before committing, weigh the Chinese-primary UI and docs and a vendor-published audit that names TabTin the only project passing all checks, which is marketing until you rerun it yourself.

Verdict generated

Verified 9d ago · liveness 75/100 · cite: rightaichoice.com/tools/tabtin

Best for
  • Small product teams already running on group chat who want agents inside that workflow
  • Engineering leads who need checkpoint and rollback around agent writes before production changes
  • Teams mixing research, spreadsheets, docs and code on one shared task surface
  • Chinese-language teams, since the primary UI and documentation ship in Chinese
Not ideal for
  • English-first teams that need fast onboarding without a Chinese-primary UI and docs
  • Solo users wanting a lightweight personal AI assistant
  • Teams needing a wide library of prebuilt third-party integrations beyond GitHub
Visit Website

IntermediateFree download to first useful task: under an hour for a team that just wants to run agents on the four surfaces and review checkpoints. Self-hosting, branding and organisations are a different scale — the developer-support library splits into 21 official Prompts across 5 modules (environment, Electron desktop, Django backend, iOS and Android clients, industry-product rebuild and delivery), so aDesktop · MobileNo public APIVerified 9d ago
Pricing
Free plan · paid plans on request
FreemiumFree tier2 plans3 hidden costs
Learning curve
Intermediate
Free download to first useful task: under an hour for a team that just wants to run agents on the four surfaces and review checkpoints. Self-hosting, branding and organisations are a different scale — the developer-support library splits into 21 official Prompts across 5 modules (environment, Electron desktop, Django backend, iOS and Android clients, industry-product rebuild and delivery), so a
Runs on
DesktopMobile
No public API · 1 integrations
Who it's for
Product lead at a small product teamResearch or analyst teamEngineering team running a release
Live sentiment
Is TabTin actually worth it?

We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.

  • Honest verdict, not marketing
  • Real pros & cons from real users
  • Attributed quotes with receipts
Run a free scan

3 free scans · no card needed

Skip it if

Skip TabTin if you want a single autonomous coding agent with production write access and no approval gate — the human confirmation step before publish is deliberate and slows every shipping cycle.

Skip-it-if note generated
The 30-second take
Biggest gripe

Team usage is metered in credits — the published workspace example shows 12,480 of 20,000 credits used, so heavy agent runs burn a finite shared pool rather than scaling flatly.

Price reality

TabTin is a free download of an open-source harness; team usage is metered in credits, with a published workspace example showing 12,480 of 20,000 credits consumed. That places the entry point below per-seat autonomous coding agents like Cursor or Devin, but the real cost curve is self-hosting and the developer time itemised across the 21 official developer Prompts. Cheaper than Devin if you have engineering capacity; more expensive than a plain Copilot seat if you do not.

Generated

In short

TabTin — TabTin is an open-source team agent harness where sub-agents and people share one task surface for code, docs and spreadsheets. Best for Small product teams already running on group chat who want agents inside that workflow, Engineering leads who need checkpoint and rollback around agent writes before production changes, Teams mixing research, spreadsheets, docs and code on one shared task surface. Free to start; it also has paid plans whose price we could not confirm — see the pricing table.

Claim this listing

What is TabTin?

TabTin — TabTin is an open-source team agent harness where sub-agents and people share one task surface for code, docs and spreadsheets. Best for Small product teams already running on group chat who want agents inside that workflow, Engineering leads who need checkpoint and rollback around agent writes before production changes, Teams mixing research, spreadsheets, docs and code on one shared task surface. Free to start; it also has paid plans whose price we could not confirm — see the pricing table.

FreemiumIntermediateNo APIDesktop · Mobile

TabTin runs AI agents next to people on a single shared work surface rather than as a solo chatbot off to the side. You choose a persona (research, efficiency, data, knowledge, development) or build your own, and it carries configured rules, memory and skills into every task. Four apps handle the hands-on work: a spreadsheet that turns scattered notes into filterable records, a document app for drafting and annotation, a dev surface that reads repositories and edits code with changed lines exposed, and a browser surface that opens live pages and writes extracted results back into the task. The collaboration layer is the core. Group chat is the hub, and agents read messages, spot issues, create tasks and @ the owner, then sync status back to the thread. A shared task surface lets a teammate open a shared agent conversation with full context and continue it. A documented July 2026 run scraped 42 AI products into a shared table and produced a linked report with 34 scored entries and 3,549 reviews. Governance sets it apart from most agent tooling. Writes and publish actions sit behind a human approval gate, a checkpoint is saved before each write so a run can roll back, repository permissions are enforced per member, and admins set token quotas per member with a global fallback (the page shows a 2,000 monthly / 400 daily default). It ships Chinese-first (English, Japanese, French, German and Korean available), offers public-cloud and private deployment, and competes with agent-collaboration platforms rather than lightweight personal assistants. Treat the vendor's self-published August 2026 audit as marketing until you reproduce it.

Key features

  • Main Agent splits a task into research, build and verification sub-agents sharing one context
  • Checkpoint saved before every write so a run can be rolled back
  • Human approval gate before publish or write actions
  • Per-member repository permissions enforced on connectors
  • Per-member AI token quotas with monthly and daily caps and admin exemption
  • Global fallback quota with department and role inheritance rules
  • Browser surface opens live pages and writes extracted results back into the task
  • Spreadsheet surface turns scattered information into filterable, countable records
  • Document surface for drafting, rewriting and annotation with saved versions
  • Dev surface reads repositories, edits code and runs tests with changed lines shown
  • Group chat where agents spot issues from messages, create tasks and @ the owner
  • Auto status sync from task progress back into the group chat
  • Share an Agent conversation with a teammate who opens the full context and continues
  • Multi-device sync: start on desktop, confirm approvals on mobile
  • Private deployment inside your own environment with managed backups and service monitoring

Behind the verdict

Pick TabTin when the problem is coordination, not generation. If your team already lives in group chat and you want agents that read the thread, file tasks, @ the owner and report back, the shared task surface is the right shape for that work. We'd especially reach for it when agent writes touch code or published docs, since the checkpoint-before-write and approval gate mean a bad run rolls back instead of shipping. It also earns a look from engineering leads who need per-member token quotas with department and role inheritance. Set a global fallback, override individuals, and you stop one heavy user from burning the team's budget. Private deployment inside your own network with managed backups covers the orgs that can't send data to a vendor cloud. Where it bites: the interface and documentation are Chinese-first, so an English-first team pays an onboarding tax that no feature list shows. Third-party integrations documented here run to GitHub, so don't expect a marketplace of connectors. And the August 2026 audit is self-published, not independent, so first-hand evaluation is on you. Pass it over for solo, lightweight personal-assistant needs, and skip it if no one will staff the human approval step, because the safety model depends on a person actually clicking. Our closest comparison is agent-collaboration platforms. Against solo coding agents, TabTin trades polish for structure and audit trails, which is the trade a team should usually make.

Limitations

  • The scraped evidence is largely Chinese-language marketing copy (the standalone changelog/docs/about pages returned only the homepage), so per-model configuration options, rate limits and context-window size cannot be verified.
  • Write and publish actions are still gated by explicit human approval, and repository write permissions remain gated by human approval — so TabTin is slower than an unsupervised autonomous agent by design.
  • The code-level audit naming TabTin the only passing project is self-published, and the 42-product competitive analysis was likewise a documented TabTin run rather than an independent benchmark.

as of 2026-10-10

Researching TabTin? Get your full AI stack in 60 seconds.

Free, no signup — tell us your goal and get tools matched to your budget & existing stack.

Is TabTin still active?

TabTin is live · free plan; paid plans on request · last verified 4 Nov 2026 · viability healthy.

Viability score

75/100
Safe Bet

How well maintained and how widely used is TabTin? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this

Recent activity
90
Traction
100
Site health
95
User sentiment
57
What the vendor publishes
40

Last calculated: November 2026

How we score →

What's new in TabTin

Checked 5 days ago

Across the latest 2 updates: 2 news mentions.

What do users say about TabTin?

What people actually say about TabTin — is it worth it?

We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.

Researched

Discussed by users across 2 sources (YouTube, GitHub) · researched Sep 30, 2026.

57% positive43% critical

Weighted by the 14 posts each of 2 sources contributed.

Recurring strengths
  • +Main Agent splits tasks into research, build and verification sub-agents sharing one context.
  • +Checkpoints saved before every write, with rollback of execution state instead of a rebuild.
  • +Human approval gate before publish or write actions is the core reason agents stay usable in delivery.
  • +Repository permissions enforced per team member and per connector, not just globally.
  • +Four concrete surfaces: code, document, spreadsheet and live browser research in one app.
Recurring frustrations
  • −Coding output quality is contested; an open issue asks for Claude Code / Codex as substitutes.
  • −Only GitHub is a first-party integration; no GitLab, Bitbucket, Slack or Jira connectors.
  • −Primary UI and documentation are Chinese-first, with a thinner English locale.
  • −No supported remote HTTPS/WSS deployment for the Community Server as of 2026-08-24.
  • −Auto-memory model catalog is stuck on legacy BYOK eligibility, blocking Codex and custom providers.
Patterns worth knowing
Users want to swap in mainstream coding harnesses (Claude Code, Codex) rather than rely on the built-in coding agent.
Seen on GitHub
The auto-memory and model-catalog plumbing is out of sync with the newer Codex / custom-provider stacks users have migrated to.
Seen on GitHub
Teams want a supported way to run the Community Server remotely over HTTPS/WSS instead of tying persistence to the Desktop process.
Seen on GitHub
Learning curve
intermediateProductive in ~A few hours
Hidden costs people mention
  • • Model API usage (Codex, Claude, OpenAI) is billed by the provider — TabTin itself doesn't include inference.
  • • Self-hosting the Community Server means you supply the host, TLS cert, and ops time to keep it online.

How we verified this

Every listed fact about TabTin — pricing, features, links, status — is re-read from the vendor's own pages by our verification pipeline and each change is logged with a date; the last pass ran on 4 Nov 2026. Analysis is drafted with AI models and checked against our editorial standards before publishing; see how we verify.

Verification history

We have re-verified TabTin 10 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.

  1. — changed pricing page, limitations
  2. — changed who it suits, our verdict, description, summary, who should skip it, features
  3. — changed pricing page, limitations, our verdict, pricing tiers, who should skip it, description, who it suits, summary, features
  4. — changed description, our verdict, who it suits, summary, features, pricing tiers
  5. — changed who should skip it, summary, who it suits, pricing tiers, features, description, our verdict
  6. — changed limitations, pricing page, platforms

Showing the 6 most recent of 10 verification passes.

Free to cite with attribution — this page re-verifies continuously.

Claim this listing

How much does TabTin cost in 2026?

TabTin: Free to start; it also has paid plans whose price we could not confirm — see the pricing table. Pricing last verified 4 Nov 2026.

12-month cost

Project the real annual outlay, including the implied monthly cost when only an annual tier is published.

Annual total
Free
Over 12 months
Effective monthly
—
—

Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.

Hidden costs & gotchas

What the public pricing page doesn't put in bold. Captured from pricing-page footnotes, contract terms, and recurring complaints.

  • Team usage is metered in credits — the published workspace example shows 12,480 of 20,000 credits used, so heavy agent runs burn a finite shared pool rather than scaling flatly.
  • Rebranding, private deployment, database and object-storage configuration, and production monitoring are all DIY work itemised in the 21 official developer Prompts, not delivered services.
  • Running the full stack yourself means paying for and maintaining Django API, collaboration service and Electron/mobile build infrastructure on your own servers.

Where the pricing makes sense

The company stage and team size where TabTin's pricing actually pencils out — and where peers do it cheaper.

TabTin is a free download of an open-source harness; team usage is metered in credits, with a published workspace example showing 12,480 of 20,000 credits consumed. That places the entry point below per-seat autonomous coding agents like Cursor or Devin, but the real cost curve is self-hosting and the developer time itemised across the 21 official developer Prompts. Cheaper than Devin if you have engineering capacity; more expensive than a plain Copilot seat if you do not.

Hidden-cost and price-fit notes generated

Has TabTin's pricing changed?

No plan price for TabTin has moved since we began logging in Aug 2026; the pricing page is re-read on every verification pass.

Who should pick TabTin?

Pick TabTin if you are Small product teams already running on group chat who want agents inside that workflow, Engineering leads who need checkpoint and rollback around agent writes before production changes, Teams mixing research, spreadsheets, docs and code on one shared task surface, Chinese-language teams, since the primary UI and documentation ship in Chinese.

Look elsewhere if you are English-first teams that need fast onboarding without a Chinese-primary UI and docs, Solo users wanting a lightweight personal AI assistant, Teams needing a wide library of prebuilt third-party integrations beyond GitHub, Anyone treating the vendor's self-published August 2026 audit as independent proof.

Skip it if Skip TabTin if you want a single autonomous coding agent with production write access and no approval gate — the human confirmation step before publish is deliberate and slows every shipping cycle.

Generated

Real-world workflow fit

Concrete scenarios for the personas TabTin actually fits — and what changes day-one when you adopt it.

Product lead at a small product team

You open the code surface against the site repository and ask the Main Agent to make the new homepage reviewable and publishable. It splits into a research sub-agent checking the brand wording and mobile breakpoints across 12 product pages, a build sub-agent updating the first screen and community module, and a verification sub-agent running a 320–1440px regression with attached evidence.

Outcome: Checkpoint #03 is saved before the write, the GitHub repository write waits on a named teammate's approval, and the deliverable is a 7-file preview with 3 checks you can review before publishing.

Research or analyst team

You task the browser surface with scraping a real product list, then have it write the results into a shared multi-dimensional table. In the documented 2026-07-28 run that meant 42 hot AI products from watcha.cn, 34 of them scored, 3,549 reviews counted.

Outcome: You get a filterable table with a linked analysis report where the document cites the same records, and both resources reuse one shared research dataset instead of duplicating it.

Engineering team running a release

Agents watch the release group chat and logs. When the same external-import session refresh shows up three times, the agent writes a repro path, opens task #4820 at P1, @s the owner and tracks it.

Outcome: Status changes sync back into the group chat, the fix is confirmed by regression, and the task closes automatically after the release instead of being tracked by hand.

Workflow scenarios generated

Use cases

Setup time & first value

How long it actually takes to get something useful out of TabTin — broken out by persona, not the marketing-page minute.

Free download to first useful task: under an hour for a team that just wants to run agents on the four surfaces and review checkpoints. Self-hosting, branding and organisations are a different scale — the developer-support library splits into 21 official Prompts across 5 modules (environment, Electron desktop, Django backend, iOS and Android clients, industry-product rebuild and delivery), so a

Switching to or from TabTin

How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.

Migrating in
  • →From Cursor or Devin: move the coding work onto the code surface, then add the team layer — repository permissions, checkpoints before writes and a human approval gate — that a solo autonomous agent does not provide.
  • →From a group chat plus spreadsheet workflow: let the spreadsheet surface absorb the shared table and point the group chat at TabTin agents so task creation and status tracking stop living in someone's head.
  • →From scattered docs and wiki pages: move the draft/rewrite/annotate work to the document surface and reference the shared multi-dimensional table directly instead of pasting numbers.
Migrating out
  • ↗To Cursor or Devin: you keep the code-editing workflow and lose the shared team surface — checkpoints, approval gates, group-chat task tracking and the shared resource model go with it.
  • ↗To a plain chat assistant plus issue tracker: re-create the agent anomaly detection, auto task creation from chat signals and status sync manually.
  • ↗To a hosted SaaS alternative: you trade self-hosting control and the open-source repository for managed operations, and you rerun any branding or industry modelling you did on TabTin.

Integrations

GitHub

Tutorials & Learning

YouTube returned 6 videos for “TabTin”, and we withheld 6: 6 could not be judged, because “TabTin” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about TabTin.

What are the best TabTin alternatives?

The closest alternatives to TabTin we list are omnigent, CowAgent and Microsoft Agent Framework. Ranked by direct product-type match, not category overlap.

Closest alternatives to TabTin
AlternativePricingStarts atLast verified
omnigentFreeFree—
CowAgentFreeFree—
Microsoft Agent FrameworkPaidPricing not published—

Alternatives to TabTin

View all
omnigent

omnigent

Open-source meta-harness that runs Claude Code, Codex and custom AI agents under one policy, sandbox and cost layer

FreeTry
CowAgent

CowAgent

Open-source AI agent harness that plans tasks, runs tools, and keeps long-term memory across sessions.

FreeTry
Microsoft Agent Framework

Microsoft Agent Framework

Microsoft Agent Framework is an open-source SDK for building agentic AI agents and workflows in Python or C#, now with the GA Agent Harness

PaidTry

Tools that pair well with TabTin

Common stack mates teams adopt alongside TabTin, with the specific reason each pairing earns its keep.

TabTin vs its closest rival

TabTin's closest head-to-head is with Cryptohopper — These are not competing products. TabTin is an open-source team harness for software, docs, spreadsheets and browser research with a human approval gate before every write; Cryptohopper is a cloud crypto trading bot that automates orders on major exchanges and costs $24.16/mo after a 3-day trial. No budget owner shortlists both — if you need auditable agent workflows across code and documents, look at TabTin; if you need automated crypto order execution, that is Cryptohopper. Choosing between them is only a question if you happen to run both a product team and a trading account. Verdict generated

Head-to-head comparisons

Tabtin vs Cryptohopper

These are not competing products. TabTin is an open-source team harness for software, docs, spreadsheets and browser research with a human approval gate before every write; Cryptohopper is a cloud crypto trading bot that automates orders on major exchanges and costs $24.16/mo after a 3-day trial. No budget owner shortlists both — if you need auditable agent workflows across code and documents, look at TabTin; if you need automated crypto order execution, that is Cryptohopper. Choosing between them is only a question if you happen to run both a product team and a trading account.

Generated

Tabtin vs Genspark

Pick TabTin if your problem is production-grade work with agents — code in real repos, gated writes, auditability, rollback — and you're willing to self-host an open-source harness with GitHub as your only connector. Pick Genspark if you want the opposite trade: a hosted, broad content-and-research workspace where a non-technical person spins up Super Agents, Sparkpages, slides, sheets, podcasts and video in one account, with Google Workspace, Microsoft 365, Canva and Figma wired in. TabTin gives you control and accountability; Genspark gives you breadth and zero setup. Small Chinese-language teams with engineering in the loop tilt to TabTin; marketers, researchers and no-code builders tilt hard to Genspark.

Generated

Tabtin vs Temporal Ai

These are not competing products, and a buyer should not frame a choice between them. TabTin is a shared surface where humans and AI sub-agents collaborate on code, documents, spreadsheets and browser research, with human approval gates, checkpoint rollback and GitHub connector. Temporal AI is infrastructure for durable execution: workflows and AI agents that survive crashes and retries, with native SDKs in eight languages. If you have a messy team workflow with agents in chat, TabTin fits. If you need an execution engine that keeps long-running state alive across failures, you want Temporal.

Generated

Tabtin vs Air Ai

These two products don't compete, and no real buyer would weigh them head-to-head. TabTin is a downloadable, freemium, open-source harness where a small product team points research/build/verification sub-agents at its own repo, docs and spreadsheets, with a checkpoint before every write and a human approval gate. Air (formerly Govini) is a contact-priced, vendor-deployed defense readiness platform whose customers are military commands and acquisition offices, judged on things like compressing Army Materiel Release from 15 months to 3 and sustaining 90% equipment readiness. Pick TabTin if you have a code/doc/research backlog and want agents inside your group chat; pick Air only if you run a defense sustainment or acquisition mission — and if you did, TabTin would never appear on your shortlist.

Generated

Tabtin vs Spider Cloud

These are not competitors and shouldn't be shortlisted against each other. Pick TabTin if you're a small product team that wants humans and multiple AI sub-agents pushing one auditable task — code, docs, sheets, browser research — through a self-hosted surface with approval gates and rollback. Pick Spider Cloud if your actual problem is that the data you need lives on websites with no API, and you want one key that returns rendered markdown, full-site crawls, or search results into your own agents and RAG pipelines. If you're a team of two, running both is plausible but they solve different layers of the stack.

Generated

Frequently asked questions

For makers of TabTin

Used TabTin? Help shape our editorial sentiment research.