Download the PHP package coquibot/coqui-toolkit-backstory without Composer

On this page you can find all versions of the php package coquibot/coqui-toolkit-backstory. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package coqui-toolkit-backstory

coqui-toolkit-backstory

Optional Coqui toolkit that generates a profile's backstory.md from the source files under profiles/<name>/backstory/. It is the producer of backstory content; Coqui core is the consumer that reads the generated backstory.md into the composed prompt. This package bundles every extractor Coqui's backstory generator previously shipped in core, plus the Word, PDF, and HTML formats that used to live in the separate coqui-toolkit-backstory-formats mod — all in one toolkit, with no discovery seam to configure.

Install

The toolkit self-registers the /backstory REPL command via Coqui's toolkit extensibility mechanism (ReplCommandProvider). There is no core wiring to configure — installing the mod is enough.

The /backstory command

All three require an active profile (/profile <name>); the handler errors clearly when none is active or the named profile doesn't exist.

Source layout and output contract

This toolkit reads sources from {workspace}/profiles/<active>/backstory/ and writes {workspace}/profiles/<active>/backstory.md plus {workspace}/profiles/<active>/.backstory-manifest.json. Core reads only backstory.md at that path and has no knowledge of how it was produced — the producer/consumer split is deliberate so core stays generator-free.

Supported formats

Extension Treatment Dependency
.txt Plain text, encoding-normalized to UTF-8 none
.md, .mdx Passed through as-is after text normalization none
.json Wrapped in a fenced json code block (validates JSON) none
.yaml, .yml Wrapped in a fenced yaml code block none
.csv, .tsv Converted to a markdown table none
.sql Simple CREATE TABLE / INSERT ... VALUES statements become markdown tables; otherwise preserved as fenced sql none
.xml Rendered as a markdown outline for simple documents, otherwise fenced xml none
.rtf Converted to plain text via conservative RTF control-word stripping none
Code files (.php, .js, .ts, .jsx, .tsx, .py, .rb, .java, .c, .cpp, .cs, .go, .rs, .sh, .zsh, .ps1, .css, .scss, .less, and similar) Wrapped in fenced code blocks with language hints; never executed none
.xlsx, .xlsm Markdown table per worksheet, when runtime-supported ext-zip
.pptx, .pptm Markdown section per slide, with speaker notes appended, when runtime-supported ext-zip
.odt Markdown with paragraph/heading/list structure preserved, when runtime-supported ext-zip
.ods Markdown table per sheet, when runtime-supported ext-zip
.odp Markdown section per slide, when runtime-supported ext-zip
.docx, .docm Text extracted and converted to markdown phpoffice/phpword
.pdf Text extracted smalot/pdfparser
.html, .htm Sanitized and converted to markdown league/html-to-markdown

The dependency-free set, .docx/.docm, .pdf, and .html/.htm are all hard requires of this package's composer.json — no separate mod is needed for Word, PDF, or HTML anymore. The ext-zip-backed office formats (.xlsx, .pptx, .odt, .ods, .odp) degrade gracefully: when ext-zip isn't available, those extensions are simply left out of the extractor map and files with those extensions show up as unsupported in /backstory failed.

None of these extractors execute scripts, formulas, macros, or embedded/active content — office and markup formats are read-only input, converted to markdown or fenced text.

Sort order and change detection

Source files are sorted using a numbered-first natural sort:

  1. Files with numeric prefixes (e.g., 01-intro.md) sort first, in natural order.
  2. Unnumbered files follow alphabetically.
  3. Files at each directory level appear before subdirectory contents.
  4. Hidden files and directories (starting with .) are skipped.

A .backstory-manifest.json file tracks SHA-256 hashes of every discovered source file, including unsupported ones. Generation is skipped when the content hash matches what was last generated, so repeated /backstory generate calls are cheap even with hundreds of source files, while still detecting newly added unsupported inputs.

On-demand generation (no auto-regeneration)

Generation only happens when you run /backstory generate. There is no boot-time auto-regeneration — Coqui core no longer regenerates backstory.md on startup. The /backstory overview compares the current source tree against the manifest and prints a staleness hint when they've drifted, so you know to run /backstory generate yourself.

Budget caveat

backstory.md is loaded and pinned into the system prompt on every turn once a profile is active — it is not paged in on demand. Keep source content proportionate to what the profile actually needs; large or redundant backstory sources inflate every request in that profile's context budget.

API routes

This toolkit does not provide any HTTP API routes. /backstory is a REPL-only command; API exposure is out of scope for this package.

Development

All versions of coqui-toolkit-backstory with dependencies

PHP Build Version
Package Version
Requires php Version ^8.4
league/html-to-markdown Version ^5.1
phpoffice/phpword Version ^1.0
smalot/pdfparser Version ^2.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package coquibot/coqui-toolkit-backstory contains the following files

Loading the files please wait ...