by AlysisAi
Open-source AI coding agent for your terminal. Bring any model (OpenAI, Anthropic, Gemini, Ollama), sandboxed by default, plans to PR-ready code.
# Add to your Claude Code skills
git clone https://github.com/AlysisAi/AlysisCodeLast scanned: 10/24/2026
{
"issues": [
{
"file": "README.md",
"line": 57,
"type": "remote-install",
"message": "Install command (remote install script piped to a shell — review the source before running): \"curl -LsSf https://raw.githubusercontent.com/AlysisAi/AlysisCode/main/scripts/in\"",
"severity": "low"
}
],
"status": "PASSED",
"scannedAt": "2026-10-24T08:40:49.023Z",
"npmAuditRan": true,
"pipAuditRan": true,
"promptInjectionRan": true
}See how AlysisCode compares with popular alternatives.
AlysisCode is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by AlysisAi. Open-source AI coding agent for your terminal. Bring any model (OpenAI, Anthropic, Gemini, Ollama), sandboxed by default, plans to PR-ready code. It has 183 GitHub stars.
Yes. AlysisCode passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/AlysisAi/AlysisCode" and add it to your Claude Code skills directory (see the Installation section above).
AlysisCode is primarily written in Python. It is open-source under AlysisAi on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh AlysisCode against similar tools.
No comments yet. Be the first to share your thoughts!
30 days in the Featured rail · terms & refunds
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
Automated security scan — not a certification.
Alysis Code requires Python 3.11+ and runs on macOS, Linux, and Windows.
1 — Install
On Windows, paste this into PowerShell:
irm https://raw.githubusercontent.com/AlysisAi/AlysisCode/main/scripts/install.ps1 | iex
On Linux, macOS, or inside a WSL/Ubuntu terminal:
curl -LsSf https://raw.githubusercontent.com/AlysisAi/AlysisCode/main/scripts/install.sh | sh
The installers provision uv and Python 3.12 when needed. No existing Python or pipx is required.
PowerShell can use alysis immediately; after the shell installer, follow its PATH instructions
or open a new terminal. If you already use pipx, pipx install alysis-code also works;
run pipx ensurepath and restart your terminal if the command is missing.
Already installed? Run alysis update to get the latest release.
2 — Choose how to connect to a model
Pick one path. You can switch later with /config or by re-running alysis-code setup.
Path A — Your own API key or a local model (no Alysis account needed)
cd your-project
alysis-code
The first run opens a guided setup wizard. Choose Use an API key, connect a provider
(OpenAI, Anthropic, DeepSeek, Gemini, OpenRouter, and more), and pick your default model.
To run fully offline, point Alysis Code at a local endpoint (Ollama, LM Studio, vLLM) from the
/config picker, which lists every preset. Prefer to configure it by hand?
export ALYSIS_API_KEY="YOUR_KEY"
alysis config set base_url "https://api.openai.com/v1"
alysis config set model "gpt-4.1-mini"
Have a ChatGPT subscription instead? Choose Use an AI subscription in the wizard, or run
alysis auth login openai-codex.
Path B — Alysis account
alysis login
Approve the code in your browser to use your Alysis credits. No provider key and no cloud environment variables are needed.
3 — Start building
cd your-project
alysis-code chat # interactive coding session
alysis-code run "Fix the failing tests" # one-shot task
(alysis works too, as a short alias.) The /config picker lists every provider preset.
Full walkthrough: Quickstart guide.
Alysis Code App is powered by the open-source Alysis Code engine, bringing an agentic desktop experience to coding and broader everyday work.
web_search that works with any provider, at no
extra cost.rm -rf /, curl | sh, and sudo — even in
fullaccess.Shell and verification commands default to strict sandboxing. Verification can run outside that
sandbox only when explicitly configured with verify_sandbox.mode="off" or
ALYSIS_VERIFY_SANDBOX_MODE=off.
A quick, good-faith snapshot based on each project's public README and docs (October 2026). "—" means we couldn't confirm it from their docs; corrections welcome via an issue.
| Alysis Code | Claude Code | Aider | Codex CLI | Gemini CLI | |
|---|---|---|---|---|---|
| License | Apache-2.0 | Proprietary | Apache-2.0 | Apache-2.0 | Apache-2.0 |
| Models | Any supported provider | Claude | Almost any LLM | OpenAI (ChatGPT sign-in or API key), plus local models | Gemini |
| Local models | Yes (Ollama, LM Studio, vLLM) | — | Yes | Yes (Ollama, LM Studio) | — |
| MCP servers | Yes | Yes | — | Yes | Yes |
| Sandboxed shell | Yes, on by default (Docker / Bubblewrap) | Yes (sandboxed Bash tool) | — | Yes | Yes |
| Editor integration | VS Code (pre-release), JetBrains (preview) | Yes | Yes | Yes (VS Code, Cursor, Windsurf) | Yes (VS Code companion, ACP integrations) |
References: Codex CLI local-provider options · Gemini CLI editor integrations.
Two layers control what the agent may do — one enforces, one focuses.
Permissions are the enforcement layer. Choose one per command with --mode, select the next
message's level in chat with /permissions or Shift+Tab, or set a default with
alysis-code config set default_mode <mode>. A selection takes effect when the next user message
starts; it does not change a turn already running:
| Mode | Behavior |
|---|---|
readonly |
Inspection plus top-level read-only delegation — no file writes, shell, MCP, candidate apply/discard, or nested delegation. |
review |
The safe default — previews and asks before every write and shell command. |
auto |
Applies routine edits with fewer prompts; dangerous operations stay blocked. |
fullaccess |
No mode-level prompts for trusted workspaces — the denylist and audit log stay active. |
Personas are working postures layered on top. Switch with /persona, or cycle with Tab in
the TUI:
| Persona | Posture |
|---|---|
code |
Implementation — the default, full coding workflow. |
architect |
Planning and design — may write markdown documents only. |
ask |
Read-only questions and codebase exploration. |
debug |
Reproduce the failure first, then fix minimally and rerun the reproduction. |
A persona is a convention, never a permission: it can keep or lower your execution mode, but can
never raise it. Define your own in .alysis_personas/*.md.
Learn more
Use /persona architect for planning in chat, or /forge for a plan-driven execution workflow.
The former chat /plan commands have been removed; Forge retains its plan views and editor.
Persona changes made during a running turn apply after that turn finishes.
Apache-2.0. You're free to use, modify, and distribute this code, including commercially, as long as you keep the attribution and license notices. See LICENSE and NOTICE. The shared editor sidebar includes MIT-licensed adaptations from Kilo Code/OpenCode; retain its third-party notices.
Alysis Code is not a fork. The agent runtime, Forge orche