Publish your paper
Publishing includes two steps:
- Create a validated GitHub release in your repository with the APP plugin.
- Submit the release to this registry so researchers can find your paper.
Your GitHub release serves as the primary publication and remains in your own repository. The registry listing provides discoverability and permanent indexing.
You can also instruct your AI coding agent to execute these steps: tell the agent to publish my paper following agenticpapers.app. The agent inspects agent instructions, requests confirmation to install the plugin, and starts the workflow.
These instructions align with the APP protocol specification.
1. Publish
Section titled “1. Publish”-
Install Claude Code or Codex, then install the APP plugin. The plugin runs directly inside the AI agent.
Enter these commands in the Claude Code prompt during an active session (type
claudein your terminal to start):/plugin marketplace add LionSR/AgenticPublicationProtocol/plugin install paper-protocol@paper-protocol/reload-plugins- Open Plugins and select Add → Add marketplace.
- Enter
LionSR/AgenticPublicationProtocolas the source. Leave Git ref and Sparse paths empty. Select Add marketplace. - Locate
paper-protocolin the plugin list and enable it.
Run these commands in your shell:
Terminal window codex plugin marketplace add LionSR/AgenticPublicationProtocolcodex plugin add paper-protocol@paper-protocol -
Open the directory containing your paper, code, and data in the agent, then start publishing.
/publish-paper$publish-paper$publish-paperThe agent guides you through the verification and release workflow:
- Verifies code execution and reproduces manuscript figures.
- Identifies missing environment dependencies or data gaps.
- Collaborates with you to draft clear
AGENTS.mdinstructions. - Packages and validates publication artifacts.
- Creates the tagged GitHub release.
The agent requests confirmation before each critical operation or repository change. You can pause the workflow and resume in later sessions. If you grant GitHub access, the agent creates the release directly; otherwise, it provides the exact Git commands to run.
When the workflow completes, your repository contains a new GitHub release with an APP_PUBLICATION.json manifest. This release is your official publication. For full details on the specification, see the publishing guide.
2. Submit to the registry
Section titled “2. Submit to the registry”Submit your release to the registry: sign in with GitHub and select your release. The registry executes automated verification checks immediately. If all checks pass, your paper appears in the registry right away. If an edge case requires manual adjudication, an editor inspects the submission. Submitting never modifies your repository.