Idea2Paper

Offload the labor. Steer the science.

Title

Score

—/10

Project Info

Cost

No cost data yet.

Idea

Live Log

Waiting for logs...

Admin Console

Submissions —

Maintenance banner

Shown to all users at the top of the dashboard. Leave empty and Publish to clear.

All Projects 0

User	Title	Idea	Venue	Status	Score	Max Iter	Created	Actions

Pending requests 0

Registered users 0

User	Affiliation	Projects	Logins	Last seen

Decided requests

Feedback

Previous feedback

Loading…

Continue Project

Experiments Backend

🔧 Slurm

Orchestrator Backend

🖥️ Local ☁️ Cloud 🔧 Slurm

Instructions / Comments (optional)

User Settings & API Keys

💡 Bring Your Own Key: Keys are stored encrypted and used only for your own research projects. Best practice: create a dedicated key with a spending cap and revoke it when you're done.

Add a key for any provider you want to use — at least one. Keys are stored encrypted, per user.

OpenRouter ★ Recommended One key unlocks Anthropic · OpenAI · Gemini models

Unlocks the OpenRouter model row (Claude / GPT / Gemini / Kimi / DeepSeek and more) in the new-project model picker.

Anthropic Claude · Opus 4.8 / Sonnet 4.6 / Haiku 4.5

OpenAI GPT · 5.5 Pro / 5.5 / Codex / 5.4 mini

Gemini Gemini · 3.5 Flash / 2.5 Pro / 2.5 Flash

If left empty, Deep Research + figure generation are skipped.

Other provider ⚠ Unverified — pick one and paste its key

Optionally auto-push every project to a private GitHub repo. Leave blank to skip.

GitHub Personal Access Token Auto-push each project to a private repo

How to set up:
1. Create a classic PAT with the repo scope, then paste it in the PAT box above. (Fine-grained PATs can't create repos — use a classic one.)
2. Organization (optional): to keep all project repos under one org, create the org on GitHub first — Idea2Paper can't create orgs for you — then put its name in the Org box. Leave blank to use your personal account.
Each project then auto-creates a private repo ark-<project> (in the org if set, else <you>/ark-…) and pushes its commits there. The PAT is stored encrypted and used only by the orchestrator — never exposed to the research agents.

Configure your Google Cloud project for remote cloud runs.

GCP Project ID

Grant compute access

Runs launch into your GCP project via a shared launcher identity — no service-account key to upload. You do a one-time setup on your Google Cloud project, then click Verify. Full walkthrough:

1. Have a GCP project with billing enabled.

Create a project (or pick an existing one) and link a billing account to it.
Copy its Project ID (not the display name) into the GCP Project ID field above.

2. This is the principal (service account) you grant access to:

(loading launcher identity…)

3. Is this project under a Google Cloud organization?

Personal account (no organization) Part of an organization

4. Run this setup in Cloud Shell (no install — opens in your browser) or a local gcloud. It enables the required APIs and grants the launcher its roles:

Enter your GCP Project ID above to generate the setup script.

…or grant via the Cloud Console →

5. Come back here and confirm we can reach your project:

Prefer the Cloud Console? / What each role is for

APIs: open APIs & Services → Library and enable Compute Engine, Cloud Resource Manager, IAM, Service Usage, and Cloud Storage.
Roles: open IAM & Admin → IAM → Grant access, paste the principal from step 2 as the new member, and add each role below.

Configure your AWS account for remote cloud runs.

AWS Account ID

Region

Grant compute access

Runs launch into your AWS account via a shared launcher identity that assumes a role you create — no access key to upload. You do a one-time setup on your AWS account, then click Verify. Full walkthrough:

1. Have an AWS account.

Find your 12-digit Account ID (top-right account menu in the AWS Console) and paste it, plus your preferred Region, above.

2. This is the identity you grant access to (it will assume the role you create):

(loading launcher identity…)

3. Run this setup in CloudShell (no install — opens in your browser) or a local aws CLI. It creates the ark-launcher role that trusts the launcher and attaches the compute policies ARK needs:

Enter your AWS Account ID above to generate the setup script.

…or create the role via the IAM Console →

4. Come back here and confirm we can reach your account:

Prefer the IAM Console? / What each policy is for

Open IAM → Roles → Create role, choose Custom trust policy, and paste the trust JSON from the script (it names the launcher identity from step 2).
Attach the policies below, and name the role exactly ark-launcher.

Get progress updates and answer the project's questions from Telegram. This is optional — leave it blank, or clear it and save to stop all Telegram notifications.

Telegram Notifications (optional)

How to set up: 1. Message @BotFather, send /newbot to get a Bot Token · 2. Message @userinfobot to get your Chat ID

Bot Token

Chat ID

To turn Telegram off, clear both fields and save. New projects will no longer send messages.