
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We just launched Copilot memory, a new capability that lets Copilot agents learn from past interactions and share knowledge across your development workflow, starting with Copilot coding agent, Copilot code review, and Copilot CLI.
⭄1�7 This Discussion is your space to try it, push it, and tell us what works and what doesn’t. You can read the technical deep dive on the blog, but we’re especially interested in how memory behaves in real repositories and real workflows.
🧠 What Copilot memory is
Copilot memory allows agents to persist useful knowledge about your repository (like conventions, dependencies, or architectural considerations) and reuse it later across tasks and agents.
Today, memory is available in public preview for all paid Copilot plans and is deployed in:
There are two important characteristics:
🔍 Where we’d love your feedback
We’re especially curious how memory shows up (or fails to show up) in everyday work. For example:
If you tried memory on a real pull request or task, we want to hear about it.
Full setup details are available in our Docs and a blog about the engineering work behind this.
📣 How you can help
Please comment below with:
Screenshots, prompts, or concrete examples are especially helpful.
🙏 Thank you
Cross-agent memory is a foundational step toward Copilot feeling less like a stateless tool and more like a teammate that actually learns your codebase over time. Your feedback directly shapes how this evolves as we expand memory to more agents and workflows.
We’re excited to hear how it behaves in the wild, and what you want it to learn next.
Beta Was this translation helpful? Give feedback.
All reactions