opencode-poe-authPoe OAuth authentication plugin for OpenCode
95
近 30 天 +2
164,564
近 7 天 35k
70.8
生态多维模型
1 天前
2026-08-18
快速安装与配置
opencode.json写入当前项目的 opencode.json,只对这个仓库生效。
opencode.json
{
"$schema": "https://opencode.ai/config.json",
"plugin": ["opencode-poe-auth@0.0.4"]
}写入 ~/.config/opencode/opencode.json,对所有项目生效。
~/.config/opencode/opencode.json
{
"$schema": "https://opencode.ai/config.json",
"plugin": ["opencode-poe-auth@0.0.4"]
}若你要在本地改造这个插件,先装到项目里再从本地路径引用。
shell
pnpm add -D opencode-poe-authopencode 启动时会通过内嵌运行时自动加载 npm 依赖并缓存至本地目录,无需手动在全局环境执行安装。
Power your favorite coding agents (Claude Code, Codex, OpenCode, and more) with your Poe subscription—no need to handle multiple providers/accounts. Poe Code routes everything through the Poe API .
Configure an agent once and use its normal CLI or desktop app, or spawn one-off prompts through Poe.
Quickstart
Set it as your default (works with CLIs and desktop apps)
This updates the provider’s config files and continue using your tools normally.
# Start the interactive setup
npx poe-code@latest configure
# Setup a specific agent
npx poe-code@latest configure codex # (or claude, opencode, kimi, goose)
Unconfigure (remove overrides)
npx poe-code@latest unconfigure claude
Authentication
Poe Code uses your Poe API key for authentication. On first run, you'll be prompted to log in via your browser (OAuth). You can also provide your key directly:
# Interactive login (opens browser)
npx poe-code@latest login
# Or pass your API key directly
npx poe-code@latest login --api-key <your-key>
# Or set it as an environment variable
export POE_API_KEY=<your-key>
Credentials are stored locally in ~/.poe-code/. Use poe-code auth status to check your login state.
# Remove all configuration and credentials
npx poe-code@latest logout
Quick links
Utilities
Utilities are especially useful for scripting and CI/CD.
Spawn a one-off prompt
npx poe-code@latest spawn codex "Say hello" --mode read
--mode is the permission mode: yolo | auto | edit | read. It is prompted for in an
interactive terminal, but required in CI: without a TTY, spawn fails unless you pass
--mode (or --yes, which uses the shared auto default). The same choices apply to
gaslight and harness run, and values are case-insensitive (--mode READ works).
Only --mode yolo skips the agent's permission prompts, so keep it out of untrusted CI jobs.
Spawn against a GitHub repository
npx poe-code@latest spawn codex "Fix the failing tests" --cwd github://owner/repo --mode edit
npx poe-code@latest spawn codex "Review the auth module" --cwd github://owner/repo#main:packages/auth --mode read
Spawn a prompt via stdin
echo "Say hello" | npx poe-code@latest spawn codex --mode read
Stdin is piped here, so there is no TTY to prompt on — --mode is required.
Review a GitHub pull request
npx poe-code@latest code-review install
npx poe-code@latest code-review run "https://github.com/owner/repo/pull/123"
npx poe-code@latest code-review commit "https://github.com/owner/repo/pull/123" --dry-run
Test a configured service
npx poe-code@latest test codex
Install agent CLIs
# Claude Code
npx poe-code@latest install claude-code
# Codex
npx poe-code@latest install codex
# OpenCode
npx poe-code@latest install opencode
# Kimi
npx poe-code@latest install kimi
# Goose
npx poe-code@latest install goose
Optional flags
--dry-run– show every mutation without touching disk.--yes– accept defaults for prompts.
Usage & Billing
Check your compute points balance and review usage history.
# Show current balance
poe-code usage
# Show usage history (20 entries, then prompts to load more)
poe-code usage list
# Show a specific number of entries without prompting
poe-code usage list --limit 100
# Filter by model name
poe-code usage list --filter claude
Models
List available Poe API models and filter them by provider, capabilities, modalities, and supported API endpoint.
# List all models
poe-code models
# Show only models that support the Responses API
poe-code models --endpoint /v1/responses
# Show only models that support Chat Completions
poe-code models --endpoint /v1/chat/completions
# Search by provider or model id
poe-code models --search claude
SDK
Use poe-code programmatically in your own code:
import { spawn, getPoeApiKey, getPoeAuthIdentity } from "poe-code";
// Get stored API key
const apiKey = await getPoeApiKey();
// Fetch the authenticated Poe account identity
const identity = await getPoeAuthIdentity();
// Run a prompt through a provider
const result = await spawn("claude-code", {
prompt: "Fix the bug in auth.ts",
cwd: "/path/to/project",
model: "claude-sonnet-4-6"
});
// Spawn against a GitHub repository
const { events, result: ghResult } = spawn("codex", {
prompt: "Review the auth module",
cwd: "github://owner/repo#main:packages/auth"
});
console.log(result.stdout);
For plugin-first agent composition, import the public agent builder from the
poe-code/agent subpath:
import { agent, openaiResponsesPlugin, systemPromptPlugin } from "poe-code/agent";
const run = await agent()
.model("gpt-5.5")
.use(openaiResponsesPlugin())
.use(systemPromptPlugin())
.run("Summarize the current repository", {
cwd: process.cwd()
});
console.log(run.output);
spawn(service, options)
Runs a single prompt through a configured service CLI.
service– Service identifier (claude-code,codex,opencode,kimi,goose)options.prompt– The prompt to sendoptions.cwd– Working directory or workspace locator (optional). Supports local paths andgithub://owner/repo[#ref[:subdir]]locators. See @poe-code/workspace-resolver for the full locator syntax.options.model– Model identifier override (optional)options.mode– Permission mode:yolo,auto,edit, orread(optional; defaults toauto. Agents without an auto mode fail clearly)options.args– Additional arguments forwarded to the CLI (optional)
Returns { stdout, stderr, exitCode }.
spawn.pretty(service, options)
Same as spawn(), but renders the ACP event stream to stdout with colored, formatted output — matching the CLI's visual style.
import { spawn } from "poe-code"
const result = await spawn.pretty("codex", "Fix the bug in auth.ts")
console.log(result.exitCode)
Returns Promise<{ stdout, stderr, exitCode }>.
getPoeApiKey()
Reads the Poe API key with the following priority:
POE_API_KEYenvironment variable- Credentials file (
~/.poe-code/credentials.enc)
Throws if no credentials found.
getPoeAuthIdentity()
Fetches the Poe account identity for the resolved API key.
import { getPoeAuthIdentity } from "poe-code";
const identity = await getPoeAuthIdentity();
console.log(identity.name, identity.handle);
Uses POE_API_KEY or the stored credential and honors POE_BASE_URL. Throws an API error when Poe rejects the credential.
Research Preview
These features are available but subject to breaking changes.
- Pipeline — Run YAML task plans through agents with configurable steps
- Ralph — Agentic build loop that iterates on a markdown doc
- Experiment loop — Karpathy-style optimize loop: agent changes code, eval script scores it, keep or discard via git, repeat.
- Poe Agent — Composable agent runtime