slife 0.1.0__tar.gz

slife-0.1.0/.claude/settings.local.json

@@ -0,0 +1,10 @@
+{
+  "permissions": {
+    "allow": [
+      "PowerShell(uv sync *)",
+      "PowerShell(uv run *)",
+      "Bash(git config *)",
+      "PowerShell(uv build *)"
+    ]
+  }
+}

slife-0.1.0/.gitignore

@@ -0,0 +1,221 @@
+# Project config (contains local settings)
+slife.json5
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml

slife-0.1.0/.python-version

@@ -0,0 +1 @@
+3.13

slife-0.1.0/.vscode/extensions.json

@@ -0,0 +1,5 @@
+{
+  "recommendations": [
+    "mrmlnc.vscode-json5"
+  ]
+}

slife-0.1.0/.vscode/settings.json

@@ -0,0 +1,21 @@
+{
+  "files.associations": {
+    "*.json5": "json5",
+    "*.j2": "jinja"
+  },
+  "[json5]": {
+    "editor.tabSize": 2,
+    "editor.insertSpaces": true
+  },
+  "[jinja]": {
+    "editor.wordWrap": "on"
+  },
+  "[log]": {
+    "editor.wordWrap": "on",
+    "editor.quickSuggestions": {
+      "comments": "off",
+      "strings": "off",
+      "other": "off"
+    }
+  }
+}

slife-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 juzcn
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

slife-0.1.0/PKG-INFO

@@ -0,0 +1,147 @@
+Metadata-Version: 2.4
+Name: slife
+Version: 0.1.0
+Summary: Terminal-based AI agent — a function-calling loop with minimum harness
+Project-URL: Homepage, https://github.com/juzcn/slife
+Project-URL: Repository, https://github.com/juzcn/slife
+Author-email: juzcn <zhangjun@cueb.edu.cn>
+License: MIT
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Terminals
+Requires-Python: >=3.13
+Requires-Dist: httpx>=0.27.0
+Requires-Dist: jinja2>=3.1.0
+Requires-Dist: json5>=0.15.0
+Requires-Dist: openai>=1.0.0
+Requires-Dist: textual>=1.0.0
+Description-Content-Type: text/markdown
+
+# slife
+
+Terminal-based AI agent — a function-calling loop with minimum harness. Chat with an LLM that can execute shell commands, search the web, and load on-demand skills.
+
+## Quick Start
+
+```bash
+# Install
+uv sync
+
+# Configure
+cp slife.json5.example slife.json5
+# Edit slife.json5 — set your API keys via ${ENV_VAR} references
+
+# Run
+uv run slife
+```
+
+## Configuration
+
+Edit `slife.json5`. Key sections:
+
+```json5
+{
+  models: {
+    providers: {
+      deepseek: {
+        base_url: "https://api.deepseek.com",
+        api_key: "${DEEPSEEK_API_KEY}",
+        models: [
+          { model: "deepseek-v4-flash", name: "DeepSeek V4 Flash" },
+          { model: "deepseek-v4-pro", name: "DeepSeek V4 Pro", reasoning: true },
+        ],
+      },
+    },
+  },
+  active_model: "deepseek/deepseek-v4-pro",
+  agent: { max_iterations: 10 },
+  tools: [
+    { type: "platform" },
+    { type: "shell", timeout: 30 },
+    { type: "serper" },
+    { type: "skill", skills_dir: "skills" },
+  ],
+}
+```
+
+API keys use `${ENV_VAR}` syntax — set them in your environment, not in the config file.
+
+## Tools
+
+| Tool | Type | What it does |
+|------|------|-------------|
+| `execute_shell` | `shell` | Run shell commands on the host machine |
+| `get_shell_command` | `platform` | Translate intent into OS-correct shell syntax |
+| `web_search` | `serper` | Google Search via Serper.dev API |
+| `list_skills` | `skill` | List available skill plugins |
+| `use_skill` | `skill` | Load a skill's documentation into context |
+
+Add or remove tools from the `tools[]` list to control what the agent can do.
+
+## Skills
+
+Skills are on-demand documentation plugins. The agent loads them only when needed, keeping the context lean.
+
+```
+skills/baidu-search/
+  SKILL.md              # Instructions the agent reads
+  scripts/search.py     # Supporting code
+```
+
+Flow: the agent calls `list_skills` → sees what's available → calls `use_skill("baidu-search")` to load full instructions.
+
+To add a skill, create a directory under `skills/` with a `SKILL.md` file.
+
+## Tips
+
+- **`/file image.png`** — attach an image for vision models
+- **`Ctrl+C`** — clear the conversation
+- **`Ctrl+Q`** — quit
+
+## Design
+
+slife is a **minimum-harness agent**. The harness only does three things the LLM cannot: execute tools, maintain conversation state, and stream responses. Everything else — reasoning, planning, tool selection, error recovery — is the LLM's job.
+
+The system prompt is intentionally lean. It only contains project-specific information not in the LLM's training data. The LLM already knows how function calling works.
+
+See [docs/design.md](docs/design.md) for the full design rationale.
+
+## Project Structure
+
+```
+slife/
+  agent/           # Core agent loop, LLM client, conversation
+    loop.py        #   Function-calling while-loop
+    llm_client.py  #   OpenAI-compatible streaming client
+    conversation.py#   Message history (OpenAI format)
+    service.py     #   Wiring: client + tools + loop
+    system_prompt.py#  Jinja2 template rendering
+  tools/           # Extensible tool system
+    base.py        #   Tool ABC
+    registry.py    #   Name → Tool lookup
+    factory.py     #   Config type → Tool instances
+    shell.py       #   execute_shell
+    shell_command.py#  get_shell_command (platform-aware)
+    serper.py      #   web_search (Serper.dev)
+    skill.py       #   list_skills / use_skill
+  ui/              # Textual TUI
+    app.py         #   Main application
+    chat.py        #   Message widgets
+    handler.py     #   Streaming event → UI bridge
+    tool_display.py#   Tool call rendering
+  config.py        # JSON5 config loading
+  env.py           # ${ENV_VAR} resolution
+  platform.py      # OS detection, shell syntax
+  skills/          # Skill plugins
+  docs/            # Design documents
+```
+
+## License
+
+MIT

slife-0.1.0/README.md

@@ -0,0 +1,122 @@
+# slife
+
+Terminal-based AI agent — a function-calling loop with minimum harness. Chat with an LLM that can execute shell commands, search the web, and load on-demand skills.
+
+## Quick Start
+
+```bash
+# Install
+uv sync
+
+# Configure
+cp slife.json5.example slife.json5
+# Edit slife.json5 — set your API keys via ${ENV_VAR} references
+
+# Run
+uv run slife
+```
+
+## Configuration
+
+Edit `slife.json5`. Key sections:
+
+```json5
+{
+  models: {
+    providers: {
+      deepseek: {
+        base_url: "https://api.deepseek.com",
+        api_key: "${DEEPSEEK_API_KEY}",
+        models: [
+          { model: "deepseek-v4-flash", name: "DeepSeek V4 Flash" },
+          { model: "deepseek-v4-pro", name: "DeepSeek V4 Pro", reasoning: true },
+        ],
+      },
+    },
+  },
+  active_model: "deepseek/deepseek-v4-pro",
+  agent: { max_iterations: 10 },
+  tools: [
+    { type: "platform" },
+    { type: "shell", timeout: 30 },
+    { type: "serper" },
+    { type: "skill", skills_dir: "skills" },
+  ],
+}
+```
+
+API keys use `${ENV_VAR}` syntax — set them in your environment, not in the config file.
+
+## Tools
+
+| Tool | Type | What it does |
+|------|------|-------------|
+| `execute_shell` | `shell` | Run shell commands on the host machine |
+| `get_shell_command` | `platform` | Translate intent into OS-correct shell syntax |
+| `web_search` | `serper` | Google Search via Serper.dev API |
+| `list_skills` | `skill` | List available skill plugins |
+| `use_skill` | `skill` | Load a skill's documentation into context |
+
+Add or remove tools from the `tools[]` list to control what the agent can do.
+
+## Skills
+
+Skills are on-demand documentation plugins. The agent loads them only when needed, keeping the context lean.
+
+```
+skills/baidu-search/
+  SKILL.md              # Instructions the agent reads
+  scripts/search.py     # Supporting code
+```
+
+Flow: the agent calls `list_skills` → sees what's available → calls `use_skill("baidu-search")` to load full instructions.
+
+To add a skill, create a directory under `skills/` with a `SKILL.md` file.
+
+## Tips
+
+- **`/file image.png`** — attach an image for vision models
+- **`Ctrl+C`** — clear the conversation
+- **`Ctrl+Q`** — quit
+
+## Design
+
+slife is a **minimum-harness agent**. The harness only does three things the LLM cannot: execute tools, maintain conversation state, and stream responses. Everything else — reasoning, planning, tool selection, error recovery — is the LLM's job.
+
+The system prompt is intentionally lean. It only contains project-specific information not in the LLM's training data. The LLM already knows how function calling works.
+
+See [docs/design.md](docs/design.md) for the full design rationale.
+
+## Project Structure
+
+```
+slife/
+  agent/           # Core agent loop, LLM client, conversation
+    loop.py        #   Function-calling while-loop
+    llm_client.py  #   OpenAI-compatible streaming client
+    conversation.py#   Message history (OpenAI format)
+    service.py     #   Wiring: client + tools + loop
+    system_prompt.py#  Jinja2 template rendering
+  tools/           # Extensible tool system
+    base.py        #   Tool ABC
+    registry.py    #   Name → Tool lookup
+    factory.py     #   Config type → Tool instances
+    shell.py       #   execute_shell
+    shell_command.py#  get_shell_command (platform-aware)
+    serper.py      #   web_search (Serper.dev)
+    skill.py       #   list_skills / use_skill
+  ui/              # Textual TUI
+    app.py         #   Main application
+    chat.py        #   Message widgets
+    handler.py     #   Streaming event → UI bridge
+    tool_display.py#   Tool call rendering
+  config.py        # JSON5 config loading
+  env.py           # ${ENV_VAR} resolution
+  platform.py      # OS detection, shell syntax
+  skills/          # Skill plugins
+  docs/            # Design documents
+```
+
+## License
+
+MIT