Plan the work in cycles, keep the code in your own repositories, design and document the product, and hire the people who build it, in one account.

Save a repository's issues as JSON with GitHub CLI and upload the file: titles, descriptions, labels, the first assignee and whether each was open or closed come in, with the GitHub number kept as the Original ID. From another tracker, upload a CSV file and choose which column fills each field. One import creates up to 200 issues, and every row is checked before any is created.

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

Create a repository and push your project to it over HTTPS, with its commits, branches and tags, using an access token as the password. Anyone who can read the repository can clone it with ordinary Git, and a credential helper such as Keychain can keep the token. A token follows its account, so someone who leaves the team can no longer push.

Invite them to the team as a guest with Git Repositories: they use the team's repositories under the team's Member access and see none of its other areas. A guest can also be let into one Team chat channel.

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

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

A team admin turns on cycle planning, and members create cycles of one week, two weeks or custom dates that do not overlap. A cycle's page counts its issues as Completed, In progress and Remaining, and unfinished issues can be moved to the next cycle together. Whatever your statuses are called, their category decides what counts as completed.

Present makes a link to a Flow as it is at that moment, which anyone can open in a browser without signing in, with Back, Restart and Full screen. It shows only the Frames the Flow reaches, not other Pages, comments or history, so present again after further changes.

Export DESIGN_SYSTEM.md at Compact, Standard or Complete detail, with critical rules first and each component's source file, and paste the section the Export page gives into AGENTS.md or CLAUDE.md. A system that is unlisted or public, with its For developers section shared, serves its current Markdown at its address followed by /assistant.md.

Start one of Y Combinator's post-money SAFEs from the Library, with a valuation cap, a discount or MFN, answer its questions, and choose Send for signature. The company's officer and the investor each sign through a link of their own without a Magpie account, and the next investor's SAFE starts with your company's answers. Have a lawyer review it first.

The Library has mutual NDAs from Common Paper, Bonterms and oneNDA, and Papertrail's short NDA. Fill in the parties and the purpose, and E-Signatures sends each party a link to sign. When the last one signs, everyone gets the signed PDF and a certificate of completion.

A job page that takes applications carries the job information search engines read for job search, such as Google for Jobs: the title, description, employment type, location, remote work, salary and closing date. Share job starts a Social Media post with the job's title and address.

Schedule interview lists the start times when every interviewer is free and adds the interview to the team's Calendar. Magpie Video Chat creates a call with places for 6 people, which the candidate joins from the link in their invitation without an account. Or enter a phone number or another meeting link.

A files website can take its files from a repository in the team's Git Repositories, and each push to its branch publishes it again. A repository with a content/ folder is built into pages from Markdown and Twig templates, with a sitemap and a feed, and a team admin can show the site at your domain.

Share the document with them by handle with Can review, and they will join as a guest who can open that document and nothing else. They comment on selected text and suggest wording that changes the document only when an editor accepts it. A link anyone can read without signing in can be turned on too.

Meetings gives each person a meeting page with Meeting Types, offering only the times their schedule and a connected Google Calendar leave free, in the visitor's time zone. Each meeting can get a Zoom call or a Google Meet link, and 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, and can scroll a script from a Document on a teleprompter. Cut parts out, then share a page anyone with the link can watch, with a transcript and link buttons. Analytics counts the views and how far people watched.

Mail adds mailboxes and aliases at your domain, such as support@ delivering to the people who answer it, connected with records at your current DNS provider or by moving the domain's DNS to Magpie. A team mailbox opens for every member, with the same folders and read status for all of them.

Clone any repository with its whole history. Issues export as CSV or JSON with comments and activity, Documents as DOCX, Markdown or HTML, Design files as SVG, PNG or PDF, and a Design System as design-system.json with tokens.json and tokens.css.