Python: New Feature:

Open
#14,573 8 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
3/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
python
Domain
security

Research direction

This is a vendor pitch for an external sandbox library, not a request for a change in the repository, so there is no file, test or entry point to start from. A newcomer should not pick it up. A maintainer would need to decide whether an integration is wanted at all, and any real work would start from an agreed design.

Written by the indexing model from the issue text.

Description

python triage

Hi Microsoft Agent Framework Team,As AutoGen and Semantic Kernel merge into unified agent runtimes, securing local process execution and tool actions without heavy performance penalties is critical.We built veltra-agent—a zero-Docker, OS-native kernel sandbox designed specifically for agent execution safety. It uses Linux Landlock LSM and macOS Seatbelt to enforce strict filesystem boundaries and block process subshell escapes at <60ms startup latency. Here is a 5-line integration wrapper in Python: Pythonfrom veltra import Sandbox

Strictly locks file read/write at the OS syscall layer

with Sandbox(allowed_paths=["/path/to/workspace"]):
# Run untrusted tool / python execution
pass
If you are evaluating native execution isolation for local tool runners, we'd love to share benchmarks or submit an integration example: https://github.com/Jayanthpulisheri/veltra-ai-engine Best regards,Jayanth

Dominant language
C#
Stars
28.8k
Forks
4.9k
Avg merge
2d 17h
Merged PRs (30d)
48

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/semantic-kernel

All issues in microsoft/semantic-kernel

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.