Skip to main content

Alysis Code — Everyone's Coding Agent

Local CLI coding agent that turns plans into reviewed, PR-ready code.
Bring your own model. Sandboxed by default.

Website · Docs · Changelog

GitHub Sponsors

CI PyPI version Python versions License


Get Started

Alysis Code requires Python 3.11+ and runs on macOS, Linux, and Windows.

1 — Install

pipx install alysis-code

2 — Launch in your project

cd your-project
alysis-code

The first run opens a guided setup wizard: choose Use an API key or Use an AI subscription, connect a provider, and pick your default model. Re-run it anytime with alysis-code setup. (alysis works too, as a short alias.)

3 — Start building

alysis-code chat                            # interactive coding session
alysis-code run "Fix the failing tests"     # one-shot task

Bring your own key from any supported provider — or point Alysis Code at a local endpoint (Ollama, LM Studio, vLLM) and run fully offline. The /config picker lists every preset. Full walkthrough: Quickstart guide.


Why Alysis Code

  • Easy to use — a full coding agent behind a clean, convenient terminal interface that anyone can pick up and play with in minutes: slash commands, interactive pickers, and live status built in.
  • Built for every developer — from solo scripts to team servers and CI, the same agent fits every workflow.
  • Forge Mode — plan-driven execution for larger work: plan, dispatch parallel workers, verify each task, ship PR-ready code.
  • Orchestrated subagents — isolated workers run in parallel, verification is pinned to their exact candidates, and changes apply only after host-side conflict checks.
  • Free built-in web search — model-independent web_search that works with any provider, at no extra cost.
  • Bring your own model — OpenAI, Anthropic, DeepSeek, Qwen, Gemini, Mistral, Xiaomi MiMo, OpenRouter, xAI, and more — plus local endpoints (Ollama, LM Studio, vLLM) for fully offline use.
  • Deeply extensible — skills, custom tools, MCP servers, hooks, subagents, and plugins, bundled in one declarative manifest.
  • Sandboxed by default — Docker or Bubblewrap isolation with an always-on denylist that refuses 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.

Permissions & Personas

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.

License

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.

FAQ

Where did Alysis Code come from?

Alysis Code is not a fork. The agent runtime, Forge orchestration, subagent system, terminal interface, and sandbox layer were designed and built from zero by the Alysis AI team.

Is Alysis Code really open source?

Yes. The entire CLI is Apache-2.0 licensed. Bring your own API key from any supported provider, or run fully offline against a local endpoint — nothing in the agent requires a paid account.

More questions? See the full FAQ.


Join the community — X | GitHub Issues

Editor integrations

VS Code uses the shared Alysis sidebar and Python IDE bridge. JetBrains is a development preview with a smaller feature set. The VS Code Marketplace pre-release is pending production signing and acceptance; see the IDE release status before installing component packages.

Metadata

Release files for alysis-code 0.14.8

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for alysis-code 0.14.8
File Size Uploaded Provenance Actions
alysis_code-0.14.8.tar.gz 2.6 MB With provenance Details for alysis_code-0.14.8.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for alysis-code 0.14.8
File Interpreter ABI Platform Actions
alysis_code-0.14.8-py3-none-any.whl Python 3 none any Details for alysis_code-0.14.8-py3-none-any.whl

Total release size: 5.6 MB

Release files / alysis_code-0.14.8.tar.gz

Download URL alysis_code-0.14.8.tar.gz
Size 2.6 MB
Tags Source
SHA-256 checksum
How to use checksums
dd4ba779362c2b7f877e432bb2a19e9f73982af84a04ccfd6c6b899c3902f909
BLAKE2b-256 checksum
How to use checksums
22dd8cd1d937f1cc62f717cfb7860cbfd0650bbfcdff67a90b4968545eb8103b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.

Transparency log

Release files / alysis_code-0.14.8-py3-none-any.whl

Download URL alysis_code-0.14.8-py3-none-any.whl
Size 2.9 MB
Tags Python 3
SHA-256 checksum
How to use checksums
54c152de961e865ba305606a77aadc04d636825abb2b9f9aa79ff37ca5d4a5a2
BLAKE2b-256 checksum
How to use checksums
34d85c43a97696a8d74d63a5f2b74a157947c0a6bc074570f147083fc301798e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.

Transparency log

Security for alysis-code 0.14.8

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for alysis_code-0.14.8.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page