# Julia Session

> Manage multiple Julia REPL sessions (create, switch, list, destroy)

- **Type:** Skill
- **Install:** `agentstack add skill-samtalki-agentrepl-jl-julia-session`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [samtalki](https://agentstack.voostack.com/s/samtalki)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [samtalki](https://github.com/samtalki)
- **Source:** https://github.com/samtalki/AgentREPL.jl/tree/main/claude-plugin/skills/julia-session

## Install

```sh
agentstack add skill-samtalki-agentrepl-jl-julia-session
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Julia Session Management

Manage multiple concurrent Julia REPL sessions. Each session has its own isolated worker process with separate state, packages, and project environment.

## Arguments

- `action` - One of: `create`, `switch`, `list`, `destroy`
- `name` - Session name (required for create/switch/destroy)

## Instructions

Parse the user's arguments:

| User Input | Action | Name |
|------------|--------|------|
| `create analysis` | create | analysis |
| `switch testing` | switch | testing |
| `list` | list | (none) |
| `destroy old-session` | destroy | old-session |

Call `session` with the appropriate action and name parameters.

## When to Create Separate Sessions

- **Development + Testing**: One session for development work, another for running tests
- **Multiple Projects**: One session per project when working across repos
- **Benchmarking**: Isolate benchmark runs from development state
- **Experimentation**: Try something risky without affecting your main session

## Session Lifecycle

1. Sessions start with no worker — workers spawn lazily on first `eval`
2. Each session gets its own Malt.jl worker process
3. Variables, packages, and project environment are fully isolated between sessions
4. Revise.jl is auto-loaded on each worker if available
5. The "default" session is auto-created if you use `eval` without creating a session first

## Notes

- Session names should be short, descriptive identifiers (e.g., "dev", "test", "analysis")
- Use `list` to see all sessions with their worker status, project, and Revise availability
- The `*` marker in list output indicates the current session
- Destroying a session kills its worker process immediately
- If you destroy the current session, another session becomes current automatically

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [samtalki](https://github.com/samtalki)
- **Source:** [samtalki/AgentREPL.jl](https://github.com/samtalki/AgentREPL.jl)
- **License:** Apache-2.0

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-samtalki-agentrepl-jl-julia-session
- Seller: https://agentstack.voostack.com/s/samtalki
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.