Magpie tracks your product's work in cycles and hosts its code. It holds the designs and specs, and handles your hiring.

You upload a repository's issues, saved as JSON with GitHub CLI. Titles, descriptions, labels, the first assignee and open or closed state come in. Each GitHub number is kept as the Original ID. From another tracker, you upload a CSV file and choose the column for each field. One import creates up to 200 issues, and checks every row before creating any.

Yes. You link a GitHub repository to a project. Each of the project's issues then has a Development section. It suggests a branch name made from the issue's identifier and title. It lists the pull requests and commits you add to the issue by their GitHub address.

Yes. You create a repository and push your project over HTTPS, with its commits, branches and tags. An access token is the password. Anyone who can read the repository can clone it with ordinary Git. A token follows its account, so someone who leaves the team can no longer push.

Yes. You invite them to the team as a guest with Git Repositories. They use the team's repositories with the access your members have. They see none of the team's other areas. You can also let them into one Team chat channel.

Yes, through a public form with your own instructions and an optional project for its reports. Customers give a title, what happened and an optional contact email. Only members who can edit issues see that email. Each report waits in Triage. A connection that sends many reports has to wait before it can send more.

Yes. The REST API lists, reads, creates and updates issues, and lists and adds their comments. It uses an API key, which acts as the person who made it. You can add webhooks that send signed issue, comment and project events to an HTTPS address. Each event gets up to 5 attempts, all with the same event ID.

Yes, once you turn on cycle planning. A cycle is one week, two weeks or custom dates, and cycles do not overlap. A cycle's page counts its issues as Completed, In progress and Remaining. You can carry unfinished issues over to the next cycle together. Whatever your statuses are called, their category decides what counts as completed.

Yes. Presenting a prototype makes a link to it as it is at that moment. Anyone can open the link in a browser without signing in. It shows only the screens the prototype reaches, not the file's comments or history. The link keeps showing the prototype as it was, so you present it again after changes.

You export DESIGN_SYSTEM.md at Compact, Standard or Complete detail. It puts critical rules first and names each component's source file. You paste the section the Export page gives into AGENTS.md or CLAUDE.md. An unlisted or public system can also share its For developers section. Its current Markdown is then served at its address followed by /assistant.md.

You start one of Y Combinator's post-money SAFEs, with a valuation cap, a discount or MFN. You answer its questions and send it for signature. The company's officer and the investor each sign through their own link, without signing up first. The next investor's SAFE starts with your company's answers. A lawyer should review it first.

Yes. Agreements has mutual NDAs from Common Paper, Bonterms and oneNDA, and Papertrail's short NDA. You fill in the parties and the purpose. E-Signatures will send each party a link to sign. When the last one signs, everyone will get the signed PDF and a certificate of completion.

A job page that takes applications includes the details search engines read for job search. Google for Jobs is one of them. The details are the title, description, employment type, location, remote work, salary and closing date. Sharing a job starts a Social Media post with its title and address.

Magpie Video Chat creates a call with places for 6 people. The candidate joins from the link in their invitation, without signing up first. Magpie lists the start times when every interviewer is free. The interview will be added to the team's Calendar. You can enter a phone number or another meeting link instead.

Yes. A files website can take its files from one of the team's repositories. Each push to its branch will publish it again. A repository with a content/ folder is built into pages from Markdown and Twig templates. The site gets a sitemap and a feed, and you can put it at your domain.

You share the document with them by handle, with Can review. They will join as a guest who can open that document and nothing else. They comment on selected text and suggest new wording. The text changes only when an editor accepts it. You can also turn on a link anyone can read without signing in.

Meetings gives each person a meeting page with Meeting types. It offers only the times their schedule and a connected Google Calendar leave free. Visitors see them in their own time zone. Each meeting can get a Zoom call or a Google Meet link. Slack can post new, moved and cancelled meetings to a channel.

Screen Recorder records a screen, a window or a tab, with your camera in a bubble. It can scroll a script from a document on a teleprompter. You can cut parts out, then share a page anyone with the link can watch. The page has a transcript and link buttons. Analytics counts the views and how far people watched.

Yes. Mail adds mailboxes and aliases at your domain. An alias such as support@ can deliver to the people who answer it. You add records at your current DNS provider, or move the domain's DNS to Magpie. A team mailbox opens for every member, with the same folders and read status.

Yes. You can clone any repository with its whole history. Your issues export as CSV or JSON, with comments and activity. Documents export as DOCX, Markdown or HTML, and Design files as SVG, PNG or PDF. A Design System exports as design-system.json, with tokens.json and tokens.css.