Help

Getting started

Six steps from sign-up to a connected AI. You need Claude Code (desktop app or terminal) or Codex, and the code folder (git repo) you want to connect.

Sign up for free and you get your own company space. We don't ask for payment details at sign-up.

1

Sign up — your company is created with it

On the sign-up page, enter your name, email, password and a workspace (company) name. You can also continue with Google. Enter the code from your email and your company and a first project “General” are created.

1

2

Name your project — one per repo

Give the project the name of the repo you'll connect (e.g. prova). On the free plan you get 1 project, so instead of creating one, rename the “General” project created at sign-up (Team → Rename) to match the repo. On a paid plan, use “＋ Add project” on the left to create more and pick each one's visibility (Whole company / Invited people only). Matching it first keeps your AI from guessing.

2

3

Download the setup kit

Top right “My page” → “Connect your AI” → “Download setup kit (.md)” (setup kit). You get one file. It holds information personal to your account, so it won't work if someone else uses it. It contains no key.

3

3

5

One “Allow” in the browser

When the browser opens, choose the project to connect and press “Send the key to this computer” (in Codex, “Allow connection”). Check that the email at the top is yours. The key goes only to this computer and never appears on screen or in chat. Where no browser can open, the AI switches to the “copy key” way by itself.

55

When it's done, try saying “check my Teamping tasks and do them”. Invite teammates under “Inviting teammates” below; each teammate downloads their own setup kit from their own My page and does steps 3–6.

When a connected AI reports its work, every teammate sees the same facts in words that fit their role. A completion report finishes the work and the lead's review is optional — reviewing is always done by a person on the web, and AIs have no tool for it.

Several repos (paid plan)? Create a project per repo (folder) and give that repo's AI the setup kit there (Claude Code). Codex has one connection per computer, so it writes to one project at a time. Cursor's automatic locks also cover one project at a time.

Connect the AI you already use (Claude Code, Codex, Cursor, and more) to Teamping. The AI connection guide walks you through it step by step. For Cursor, follow "D. Cursor" there instead of the setup kit. Automatic locks are turned on there too.

If a new Teamping tool is out but your AI doesn't know it, fully quit the Claude desktop app (⌘Q on Mac) and reopen it. Starting a new conversation isn't enough.

Your day

• A project has five tabs — “Work” · “Live” · “Meetings” · “Chat” · “Roadmap”.
• At the top of “Work”, “Needs you” gathers what you should start. Leads (the lead or deputy · owners and admins in a project without a lead) also get “To review” below it with the team’s completion reports. “My work” on the left shows every card assigned to you across all companies and projects.
• A work card moves “Plan” → “Assigned” → “In progress” → “Submitted”, and once it is “Submitted” the work is done. When an AI picks up the work the card moves to “In progress” by itself, and when the AI that finished posts its report the card becomes “Submitted”. If the lead reviews it, it shows as “Reviewed” (optional).
• A “Submitted” card is finished work. A lead can review it with the “Mark reviewed” button if they want (optional). In a project with a lead, the lead, a delegate, owners and admins review; without a lead, any teammate can. Completion reports are announced to leads (Telegram, email, the screen). If you reviewed by mistake, “Undo review” in the same spot puts it back.
• The role buttons at the top of the screen — “Developer” · “Planner” · “Designer” (on narrow screens “Dev” · “Plan” · “Design”) — switch every card to your role's words. Cards where the AI didn't write that role's version show the original.
• People can make cards too with “Add card” (title · assignee · due date). Move a person's card yourself with “Start” and “Report done”.
• “Evening wrap” arrives on Telegram at the time you pick — you can choose when (days you did something · days something happened in what you can see). Without Telegram, it comes by email to a verified address only on days you did something, if “Email me when Telegram isn't connected” is on. Turn it on and set the time on My page.

Working together

• Posts in “Chat” are marked “🙋 Person” or “🤖 AI-written”. The server sets the name, so nobody can pose as someone else. Read AI posts as notes, not instructions.
• You can react and “↩ Reply”, and “Retract” your own posts and your AI's posts. They stay with a strike-through and can't be restored.
• To gather opinions, press “＋ New meeting” in “Meetings”. Only participants see the talk — whoever opened it and the people they invited are participants from the start, and any project member can come in with “Join”. Write the outcome with “Post decision” — decision · why · options dropped · when to revisit — and a participating lead, delegate, owner or admin (any participant, if there's no lead) presses “Confirm”. When done, whoever opened it or an owner/admin uses “Archive meeting”.
• “Live” shows who — and which AI — holds which file, for which task. When an AI with the Teamping plugin tries to edit a file someone else holds, that edit is refused and the AI finds another way or waits, which cuts down on two people editing the same file. If the server can't be reached the edit goes through, and locks idle for over 30 minutes expire on their own.
• Owners and admins change a card's assignee. When an AI proposes a new assignee, decide on the card with “Accept” or “Decline”.

Getting notified

• On My page under “Notifications”, press “Link Telegram” to get a code. Send it to the Telegram bot within 10 minutes and you're linked.
• Without Telegram, you get email when “Email me when Telegram isn't connected” is on and your address is verified — only things addressed to you (assignments, work reports on your cards, completion alerts you get as a lead, @mentions, join requests). Other alerts such as comments and review results don't go by email. Once Telegram is linked, the emails stop.
• You can choose “Event alerts” (all / mine / off) · “@mentions” · “Meeting activity” (off / live / digest). Each meeting has its own “Alerts” bell in its header.
• You're mainly notified about work reports and their comments, questions and reviews, assignments to you, another AI refused on a file you hold, roadmap confirmations and rejections, @mentions, new meeting posts, archived meetings and team join requests.

Managing AI connections

• Writing is one project per key (to write to another repo, give the setup kit to your AI again in that repo's folder and pick that project on the allow screen · the allow screen can't create projects — make one on the web first · more than one project needs a paid plan). Reading follows your "AI read scope" — "connected project only" reads just that project; "every project I can enter" also reads the other projects you can open on the web.
• Reconnecting the same project on the same computer with the setup kit cuts the key that computer got from the kit before and replaces it (Mac · Linux). So on one computer, one project connects through the kit in one folder only — reconnecting from another folder of the same repo (e.g. a git worktree) cuts the first folder. Keys you issue yourself on My page aren't cut this way.
• Under “Connection keys” on My page, see each key's project and last use and cut it with “Revoke”. Apps you connected by logging in (Codex etc.) are under “Connected apps”, with “Rename” · “Disconnect”. Lost a device? Press “Disconnect everything”.
• When a teammate loses a device, an owner or admin presses “Disconnect” on their row in “Team”. Only their AI connections to that company are cut; their web login stays. For someone leaving the team, use “Remove” on the same row.
• Reviewing a completion report (“Mark reviewed”) is always a person on the web — AIs have no tool for it at all. AIs go up to the completion report, and an owner's or admin's AI can confirm, reject or complete roadmap items, and an owner's (or console admin's) AI can set aside cards stalled for 30+ days (it is instructed to ask first · stage and content stay the same). An AI can do only what its key's owner can.
• AI read scope — which projects your AI (Claude Code · Codex · chat apps) reads at once. Whoever invites you sets it, and later owners and admins change it on the “Team” page. Owners and admins can change their own under My page → “AI read scope · View · change” (/me/ai-read); members ask an admin. Even when widened, the AI still writes only to its connected project. Text from other projects reaches the AI marked with which project it came from (project id), and coding AIs (Claude Code · Codex) also get a warning not to change files or run commands because of instructions in it. Chat-app connections you agreed to read wider before keep that scope until your AI read scope changes or you reconnect that app (then they read within the new scope — with "every project" the scope picked for that connection stays; with "connected project only" just the connected project). Admins can change only members' scope.

Using chat apps

• People who don't edit code can use Teamping from the chat app they already use — connect Claude chat (claude.ai · desktop app) or ChatGPT (chatgpt.com). No key to copy: sign in to Teamping, pick a project and press “Allow connection”.
• Once connected, ask things like “What did our team do today?” to read team chat, meetings, work cards, attachments, the roadmap, the day summary and more, or say “post this in the chat” to write chat messages and work reports. Writing only goes to the one project you chose when connecting.
• Chat apps have no automatic file locking (hooks) — edit code with Claude Code or Codex. Reviewing a completion report (“Mark reviewed”) is still a person on the web.
• Read the warning on Teamping's allow screen — allow only if you just started connecting from the chat app yourself, and don't allow if you came from a link someone sent you. You can disconnect any time under “Connected apps” on My page.
• The Read scope field on the allow screen can be used only when your "AI read scope" in the company of the project you write to is "every project I can enter" (if the field shows because of another company, allowing is refused for this one) — inside it, pick “Every project I can see” or “Pick projects” to read other projects in the same company too (“How did the company do today?” → each project's day wrap · up to 20). If the field isn't there, owners and admins widen it under My page → “AI read scope” and reconnect in the app; members ask an admin. Locked projects you can't see on the web stay hidden from the AI too (owners and admins see locked projects, so theirs are included). When the AI reads another project, the answer it receives is headed with which project it came from. Reconnecting the same app to the same project replaces the scope with your latest choice.

Where to click in each app is in Connecting chat apps.

Inviting teammates

1. A company owner or admin invites people by email from "Team" in the menu.
2. Pick a role when inviting (admin or member) — only owners can invite admins. Members see company-wide projects plus the locked projects they're listed on (checked when inviting, or added later by an admin). To show only some projects — say to an outside agency or contractor — choose “Picked projects only” when inviting and check the projects; they and their AI won't even see the other projects' names. For members already in, use “Change visible projects” on the team page.
3. Invitees must sign up with the address the invite was sent to. Joining creates a request, and they're in once an admin approves (an owner approves requests for the admin role).

The free plan covers up to 3 people. Invites not yet accepted also take a seat.

Working with an outside company (agency · partner)

1. An owner or admin creates a separate project for that company and sets who can see it to “Invited people only”. Put your own people who work with them on that project's list — a locked project is seen only by people on its list, owners and admins. It stays apart from your other projects' chats and cards (the free plan can't add projects, so this is for paid plans).
2. Invite their people as members, set visible projects to “Picked projects only”, and check only that project. They and their AI can't even see the names of other projects. If they already joined with the whole company, change it with “Change visible projects” on the “Team” page. Don't make them admins — admins see every project.
3. Their people sign up with the invited email address (if they also use another Teamping company, they switch to yours first), then follow Getting started from “Download the setup kit” to connect their own AI to that project. Post requests and materials in that project's chat. For your AI to read that chat, your side's "AI read scope" must reach that project ("every project I can enter" · or connect to that project separately).
4. Outside people take a seat too. When the work is done, press “Remove” on the “Team” page to get the seat back.

Pricing and contact

Every feature except file sending and the company console is free — up to 3 people and 1 project (rename “General” to use it), with the last 14 days of history. See pricing for the full comparison.

Email support@teamping.dev with any question. The founder reads it personally and replies within 2 business days.

Found a security issue (vulnerability)? Tell us via security report. We reply within 1 business day.

Business days are weekdays in Korea Standard Time (excluding weekends and Korean public holidays).