andrewyng--aisuite
Devika
eb160aae74
Two developer surfaces on top of the agent runtime: a local web viewer for inspecting agent runs and traces, and a coding-agent CLI. Viewer: - aisuite/tracing: a local ViewerServer that serves a runs/trace UI, plus HttpTraceSink, TraceStoreSink, and InMemoryTraceStore - viewer-ui: React/Vite single-page app for browsing runs, with the prebuilt bundle shipped under aisuite/tracing/static/viewer CLI: - cli/py/aisuite-code-cli: the aisuite-code coding-agent CLI (app, agent loop, approval flow, config, rendering) as a standalone package - scripts/aisuite-code launcher and examples/cli usage - tests for the viewer server, trace sinks, and the CLI Co-authored-by: Rohit <rohit.prasad15@gmail.com>
1.2 KiB
1.2 KiB
Try aisuite-code locally
From the repository root:
./scripts/aisuite-code --cwd /tmp/aisuite-cli-play --viewer
If you prefer running from the package directory:
cd cli/py/aisuite-code-cli
python3 -m poetry install
python3 -m poetry run aisuite-code --cwd /tmp/aisuite-cli-play --viewer
Make sure OPENAI_API_KEY is set first. If the repo .env contains it:
set -a
source .env
set +a
Prompts to try:
List files in this directory and tell me what you see.
Create app.py with an add(a, b) function and a small main block that prints add(2, 3). Then run it.
Show git status and git diff.
Ask the reviewer subagent to review the current changes.
Expected behavior:
- File reads and git status/diff are read-only and should not ask for approval.
- File writes and shell commands ask for approval before execution.
- Shell approvals support allowing once, denying, always allowing the tool, or always allowing the exact command for the session.
/viewer startstarts the local trace viewer if it was not started at launch./statusshows model, cwd, trace file, artifact root, and shell command policy.